Changes between Version 8 and Version 9 of CMDI 1.2/Lifecycle management

Timestamp:

01/10/14 13:49:19 (10 years ago)

Author:

oddrun.ohren@nb.no

Comment:

--

CMDI 1.2/Lifecycle management

@@ -25 +25 @@
 This information needs to be communicated to the client that request the deprecated component, and remove it from the public list. Clients should of course still be able to use the deprecated component since it is not always possible to upgrade.
 
-[[Image(versioning.png,400)]]
+[[Image(versioning.png,600)]]
 
 == Proposed solution ==
@@ -123 +123 @@
 * Propagation of status change: In the proposed solution, steps are taken to prevent inadvertent use of deprecated components (remove them from public view). However, CMDI is a recursive universe, and any component may occur in other components and/or profiles. Consider the following figure:
 
-[[Image(version-propagation.png,600)]]
+[[Image(version-propagation.png,400)]]
 
 When C2 is deprecated and a new version is available, this information should in some way be propagated to all its containing components and profiles. If not, both C1 and P1 will remain available in public. Any users selecting P1 (or another profile containing C2) for their metadata will then also choose the deprecated C2, without knowing that it is so. I really think that when a component is "replaced" by a new version, any "new" use of the old version should be strongly discouraged.