Changes between Version 2 and Version 3 of MetadataSiblings
- Timestamp:
- Sep 19, 2012, 8:15:52 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MetadataSiblings
v2 v3 35 35 36 36 == Motivations == 37 The current configuration is .... A change to ....37 There is a need to describe named sibling relationships between metadata records. 38 38 39 39 == Proposal == 40 41 Aggregate Information in a record that has a related sibling record looks something like the following: 40 42 41 43 {{{ … … 52 54 </gmd:aggregateDataSetIdentifier> 53 55 <gmd:associationType> 54 <gmd:DS_AssociationTypeCode codeList="http://...#DS_AssociationTypeCode" codeListValue="crossReference">crossReference</gmd:DS_AssociationTypeCode> 56 <gmd:DS_AssociationTypeCode codeList="http://...#DS_AssociationTypeCode" 57 codeListValue="crossReference">crossReference</gmd:DS_AssociationTypeCode> 55 58 </gmd:associationType> 56 59 <!-- initiative type describes the type of sibling relationship - in this case the code is a project 57 60 related to the record that contains this aggregateInformation --> 58 61 <gmd:initiativeType> 59 <gmd:DS_InitiativeTypeCode codeList="http://...#DS_InitiativeTypeCode" codeListValue="project">project</gmd:DS_InitiativeTypeCode> 62 <gmd:DS_InitiativeTypeCode codeList="http://...#DS_InitiativeTypeCode" 63 codeListValue="project">project</gmd:DS_InitiativeTypeCode> 60 64 </gmd:initiativeType> 61 65 </gmd:MD_AggregateInformation> 62 66 </gmd:aggregateInformation> 63 67 }}} 64 An in depth proposal can be found here : link 65 ... 68 66 69 67 70 === Backwards Compatibility Issues ===