Changes between Version 22 and Version 23 of CMDI 1.2/Lifecycle management

Timestamp:

02/13/14 08:14:53 (10 years ago)

Author:

twagoo

Comment:

small amendments to owner/user notification

CMDI 1.2/Lifecycle management

@@ -9 +9 @@
 The issue has been described and explored on the page [[ComponentVersioning]]. The issue description below is based on the one found on that page.
 
-Once published a component gets 'frozen' so that all instantiations can rely on it not changing and thus are guaranteed to retain their validity. Also, after a certain 'cooling down' period, published components cannot be removed from the public space (except by administrators). Robust though this practice may be, it leads to issues when changes in the domain, or simply new insights, need to be incorporated in the component. It is easy to create a new component based on an existing one, extend it and finally make it public. But then one would like to communicate to the users of the component that they should use the new component for new metadata (possibly even convert existing metadata) instead of the old one. However, there are a few problems:
+Once published a component gets 'frozen' so that all instantiations can rely on it not changing and thus are guaranteed to retain their validity. Also, after a certain 'cooling down' period, published components cannot be removed from the public space (except by admsuinistrators). Robust though this practice may be, it leads to issues when changes in the domain, or simply new insights, need to be incorporated in the component. It is easy to create a new component based on an existing one, extend it and finally make it public. But then one would like to communicate to the users of the component that they should use the new component for new metadata (possibly even convert existing metadata) instead of the old one. However, there are a few problems:
 co
 * There is no reliable way to find out who is instantiating specific components, so the users are unknown and cannot simply be informed
@@ -99 +99 @@
 The following automatic notifications would be nice to have:
 
-* Notification of component owners when a component referenced in one of their components becomes deprecated
+* Notification of component owners when a component referenced (either directly or indirectly) in one of their components becomes deprecated
 * Notification of component owners when a derivative of one of their components is created
 * Notification of component subscribers when any of the subscribed components become deprecated
 
-RSS or e-mail could be used as a means of notification
+RSS or e-mail could be used as a means of notification/subscription
 
 ===== Tools: metadata editing =====