Changes between Version 7 and Version 8 of ISO2ebRIM


Ignore:
Timestamp:
03/22/09 03:13:14 (16 years ago)
Author:
heikki
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ISO2ebRIM

    v7 v8  
    33author: Heikki Doeleman
    44
    5 This page describes GeoNetwork's implementation of the transformation of ISO19139 metadata to ebRIM data. This is specified in OGC 07-038, section F.
     5This page describes GeoNetwork's implementation of the transformation of ISO19139 metadata to ebRIM data. This is specified in [http://portal.opengeospatial.org/files/?artifact_id=20596 OGC 07-038], section F.
    66[[BR]]
    77
    … …  
    1010== Introduction ==
    1111
    12 The specification in OGC 07-038 section F about how to register ISO metadata in a ebRIM registry is rather obscure. I will attempt to describe the process on this page. The implementation in GeoNetwork is in the form of an XSLT transformation. The input for this transformation is an ISO19139 metadata document; the output is a list of ebRIM !RegistryObjects, of various types. The !RegistryObjects created by this transformation receive unique IDs, but since these are not UUIDs (as they should be) the result of the transformation is post-processed in Java, where they are replaced by newly generated UUIDs.
     12The specification in [http://portal.opengeospatial.org/files/?artifact_id=20596 OGC 07-038] section F about how to register ISO metadata in a ebRIM registry is rather obscure. I will attempt to describe the process on this page. The implementation in GeoNetwork is in the form of an XSLT transformation. The input for this transformation is an ISO19139 metadata document; the output is a list of ebRIM !RegistryObjects, of various types. The !RegistryObjects created by this transformation receive unique IDs, but since these are not UUIDs (as they should be) the result of the transformation is post-processed in Java, where they are replaced by newly generated UUIDs.
    1313
    1414A list of uncertainties about the interpretation of this specification is [wiki:ISO2ebRIMIssues here].
    … …  
    1616----
    1717
    18 == The transformation of ISO 19139 to ebRIM ==
     18== The transformation of ISO19139 to ebRIM ==
    1919
    2020The transformation takes the following actions :
    … …  
    27272. an Extrinsic Object '!DataMetadata' or '!ServiceMetadata'. This depends on the presence of either gmd:MD_metadata/gmd:identificationInfo/gmd:MD_DataIdentification or gmd:MD_metadata/gmd:identificationInfo/gmd:MD_ServiceIdentification (in both cases '!DataMetadata' is created) or gmd:MD_metadata/gmd:identificationInfo/srv:SV_ServiceIdentification ('!ServiceMetadata' is created).
    2828
    29 The transformation does this for each gmd:identificationInfo; the caller of the transformation is supposed to check the 1..1 cardinality on that element imposed by the CIM profile in section F.3.1.
     29The transformation does this for each gmd:identificationInfo; the caller of the transformation is supposed to check the 1..1 cardinality on that element imposed by the [http://portal.opengeospatial.org/files/?artifact_id=20596 CIM profile] in section F.3.1.
    3030
    31313. if gmd:parentIdentifier is present, a second '!MetadataInformation' is created representing the parent.