Changes between Version 18 and Version 19 of CMDI 1.2/Lifecycle management


Ignore:
Timestamp:
02/11/14 16:12:56 (10 years ago)
Author:
twagoo
Comment:

component registry nice to haves

Legend:

Unmodified
Added
Removed
Modified

  • CMDI 1.2/Lifecycle management

    v18 v19  
    33= Component lifecycle management in CMDI 1.2 =
    44
    5 [[PageOutline(1-4)]]
     5[[PageOutline(1-5)]]
    66
    77== The issue ==
    … …  
    8181The expected impact will be relatively small as implementation wise all required changes are in the 'metadata' of the component specification and can actually be ignored. The only software component that is affected in a large degree is the Component Registry, which will be responsible for gathering, storing and representing the status and versioning information.
    8282
    83 ''[Marc Kemps-Snijders showed some concerns regarding the situation at Meertens, would be good to summarize here]''
    84 
    8583===== Tools: Component Registry =====
    8684
    8785Status can be mapped to views, see [[ComponentVersioning#Viewsworkspacesandregistries|ComponentVersioning]]. Besides that, the Component Registry will have to provide inputs for the user to manage the status of their own components. Part of the information gathering can be automated (!DerivedFrom).
     86
     87====== Nice to haves ======
     88
     89* Notification of component owners when a component referenced in one of their components becomes deprecated
     90* Notification of component owners when a derivative of one of their components is created
    8891
    8992===== Tools: metadata editing =====