Context Navigation

Changes between Version 16 and Version 17 of CMDI 1.2/Lifecycle management

v16	v17
32	32
33	33	The '''component specification''' needs to be extended with a number of header elements that contain the versioning information. The header elements to be added are described in the following subsections. Because the header gets embedded into an 'appinfo' element in the schema derived from profile specifications, the state and versioning information is available from the schema as well, which is convenient for tools that (primarily) make use of the schema.
	34
	35	In addition to these extensions to the component model, the ''infrastructure'' needs to be adapted to implement a ''workflow'' for changing lifecycle statuses and the consequences of such changes. More specifically, the CMDI Component Registry will have to manage the status of each component and discourage users (both metadata modellers and creators) from using components or profiles that carry a non-production (i.e. development or deprecated) state. Details of the required changes are given below under 'centre impact'.
34	36
35	37	==== Status header ====