Context Navigation

Changes between Version 7 and Version 8 of CMDI 1.2/Migration

v7	v8
4	4	Centres should migrate their metadata, tools and infrastructure to CMDI 1.2 if they want to keep up with current developments. The challenge is to provide means for centres to carry out such a migration independently, with an acceptable amount of effort and at their own pace (i.e. the degree of centralised orchestration should be minimal).
5	5
6		Migration will ~~be a matter primarily~~ of upgrading: existing 1.1 components and profiles will be centrally migrated to 1.2, and existing 1.1 instances can be converted to 1.2 equivalents using an XSLT stylesheet made available. To keep new components available for existing versions of tools, a 'dumbing down' procedure will be available for the Component Registry, providing a 1.1 projection of 'native' 1.2 profiles so that these can still be used with existing software (lacking new features from 1.2 of course).
	6	Migration will primarily be a matter of upgrading: existing 1.1 components and profiles will be centrally migrated to 1.2, and existing 1.1 instances can be converted to 1.2 equivalents using an XSLT stylesheet made available. To keep new components available for existing versions of tools, a 'dumbing down' procedure will be available for the Component Registry, providing a 1.1 projection of 'native' 1.2 profiles so that these can still be used with existing software (lacking new features from 1.2 of course).
7	7
8	8	Some statements to consider (open for discussion!):