This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Interaction and Versioning"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
|||
| Line 9: | Line 9: | ||
How is versioning, and 'backwards compatibility' related to interaction version (in its name), profileId, etc. | How is versioning, and 'backwards compatibility' related to interaction version (in its name), profileId, etc. | ||
| − | See | + | See [[Interaction_Versioning]] and [[Interaction_Conformance_and_Versioning_-_Implementation_Issues]] for earlier discussions on this topic. |
| − | and | ||
| − | |||
| − | |||
| − | |||
| − | for earlier discussions on this topic. | ||
Effectively NICTIZ poses the question "can new artefacts (compliant | Effectively NICTIZ poses the question "can new artefacts (compliant | ||
with the new/modified model) be parsed by the current schema"? If not, | with the new/modified model) be parsed by the current schema"? If not, | ||
then we need a new interaction version. | then we need a new interaction version. | ||
Revision as of 04:20, 30 December 2007
This page documents an Open MnM Hot Topic, i.e. a methodology issue requiring a resolution from Modeling and Methodology.
How is versioning, and 'backwards compatibility' related to interaction version (in its name), profileId, etc. See Interaction_Versioning and Interaction_Conformance_and_Versioning_-_Implementation_Issues for earlier discussions on this topic.
Effectively NICTIZ poses the question "can new artefacts (compliant with the new/modified model) be parsed by the current schema"? If not, then we need a new interaction version.
