Changes between Version 14 and Version 15 of CMDI 1.2/Lifecycle management

Timestamp:

01/20/14 14:46:08 (10 years ago)

Author:

oddrun.ohren@nb.no

Comment:

--

CMDI 1.2/Lifecycle management

@@ -136 +136 @@
 
 ----
-Oddrun: After having read other parts of this wiki, I begin to think we should distinguish between updates (to a component) that qualify for state change, and those which do not. For instance, adding a documentation file to a component corresponds to updating its ''metadata'', not the component in itself.  Thereby, it has no consequences for its instances.
+ Oddrun: After having read other parts of this wiki, I begin to think we should distinguish between updates (to a component) that qualify for state change, and those which do not. For instance, adding a documentation file to a component corresponds to updating its ''metadata'', not the component in itself.  Thereby, it has no consequences for its instances.
  Menzo: This not a CMDI 1.2 issue but could be a nice addition for the CR. Still its tricky to assess what changes have a semantic impact, e.g., the documentation file might state some restrictions that were not explicit before as they can't be expressed by CMDI, e.g., if element A has a value X then optional element B should have a value.