2.3. identificationInfo Node

The gmd:identificationInfo node groups different pieces of information corresponding mainly to the Dataset Information Model element properties.

Figure 2.2. Children nodes of the identificationInfo node

Children nodes of the identificationInfo node

The following contents of this section describes the children XML nodes of the identificationInfo node that are used to implement the Model.

According to the SC5 of the INSPIRE Directive, only the first instance of the identificationInfo node is considered in the scope of an INSPIRE-conform XML document.

2.3.1. citation Node

The gmd:citation node groups the most general information about the dataset: its name, publication date and other possible identifiers.

2.3.1.1. title Node

The gmd:title node specifies the Name property of the Dataset Information element.

Table 2.14. title node description

ESPON MetadataReferenceSection 1.3.1.1
NameName
ISO 19115Namegmd:title
XPath/gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/*/gmd:title/gco:CharacterString
Observations 

<gmd:identificationInfo>
<gmd:MD_DataIdentification>
<gmd:citation>
<gmd:CI_Citation>
<gmd:title>
<gco:CharacterString>
Climate Change Data
</gco:CharacterString>
</gmd:title>
</gmd:CI_Citation>
</gmd:citation>
[...]
</gmd:MD_DataIdentification> </gmd:identificationInfo>

2.3.1.2. date Node

The gmd:date node specifies the dates associated with the dataset. This is a property belonging to the Temporal Reference property of the Dataset Information element and may correspond to the Upload, Creation or Revision date of the dataset. This means that for import metadata, when the dataset is sent for the first time to the data processors, the Upload or Creation date may be specified. If the data provider makes a correction in a dataset already uploaded, a Revision date should be added to the list of dates.

According to the SC7 of the INSPIRE Directive, no more than one Creation date can be specified.

Table 2.15. date node description

ESPON MetadataReference Section 1.3.1.12.2 or Section 1.3.1.12.3 or Section 1.3.1.12.4
Name Upload Date or Creation Date or Revision Date
ISO 19115Namegmd:date
XPath/gmd:MD_Metadata/gmd:identificationInfo/*/gmd:CI_Citation/gmd:date/*/gco:Date
Observations 

<gmd:identificationInfo>
<gmd:MD_DataIdentification>
<gmd:citation>
<gmd:CI_Citation>
<gmd:title [...] />
<gmd:date>
<gmd:CI_Date>
<gmd:date>
<gco:Date>
2011-08-31
</gco:Date>
</gmd:date>
<gmd:dateType>
<!-- example for a revision date: for other types change
the codeListValue and the text content of the node -->

<gmd:CI_DateTypeCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode"
codeListValue="revision">

revision
</gmd:CI_DateTypeCode>
</gmd:dateType>
</gmd:CI_Date>
</gmd:date>
<!-- other dates may follow here -->
</gmd:CI_Citation>
</gmd:citation>
[...]
</gmd:MD_DataIdentification> </gmd:identificationInfo>

2.3.1.3. identifier Node

The gmd:identifier node corresponds to the Unique Resource Identifier property of the Dataset Information element. This property is required by the INSPIRE directive and is requested by the SC8.

Table 2.16. identifier node description

ESPON MetadataReferenceSection 1.3.1.6
NameUnique Resource Identifier
ISO 19115Namegmd:identifier
XPath/gmd:MD_Metadata/gmd:identificationInfo/*/gmd:citation/*/gmd:identifier/*/gmd:code/*/gco:CharacterString
Observations

Generally, the expected value of this node should correspond to the one described in Section 1.3.1.6. Therefore, it can be defined using the RS_Identifier ISO 19115 node, that allows to specify additionaly the codeSpace and version values, that can be useful in the case of multiple documents having similar identifiers. Please see the ISO-19115 documentation (part B.2.7.3) for details on this node.


<gmd:identificationInfo>
<gmd:MD_DataIdentification>
<gmd:citation>
<gmd:CI_Citation>
<gmd:title [...] />
<gmd:date [...] />
<gmd:identifier>
<gmd:MD_Identifier>
<gmd:code>
<gco:CharacterString>
DEMIFER_LaborForce_2011_v2_corrected
</gco:CharacterString>
</gmd:code>
</gmd:MD_Identifier>
</gmd:identifier>
[...]
</gmd:CI_Citation>
</gmd:citation>
[...]
</gmd:MD_DataIdentification>
</gmd:identificationInfo>

2.3.1.4. collectiveTitle Node

The gmd:collectiveTitle node corresponds to the Project property of the Dataset Information element.

Table 2.17. collectiveTitle node description

ESPON MetadataReferenceSection 1.3.1.2
NameProject
ISO 19115Namegmd:collectiveTitle
XPath/gmd:MD_Metadata/gmd:identificationInfo/*/gmd:citation/*/gmd:collectiveTitle/gco:CharacterString
Observations 

<gmd:identificationInfo>
<gmd:MD_DataIdentification>
<gmd:citation>
<gmd:CI_Citation>
<gmd:title [...] />
<gmd:date [...] />
<gmd:collectiveTitle>
<gco:CharacterString>
ESPON 2013 Database Project
</gco:CharacterString>
</gmd:collectiveTitle>
</gmd:CI_Citation>
</gmd:citation>
[...]
</gmd:MD_DataIdentification>
</gmd:identificationInfo>

2.3.2. abstract Node

The gmd:abstract node corresponds to the respective property of the Dataset Information element.

Table 2.18. abstract node description

ESPON MetadataReferenceSection 1.3.1.3
NameAbstract
ISO 19115Namegmd:abstract
XPath/gmd:MD_Metadata/gmd:identificationInfo/*/gmd:abstract/gco:CharacterString
Observations 

