Version numberting of COEL Data Model

[matt Reed <matt@coelition.org>]

Hi,

I have been trying to write the section on Principles for version control of COEL model.The major problem is keeping track of how different versions of the COEL Specification relate (or not) to versions of the COEL Data Model JSON Artefact.

I think the text is as follows:

The OASIS COEL-TC has adopted a conservative approach to modifying the COEL model. This is because the structure of the COEL Data Model is a fundamental part of the whole COEL specification. If possible, changes to the structure of the COEL Data Model should be avoided.

When a non-backwards compatible change is made, e.g. new structure or changing the value of an existing field, this change MUST run through the full OASIS process. The Index value 0 in the Version section of JSON artefact MUST be incremented. In addition, a new version of the COEL Specification will be released by OASIS. If the implications of the change in the COEL Data Model are minor then this new version MUST be agreed by the OASIS Committee. If the changes are more substantial then the new version MUST run through the full OASIS process.

When a backwards compatible change is made, e.g. new fields, this change MUST be agreed by the OASIS Committee. The Index value 1 in the Version section of JSON artefact MUST be incremented. In addition, a new version of the COEL Specification MUST be released by the OASIS Committee.

A plain text concordance aligning appropriate version numbers of the COEL Specification and COEL Data Model will be permanently held at URI.

Then the table we already had describing the JSON Artefacts Version section.

Best wishes

Matt