Changes between Version 3 and Version 4 of CMDI 1.2/Schema sanity/Namespaces
- Timestamp:
- 12/05/13 15:53:10 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CMDI 1.2/Schema sanity/Namespaces
v3 v4 13 13 == Proposed solutions == 14 14 15 === First solution ===15 === First solution: be pragmatic === 16 16 17 17 One can be pragmatic and conclude that we have been using OAI-PMH for harvesting CMDI for several years now, so this non-compliance can be ignored. … … 37 37 Discuss this solution proposal in this section 38 38 39 === Second solution ===39 === Second solution: profile specific metadataPrefixes === 40 40 41 41 A metadataPrefix per profile, e.g., cmdi0554, cmdi0571, cmdi2312. Each of these metadataPrefixes is linked to a different schema. … … 63 63 Discuss this solution proposal in this section 64 64 65 === Third solution ===65 === Third solution: up to the centers === 66 66 67 67 Leave it up to the centers to choose between the first or second solution. … … 87 87 Discuss this solution proposal in this section 88 88 89 === Fourth solution ===89 === Fourth solution: CMD envelop and payload specific schemas and namespaces === 90 90 91 91 The envelope of a CMD record is fixed and described by the [http://infra.clarin.eu/cmd/xsd/minimal-cmdi.xsd minimal CMD schema] (TODO: needs to be synced with the latest version of the envelope generated by the [http://infra.clarin.eu/cmd/xslt/comp2schema-v2/comp2schema.xsl CMDI XSD XSLT]). We can bind this schema to the metadataPrefix and also use it in the instance. The profile specific schema would then only describe the profile specific part of the CMD record. However the namespace schema binding in xsi:schemaLocation only allows us to use a namespace once, which means we need two namespaces one for the envelope and one for the payload: … … 187 187 Discuss this solution proposal in this section 188 188 189 === Fifth solution ===189 === Fifth solution: profile specific payload namespaces === 190 190 191 191 Same as the fourth solution but instead of a fixed namespace to be used by all profiles each profile payload gets its own namespace.