<gmd:identificationInfo>
<gmd:MD_DataIdentification>
<gmd:citation [...] />
<gmd:abstract>
<gco:CharacterString>
Contains data on internal migration trends and demographic changes
on NUTS3 level for all European countries, from 2010 to 2015.
</gco:CharacterString>
</gmd:abstract>
[...]
</gmd:MD_DataIdentification>
</gmd:identificationInfo>

2.3.3. pointOfContact Node

The gmd:pointOfContact node is mandatory according to the SC14 of the INSPIRE Directive. This node may have multiple occurences and the first of them represents the main contact point for the entire dataset, that is to say the Responsible Party property of the Dataset Information element. The next gmd:pointOfContact nodes correspond to secondary contact points of the dataset, listed by the Point of Contact property.

Table 2.19. pointOfContact node description

ESPON MetadataReferenceSection 1.3.1.16 and Section 1.3.1.19
Name Responsible Party and Points of Contact
ISO 19115Namegmd:pointOfContact
XPath/gmd:MD_Metadata/gmd:identificationInfo/*/gmd:pointOfContact/gmd:CI_ResponsibleParty
Observations 

<gmd:identificationInfo>
<gmd:MD_DataIdentification>
<gmd:citation [...] />
<gmd:abstract [...] />
<gmd:pointOfContact>
<!-- this contact point is mandatory! -->
<gmd:CI_ResponsibleParty>
<!-- the contents is similar to the <gmd:CI_ResponsibleParty>
in <gmd:contact> of the metadata root node -->

</gmd:CI_ResponsibleParty>
</gmd:pointOfContact>
<!-- here may follow other contact points of the dataset -->
[...]
</gmd:MD_DataIdentification>
</gmd:identificationInfo>

2.3.4. descriptiveKeywords Node

The gmd:descriptiveKeywords node groups the keywords associated with the entire dataset, belonging to the same originating vocabulary. All keywords must be grouped according to their vocabularies and there must be at least one keyword group (with at least one keyword) coming from the GEMET thesaurus, in respect of the SC17 of the INSPIRE Directive.

Table 2.20. gmd:descriptiveKeywords node description

ESPON MetadataReferenceSection 1.3.1.11 and Section 1.7.3
NameKeyword
ISO 19115Namegmd:descriptiveKeywords
XPath/gmd:MD_Metadata/gmd:identificationInfo/*/gmd:descriptiveKeywords
Observations

