Changes between Version 2 and Version 3 of MetadataSiblings


Ignore:
Timestamp:
Sep 19, 2012, 8:15:52 PM (12 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MetadataSiblings

    v2 v3  
    3535
    3636== Motivations ==
    37 The current configuration is .... A change to ....
     37There is a need to describe named sibling relationships between metadata records.
    3838
    3939== Proposal ==
     40
     41Aggregate Information in a record that has a related sibling record looks something like the following:
    4042
    4143{{{
     
    5254            </gmd:aggregateDataSetIdentifier>
    5355            <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>
    5558            </gmd:associationType>
    5659            <!-- initiative type describes the type of sibling relationship - in this case the code is a project
    5760                 related to the record that contains this aggregateInformation -->
    5861            <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>
    6064            </gmd:initiativeType>
    6165        </gmd:MD_AggregateInformation>
    6266    </gmd:aggregateInformation>
    6367}}}
    64 An in depth proposal can be found here : link
    65 ...
     68
    6669
    6770=== Backwards Compatibility Issues ===