This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Interaction Versioning"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) (new page) |
Rene spronk (talk | contribs) |
||
| Line 11: | Line 11: | ||
Implication: The complete version of all message types, CMETs, Vocabulary, Datatypes and ITS is fully pre-coordinated in the version of the identifier combined with the Release version. | Implication: The complete version of all message types, CMETs, Vocabulary, Datatypes and ITS is fully pre-coordinated in the version of the identifier combined with the Release version. | ||
| + | |||
| + | Question: the version of what things/artefacts can NOT be derived from the interaction identifier version? Or: the version of what things/artefacts can ONLY be derived from the Release/versionCode attribute? [[User:Rene spronk|Rene spronk]] 06:41, 30 Apr 2006 (CDT) | ||
Revision as of 11:41, 30 April 2006
(from an MnM discussion and decision during the Sept 2005 WGM)
Artifacts using traditional identifiers (SSDD_AAnnnnnnRRvv) are assigned versions under two circumstances:
- When the artifact passes membership and is Semantically Backward Compatible with the previous version. If not semantically backward compatible, you *must* assign a new identifier, not a new version.
- When dependents of the artifact have been assigned new versions, the parent of those dependent artifacts will be assigned a new version as part of the normative release.
Caveats:
- Assumption is that 'semantically backward compatible' means not necessarily schema-compatible, but doesn't allow for complete remodeling of content either.
- Non-semantically compatible changes in approach to Datatypes, RIM, Vocabulary and/or ITS could result in a mass version change to all artifacts.
- The version specified in the instance interactionId attribute must be the same as the interaction version published in the edition specified in the instance versionCode attribute.
Implication: The complete version of all message types, CMETs, Vocabulary, Datatypes and ITS is fully pre-coordinated in the version of the identifier combined with the Release version.
Question: the version of what things/artefacts can NOT be derived from the interaction identifier version? Or: the version of what things/artefacts can ONLY be derived from the Release/versionCode attribute? Rene spronk 06:41, 30 Apr 2006 (CDT)