Please note that the originating vocabulary is referenced using a gmd:CI_Citation node.


<gmd:identificationInfo>
<gmd:MD_DataIdentification>
<gmd:citation [...] />
<gmd:abstract [...] />
<gmd:pointOfContact [...] />
<gmd:descriptiveKeywords>
<gmd:MD_Keywords>
<gmd:keyword>
<gco:CharacterString>
Land cover
</gco:CharacterString>
</gmd:keyword>
<!-- other keywords from the same originating vocabulary may follow here -->
<!-- if the originating vocabulary is not cited, these keywords will be "free" -->
<gmd:thesaurusName>
<gmd:CI_Citation>
<gmd:title>
<gco:CharacterString>
GEMET - INSPIRE themes, version 1.0
</gco:CharacterString>
</gmd:title>
<gmd:date>
<gmd:CI_Date>
<gmd:date>
<gco:Date>
2008-06-01
</gco:Date>
</gmd:date>
<gmd:dateType>
<gmd:CI_DateTypeCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode"
codeListValue="publication">

publication
</gmd:CI_DateTypeCode>
</gmd:dateType>
</gmd:CI_Date>
</gmd:date>
</gmd:CI_Citation>
</gmd:thesaurusName>
</gmd:MD_Keywords>
</gmd:descriptiveKeywords>
<!-- other groups of keywords from another vocabularies may follow here -->
[...]
</gmd:MD_DataIdentification>
</gmd:identificationInfo>

2.3.5. resourceConstraints Node

The resourceConstraints node is require by the SC12 and corresponds to the Constraints property of the Dataset Information element. In terms of the ISO 19115 standard, the Constraints property can be specified using two instances of the resourceConstraints node. The first one is dedicated to define the restrictions of the dataset use. The second specifies the classification of the access to the dataset.

2.3.5.1. useConstraints and otherConstraints Nodes

The gmd:useConstraints and gmd:otherConstraints nodes correspond respectively to the Use Constraint and Other Constraints properties of the Model.

Table 2.21. gmd:useConstraints and gmd:otherConstraints nodes description

ESPON MetadataReferenceSection 1.3.1.15.1 and Section 1.3.1.15.3
Name Use Constraint and Other Constraints
ISO 19115Namegmd:useConstraints and gmd:otherConstraints
XPath/gmd:MD_Metadata/gmd:identificationInfo/*/gmd:resourceConstraints/gmd:MD_LegalConstraints
Observations 

<gmd:identificationInfo>
<gmd:MD_DataIdentification>
<gmd:citation [...] />
<gmd:abstract [...] />
<gmd:pointOfContact [...] />
<gmd:descriptiveKeywords [...] />
<gmd:resourceConstraints>
<gmd:MD_LegalConstraints>
<gmd:useConstraints>
<gmd:MD_RestrictionCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#MD_RestrictionCode"
codeListValue="copyright">

copyright
</gmd:MD_RestrictionCode>
</gmd:useConstraints>
<gmd:otherConstraints>
<gco:CharacterString>
no limitations
</gco:CharacterString>
</gmd:otherConstraints>
</gmd:MD_LegalConstraints>
</gmd:resourceConstraints>
[...]
</gmd:MD_DataIdentification>
</gmd:identificationInfo>

2.3.5.2. useLimitation and classification Nodes

The gmd:classification node corresponds to the Access Classification property of the Model and the gmd:useLimitation one corresponds to the Access Condition property. The gmd:classification node must be used inside a gmd:MD_SecurityConstraints node and corresponds to the Access Classification property of the Model. The gmd:useLimitation may be used as the first child of the gmd:MD_SecurityConstraints node, but also can be placed as the first child of the gmd:MD_LegalConstraints node used in the Section 2.3.5.1.

Table 2.22. gmd:classification and gmd:useLimitation nodes description

ESPON MetadataReferenceSection 1.3.1.15.2 and Section 1.3.1.15.4
Name Access Condition and Access Classification
ISO 19115Namegmd:useLimitation and gmd:classification
XPath/gmd:MD_Metadata/gmd:identificationInfo/*/gmd:resourceConstraints/gmd:MD_SecurityConstraints
Observations 

