Copyright © 2014 Open Geospatial Consortium
79 Further an instance of Person is created for the same instance of
gmd:MD_Metadatagmd:contact where is CI_ResponsibleParty or an element in its substitutionGroup – see before have a none empty gmd:individualName. This Person
instance is then assigned to the Organization by referencing the Person´s id-Attribute in the Organization´s “primaryContact” attribute. The mapping between the CI_ResponsibleParty
property and the Person property is given in the table below. If there is already a matching Person registry object, a new one shall not be created: the reference can just be used as
described before.
Table 52: - From CI_ResponsibleParty to Person
ISO 1911519115-219119 I15
Comments
gmd:individualNamegco:CharacterString Attribute lastName of
element PersonName
11.2.3 Instance of MetadataInformation for the parent resource
Two cases have to be considered: 1. The parent resource has already been registered i.e., there is already a
MetadataInformation extrinsic object having an Identifier slot instance matching the parentIdentifier property of MD_Metadata. In that case, the ResourceMetadata
extrinsic object of the current metadata record has to be associated to the existing parent MetadataInformation extrinsic object through a ParentMetadataInformation
association.
2. The parent resource has not been registered yet. In that case, a MetadataInformation extrinsic object has to be created accordingly to Table 53 along with a
ParentMetadataInformation association.
Table 53: MetadataInformation extrinsic object related to the parent resource
ISO 1911519115-219119 I15
Comments
gmd:MD_Metadatagmd:parentIdentifier slot Identifier
Concerns the second instance of MetadataInformation, when parentIdentifier is
instantiated in the metadata
11.2.4 Instance of ResourceMetadata
Some properties of MD_Metadata are mapped to the abstract Extrinsic Object ResourceMetadata and are used to populate the instance of the Extrinsic Objects derived from
DataMetadata or the Extrinsic Object ServiceMetadata created for the first instance of MD_Metadata.identificationInfo. This mapping is defined in Table 54.
Table 54: Metadata properties handled by the ResourceMetadata ExtrinsicObject
ISO 1911519115-219119 I15
Comments
gmd:MD_Metadatagmd:hierarchyLevel ExtrinsicObject
ResourceMetadata see column Comments
Depending on the hierarchyLevel an instance of
“ElementaryDataset”,
Copyright © 2014 Open Geospatial Consortium
80
ISO 1911519115-219119 I15
Comments “DatasetCollection”,
“ServiceMetadata” or “Application” all are subclasses
of ResourceMetadata has to be created. This is done by
referencing one of corresponding node in the
ObjectType classification schema. See also 11.3.1.
gmd:MD_Metadatagmd:hierarchyLevelName slot Type
For each instance of the property.
gmd:MD_Metadatagmd:referenceSystemInfo See Clause 11.6
For each instance of the property
gmd:MD_Metadatagmd:identificationInfo See Clause 11.3
For the first instance of the property
gmd:MD_Metadatagmd:distributionInfogmd:M D_Distributiongmd:distributorgmd:MD_Distribut
orgmd:distributorFormatgmd:MD_Format or
gmd:MD_Metadatagmd:distributionInfogmd:M D_Distributiongmd:distributionFormatgmd:MD_
Format slot Format
For each instance a slot value will be created.
The slot type is a two-level classification that manages both
the format name gmd:name and the format version
gmd:version.
gmd:MD_Metadatagmd:distributionInfogmd:M D_Distributiongmd:transferOptionsgmd:MD_Dig
italTransferOptionsgmd:onLinegmd:CI_OnlineR esourcegmd:linkagegmd:URL
or gmd:MD_Metadatagmd:distributionInfogmd:M
D_Distributiongmd:distributorgmd:MD_Distribut orgmd:distributorTransferOptionsgmd:MD_Digit
alTransferOptionsgmd:onLinegmd:CI_OnlineRe sourcegmd:linkagegmd:URL
slot Source This mapping is not applicable
to the
ExtrinsicObject ServiceMetadata see below.
For an Application the onLine link will be found here.
gmd:MD_Metadatagmd:dataQualityInfo See Clause 11.4
11.3 Registration of the information resources
11.3.1 Preamble
Each instance of MD_Metadata.identificationInfo describes an information resource concerned by the metadata record. In this profile, the cardinality of this property is restricted
to 1..1 for the ISO 19139 metadata files stored in the ebRIM Repository. The restriction on this cardinality makes it easier to manage the associations between the registry objects and
repository items. Besides, it is compliant with the ISO 1911519119 Application Profile of CS-W [OGC 07-045].
In the following it is described how to deduce an information resource from ISO 19139 metadata including the possible associations:
- ElementaryDataset, if MD_Metadata.hierarchyLevel is set to ‘dataset’. In this case,
the metadata record must contain one property Metadata.identificationInfo of type MD_DataIdentification or one of its subtypes
