This page is a subpage of CMDI 1.2

Migration issues for CMDI 1.2

An executive summary is available at CMDI 1.2/Migration/Summary

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).

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).

Some statements to consider (open for discussion!):

• Existing metadata and tools should not break as a result of the appearance of the new version of CMDI
• Migration is strongly recommended but should remain optional
• New tools should ideally support both CMDI 1.1 and CMDI 1.2 metadata
  • in most cases this will require some degree of version-awareness
• There is no need to support migration ('downgrading') of CMDI 1.2 based instances to CMDI 1.1

Sub-issues

• Migration of components
• Migration of instances
• Tool aspects of migration

Also see

• Conrete information with respect to rollout

Also see Schema version management.

Tickets

Tickets in the CMDI 1.2 milestone with keyword migration:

Ticket	Summary	Owner	Component	Priority	Status
#235	Implement conversion from CMDI 1.1 to 1.2	Dieter Van Uytvanck	ComponentSchema	major	closed

Discussion

Discuss the migration of 1.1 to 1.2 in general below this point