<gmd:identificationInfo>
<gmd:MD_DataIdentification>
<gmd:citation [...] />
<gmd:abstract [...] />
<gmd:pointOfContact [...] />
<gmd:descriptiveKeywords [...] />
<gmd:resourceConstraints [...] />
<gmd:resourceConstraints>
<gmd:MD_SecurityConstraints>
<!-- this node may be placed as the first child of the previous gmd:resourceConstraints node -->
<gmd:useLimitation>
<gco:CharacterString>
No conditions apply
</gco:CharacterString>
</gmd:useLimitation>
<gmd:classification>
<gmd:MD_ClassificationCode
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml#MD_ClassificationCode"
codeListValue="unclassified">

unclassified
</gmd:MD_ClassificationCode>
</gmd:classification>
</gmd:MD_SecurityConstraints>
</gmd:resourceConstraints>
[...]
</gmd:MD_DataIdentification>
</gmd:identificationInfo>

2.3.6. language Node

The gmd:language node of the identificationInfo section corresponds to the Dataset Language property of the model (not to be confused with the Metadata Language described in the Section 2.2.2). The value of this node is constant for any ESPON dataset. This node is the SC9 of the INSPIRE Directive.

Table 2.23. gmd:language node description

ESPON MetadataReferenceSection 1.3.1.7
NameDataset Language
ISO 19115Namegmd:language
XPath/gmd:MD_Metadata/gmd:identificationInfo/*/gmd:language/gmd:[email protected]
Observations


<gmd:identificationInfo>
<gmd:MD_DataIdentification>
<gmd:citation [...] />
<gmd:abstract [...] />
<gmd:pointOfContact [...] />
<gmd:descriptiveKeywords [...] />
<gmd:resourceConstraints [...] />
<gmd:resourceConstraints [...] />
<gmd:language>
<gmd:LanguageCode
codeList="http://www.loc.gov/standards/iso639-2/"
codeListValue="eng">

eng
</gmd:LanguageCode>
</gmd:language>
[...]
</gmd:MD_DataIdentification>
</gmd:identificationInfo>

2.3.7. topicCategory node

The gmd:topicCategory node corresponds to the Topic Category property of the Dataset Information element. There must be at least one topic category defined for a dataset.

Table 2.24. gmd:topicCategory node description

ESPON MetadataReferenceSection 1.3.1.10
NameTopic Category
ISO 19115Namegmd:topicCategory
XPath/gmd:MD_Metadata/gmd:identificationInfo/*/gmd:topicCategory/gmd:MD_TopicCategoryCode
Observations 

<gmd:identificationInfo>
<gmd:MD_DataIdentification>
<gmd:citation [...] />
<gmd:abstract [...] />
<gmd:pointOfContact [...] />
<gmd:descriptiveKeywords [...] />
<gmd:resourceConstraints [...] />
<gmd:resourceConstraints [...] />
<gmd:language [...] />
<gmd:topicCategory>
<gmd:MD_TopicCategoryCode>
society
</gmd:MD_TopicCategoryCode>
</gmd:topicCategory>
<!-- other topic categories may follow here -->
[...]
</gmd:MD_DataIdentification>
</gmd:identificationInfo>

2.3.8. extent Node

The gmd:extent node is shared both by the Spatial Binding element and the Temporal Reference property of the Dataset Information element. This node is detailed in the Section 2.5.