Changes between Version 4 and Version 5 of CMDI 1.2/Resource proxies/Single reference
- Timestamp:
- 12/05/13 15:45:21 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CMDI 1.2/Resource proxies/Single reference
v4 v5 9 9 With OAI-PMH its possible to retrieve multiple records with one request. When one validates the returned document its possible that IDs clash, as they are unique within the original XML document but there was no requirement that they should have been globally unique. 10 10 11 == Proposed solutions == 12 13 === First solution === 11 == The proposed solution == 14 12 15 13 It's possible in XSD to limit the scope of IDs and IDREFs using xs:key and xs:keyref. This solution has been described in the [[CmdiMultipleRecords]] page. A showstopper for this solution is currently that @ref can refer to multiple !ResourceProxies, i.e., the type of @ref is IDREFS, while there is no xs:keyrefs. A solution in CMDI 1.2 would be to make the type of @ref IDREF again as it was once. An investigation of the around half million harvested CMD records shows that instances of [http://catalog.clarin.eu/ds/ComponentRegistry/?item=clarin.eu:cr1:p_1345561703620# collection] profile are currently the only users of this feature, e.g., the [http://hdl.handle.net/1839/00-F78BED6F-D8DA-4355-BF41-88F6D4A169F8 IPROSLA Abel CMD collection record]. Here the root collection component refers to all the !ResourceProxies. Its debatable if that is needed, as this should be the default interpretation if there is no @ref. 16 14 17 === = Pros ====15 === Pros === 18 16 19 17 CMD records can be concatenated for bulk retrieval. 20 18 21 === = Cons ====19 === Cons === 22 20 23 21 There are CMD records that currently use multiple !ResourceProxy references in one @ref. 24 22 25 === = Centre impact ====23 === Centre impact === 26 24 27 25 When a centre uses references to multiple resource proxies in one @ref these would have to be modeled differently. 28 26 29 === = Implementation examples ====27 === Implementation examples === 30 28 31 29 See the [[CmdiMultipleRecords]] page. 32 30 33 === = Discussion ====31 === Discussion === 34 32 35 33 Discuss this solution proposal in this section
