What should be the scope or nature of document releases for C2 for 2020?

[cta-source]

Put another way: Should we revise the C2 document, or publish a second document enhancing / clarifying / advancing things, but keep C2 static?

If the scope of changes isn’t great, it may be best not to open up the document and revise it.  Instead perhaps we would do an errata, or maybe publish web updates to (for example) the “mapping” Annexes E-P.  

This issue is open to comment in general, but note also that the resolutions to other issues being posted may be part of a decision here. (That is, if we resolve another issue by deciding to revise the main C2 document, then this issue discussion thread becomes moot.)

[mawalker309]

From an OCF perspective, we'd be supportive of allowing updates to the mapping Annexes. OCF continues to revise and updates its specification and open source implementation to increase security, and we'd like the opportunity to update the official mappings to reflect those changes.

Outside of updating mapping annexes, we don't see a need to open the C2 document for revisions at this time. It has been less than a year since the C2 document was publicly released and to make any significant changes so quickly after release could potentially undermine the credibility of the document.