Changes between Version 11 and Version 12 of CMDI 1.2/Migration/Instance migration

Timestamp:

02/04/14 09:25:01 (10 years ago)

Author:

twagoo

Comment:

Instance migration assessment document

CMDI 1.2/Migration/Instance migration

@@ -22 +22 @@
 The XSLT will be made publicly available so that any centre can apply it to their metadata instances as soon as they have made all other required changes to their infrastructure.
 
+[https://docs.google.com/spreadsheet/ccc?key=0Avyg_78eBoF4dFN5OWpKZE1XRDRyYm5VcG1CRW1Zanc&usp=sharing Overview of implications for instance migration of the various CMDI 1.2 specification topics]
+
 === Centre impact ===
 
@@ -34 +36 @@
 Oddrun: Not sure I understand why downgrading instances is not relevant. If some Clarin node who chooses to stick with 1.1 wants to harvest metadata from a node serving 1.2, downgrading those data could be necessary. Unless one can be sure that absolutely all tools/software are able to handle both format from the moment go.
 
-[[herold|Axel Herold]]: I'd guess that scenario would apply rarely. We could/should ask the centres whether they would stick to 1.1 while consuming with 1.2 instances provided by others. However, I would propose placing the development/maintenance burden on those center.
+ [[herold|Axel Herold]]: I'd guess that scenario would apply rarely. We could/should ask the centres whether they would stick to 1.1 while consuming with 1.2 instances provided by others. However, I would propose placing the development/maintenance burden on those center.
+
+ '''Twan''': [https://docs.google.com/spreadsheet/ccc?key=0Avyg_78eBoF4dFN5OWpKZE1XRDRyYm5VcG1CRW1Zanc&usp=sharing This document] assesses the implications for instance migration of the the various topics. Some aspects of the downgrade can be tricky. I think we should not want to promise an out-of-the-box downgrade but leave it up to the centres as Axel proposes.