1.3. Dataset Information Element

The Dataset Information element is a composite element, the root of the entire metadata model. It wraps all the properties used to describe an ESPON Dataset.

Table 1.2. Dataset Information element description

ESPON MetadataNameDataset Information
Name literalDatasetInformation
ParentNone. This is the root element of the Abstract Metadata Model, it does not have parents.
Obligation / conditionMandatory
Multiplicity1
Description

Gives the most general information about the data produced by an ESPON project. Wraps all the elements that represent the metadata of an ESPON dataset.

Data typeThis is a composite element grouping sub-elements and properties
Example(s)-
INSPIREReferencePart B 1
NameMD_Metadata
Observations 

1.3.1. Properties of the Dataset Information Element

A Dataset Information element can be described with the properties explained in the following sections.

1.3.1.1. Name Property

Table 1.3. Name property description

ESPON MetadataNameName
Name literalName
ParentDataset Information
Obligation / conditionMandatory
Multiplicity1
Description Name of the dataset. This is a brief expression that gives an idea about the dataset contents. We encourage all dataset providers to produce the most short and meaningful dataset names that reflect directly the data semantics.
Data typeCharacter string with max length of 128 characters
Example(s)"Demographic trends", "Climate Change Data"
INSPIREReferencePart B 1.1
NameResource title
ObservationsThis property should not have a length of more than 150 characters.

1.3.1.2. Project Property

Table 1.4. Project property description

ESPON MetadataNameProject
Name literalProject
ParentDataset Information
Obligation / conditionMandatory
Multiplicity1
Description ESPON project in which the dataset was produced. This must be an acronym of one of existing ESPON projects. Please consult the possible values of acronyms for all referenced ESPON projects in Appendix C.
Data typeCharacter string with max length of 32 characters
Example(s)"DEMIFER", "TIPTAP"
INSPIREReferenceNo INSPIRE reference
NamecollectiveTitle
Observations 

1.3.1.3. Abstract Property

Table 1.5. Abstract property description

ESPON MetadataNameAbstract
Name literalAbstract
ParentDataset Information
Obligation / conditionMandatory
Multiplicity1
Description Free-text description of the contents of the dataset, in a more detailed way than it can be made by the name of the dataset.
Data typeCharacter string with max length of 1024 characters
Example(s)Contains data on internal migration trends and demographic changes on NUTS3 level for all European countries, from 2010 to 2015.
INSPIREReferencePart B 1.2
NameResource abstract
Observations

This property must not duplicate the expression used in the name of the dataset. It should provide more detailed information on the contents than the Name property.


1.3.1.4. Resource Type Property

Table 1.6. Resource type property description

ESPON MetadataNameResource Type
Name literalResourceType
ParentDataset Information
Obligation / conditionMandatory
Multiplicity1
DescriptionType of the resource. This property is a requirement of the INSPIRE Directive. For any ESPON dataset, the value of this property must always be "dataset".
Data typeCharacter string
Example(s)"dataset"
INSPIREReferencePart B 1.3
NameResource Type
ObservationsThis property is a constant value that must be present in the metadata.

1.3.1.5. Resource Locator Property

Table 1.7. Resource locator property description

ESPON MetadataNameResource Locator
Name literalResourceLocator
ParentDataset Information
Obligation / conditionOptional
Multiplicity0... *
Description

If the dataset has a public URL, it must be mentioned in the metadata so as the users could "obtain more information on the resource and/or access services".

The URL value of this property must point to the location where the dataset and/or its documentation are published.

Data typeURL with max length of 256 characters
Example(s)http://www.espon.eu/report/report001.pdf
INSPIREReferencePart B 1.4
NameResource locator
Observations

According to the INSPIRE Metadata Implementing Rules, page 17, if a URL for the resource exists, it must be mentioned in the metadata.


1.3.1.6. Unique Resource Identifier Property

Table 1.8. Unique Resource Identifier property description

ESPON MetadataNameUnique Resource Identifier
Name literalUniqueResourceIdentifier
ParentDataset Information
Obligation / conditionMandatory
Multiplicity1
DescriptionCode that represents a unique identification of the dataset. Please see the observations below for the recommended URI code scheme.
Data typeCharacter string with max length of 256 characters
Example(s)"DEMIFER_LaborForce_v2_20111021_corrected"
INSPIREReferencePart B 1.5
NameUnique resource identifier
Observations

The recommended value for this property should be a merged character string referring to the originating project, shortened dataset name, publication date and version, for example: {ProjectAcronym}_{DatasetName}_{UploadOrCreationDate}_{version}[_{OtherOptionalInfo}]. This value must contain only alphanumeric characters, the spaces must be replaced with underscores. The value of this property should be used as the main component for the names of the files related with the dataset.


1.3.1.7. Dataset Language Property

Table 1.9. Dataset Language property description

ESPON MetadataNameDataset Language
Name literalDatasetLanguage
ParentDataset Information
Obligation / conditionMandatory
Multiplicity1
DescriptionISO/TS 19139 alpha-3 (three characters) code denoting the language in which the textual information of the dataset is presented. According to ESPON working languages, the only value for this property is "eng" and the only language of the textual information in ESPON datasets is the English language.
Data typeCharacter string of 3 characters
Example(s)"eng"
INSPIREReferencePart B 1.7
NameResource language
ObservationsThis property is a constant value that must be present in the metadata.

1.3.1.8. Metadata Language Property

Table 1.10. Metadata Language property description

ESPON MetadataNameMetadata Language
Name literalMetadataLanguage
ParentDataset Information
Obligation / conditionMandatory
Multiplicity1
DescriptionISO/TS 19139 alpha-3 (three characters) code denoting the language in which the textual information of the metadata is presented. According to ESPON working languages, the only value for this property is "eng" and the only language of the textual information in the metadata is the English language.
Data typeCharacter string of 3 characters
Example(s)"eng"
INSPIREReferencePart B 10.3
NameMetadata language
Observations This property is a constant value that must be present in the metadata. It represents a so-called "metadata on metadata". It describes the metadata, but not the dataset.

1.3.1.9. Metadata Date Property

Table 1.11. Metadata Date property description

ESPON MetadataNameMetadata Date
Name literalMetadataDate
ParentDataset Information
Obligation / conditionMandatory
Multiplicity1
DescriptionDate when the metadata for this dataset was created. This is a requirement of the INSPIRE Directive.
Data typeDate
Example(s)2011-08-21
INSPIREReferencePart B 10.2
NameMetadata date
Observations

This property represents a so-called "metadata on metadata". It describes the metadata, but not the dataset. Please see the Calendar Date Values Constraints for dates format.


1.3.1.10. Topic Category Property

Table 1.12. Topic Category property description

ESPON MetadataNameTopic Category
Name literalTopicCategory
ParentDataset Information
Obligation / conditionMandatory
Multiplicity1... *
DescriptionGeneric theme(s) associated with the dataset. The theme must be taken from the INSPIRE Directive theme list available in Appendix F. At least one code of Table F.1 must be specified. The maximum number of topic categories is bound to the 19 currently existing ones.
Data typeCharacter string restricted to a list of values
Example(s)"Society", "Transportation", "Health"
INSPIREReferencePart B 2.1
NameTopic category
ObservationsThe topic categories defined in INSPIRE Directive are different from the ones of the ESPON Thematic Classification and must not be confused. At Dataset Information level, the INSPIRE topic categories must be applied, while the ESPON classification is used on Indicator Identification level.

1.3.1.11. Keyword Property

Table 1.13. Keyword property description

ESPON MetadataNameKeyword
Name literalKeyword
ParentDataset Information
Obligation / conditionMandatory
Multiplicity1... *
DescriptionPlease see the shared Keyword property.
Data typeThis is a composite property
Example(s)-
INSPIREReferencePart B 3
NameKeyword
Observations 

1.3.1.12. Temporal Reference Composite Property

This composite property covers several values grouped because they all correspond to temporal references of the dataset.

Table 1.14. Temporal Reference property description

ESPON MetadataNameTemporal Reference
Name literalTemporalReference
ParentDataset Information
Obligation / conditionMandatory
Multiplicity1
Description Groups values representing temporal bindings of the entire dataset. These bindings are the union of all the time periods covered by the indicator values, the date when the dataset was uploaded on the ESPON Web server and, optionaly, the dates of creation and revision of the dataset.
Data typeThis is a composite property
Example(s)-
INSPIREReferencePart B 5
NameTemporal Reference
Observations 

The Temporal Reference composite property define Temporal Extent, Upload Date, Creation Date and Revision Date properties.

1.3.1.12.1. Temporal Extent Property

The Temporal Extent property at the Dataset Information level defines the global temporal extent of all the indicator values present in the dataset. This is the start and the end marks of the union of all the time periods covered by the indicator values. For example, if the indicator values existing in the dataset cover the years 2005, 2006, 2007 and 2008, the TemporalExtent property must have the value [2005, 2008].

Table 1.15. Temporal Extent property description

ESPON MetadataNameTemporal Extent
Name literalTemporalExtent
ParentTemporal Reference
Obligation / conditionMandatory
Multiplicity1
Description

Please see the Temporal Extent shared property description.

Data typeList of one or two dates: [startDate[, endDate]]
Example(s)[2001-01-01, 2020-12-31]
INSPIREReferencePart B 5.1
NameTemporal extent
Observations

Please see the Calendar Date Values Constraints for dates format.


1.3.1.12.2. Upload Date Property

Table 1.16. Upload date property description

ESPON MetadataNameUpload Date
Name literalUploadDate
ParentTemporal Reference
Obligation / conditionMandatory
Multiplicity1
Description Date when this dataset was uploaded to the ESPON server. This date is considered to be equivalent to the publication date of the dataset.
Data typeDate
Example(s)'2010-10-31', '2011-08-12', '2012-01-01'
INSPIREReferencePart B 5.2
Namedate
Observations

Please see the Calendar Date Values Constraints for dates format.

An upload date is considered to be equivalent to a publication date.


1.3.1.12.3. Creation Date Property

Table 1.17. Creation Date property description

ESPON MetadataNameCreation Date
Name literalCreationDate
ParentTemporal Reference
Obligation / conditionOptional
Multiplicity0... 1
DescriptionThe date when the dataset was created.
Data typeDate
Example(s)2011-08-19
INSPIREReferencePart B 5.4
NameDate of creation
Observations

Please see the Calendar Date Values Constraints for dates format.


1.3.1.12.4. Revision Date Property

Table 1.18. Revision Date property description

ESPON MetadataNameRevision Date
Name literalRevisionDate
ParentTemporal Reference
Obligation / conditionOptional
Multiplicity0... 1
DescriptionDate of the last revision of the dataset. For a dataset that has never had a revision, this date may be dropped.
Data typeDate
Example(s)2011-08-19
INSPIREReferencePart B 5.3
NameDate of last revision
Observations

Please see the Calendar Date Values Constraints for dates format.


1.3.1.13. Lineage Property

Table 1.19. Lineage property description

ESPON MetadataNameLineage
Name literalLineage
ParentDataset Information
Obligation / conditionMandatory
Multiplicity1
DescriptionGeneral explanation of the data producer’s knowledge about the lineage of the dataset.
Data typeCharacter string without length restriction
Example(s)

This dataset was produced by aggregating data from the following sources: [...]. After the data aggregation, they were checked with [...] and processed by [...]. The missing indicator values have been interpolated using the method of [...]. The data was then validated by [...].

INSPIREReferencePart B 6.1
NameLineage
Observations

This property is required by the INSPIRE Directive and must provide a general description of the lineage for the entire dataset.


1.3.1.14. Conformity Composite Property

Table 1.20. Conformity composite property description

ESPON MetadataNameConformity
Name literalConformity
ParentDataset Information
Obligation / conditionOptional
Multiplicity0... *
DescriptionInformation on the degree of conformity with the implementing rules provided in Art.7-1 of INSPIRE Directive.
Data typeThis is a composite property
Example(s)-
INSPIREReferencePart B 7
NameConformity
Observations

If the conformity of the data and/or the metadata was evaluated against one or more specifications, the results of the evaluations must be provided by the Conformity property. Otherwise the data and the metadata are considered to be not evaluated. Please see the p. 2.8 of the INSPIRE Metadata Implementing Rules[2].


The Conformity property groups three properties: Conformance, Specification and Specification Date.

1.3.1.14.1. Conformance Property

Table 1.21. Conformance property description

ESPON MetadataNameConformance
Name literalConformance
ParentConformity
Obligation / conditionMandatory
Multiplicity1
DescriptionShows if the data and/or metadata are conformant to the cited specification.
Data typeBoolean
Example(s)true, false
INSPIREReferencePart B 7.2
NameDegree
Observations 

1.3.1.14.2. Specification Property

Table 1.22. Specification property description

ESPON MetadataNameSpecification
Name literalSpecification
ParentConformity
Obligation / conditionMandatory
Multiplicity1
DescriptionTitle of the specification against which the data and/or metadata were evaluated.
Data typeCharacter string with max length of 128 characters
Example(s)"INSPIRE Metadata Implementing Rules"
INSPIREReferencePart B 7.1
NameSpecification
Observations 

1.3.1.14.3. Specification Date Property

Table 1.23. Specification Date property description

ESPON MetadataNameSpecification Date
Name literalSpecifDate
ParentConformity
Obligation / conditionMandatory
Multiplicity1
DescriptionDate when the conformity check against the cited specification was made.
Data typeDate
Example(s)2011-05-12
INSPIREReferencePart B 7.1
NameSpecification
Observations

Please see the Calendar Date Values Constraints for dates format.


1.3.1.15. Constraints Composite Property

Table 1.24. Constraints composite property description

ESPON MetadataNameConstraints
Name literalConstraints
ParentDataset Information
Obligation / conditionMandatory
Multiplicity1... *
DescriptionDefines the use and access constraints applied to the entire dataset. This property is required by the INSPIRE Directive.
Data typeThis is a composite property
Example(s)-
INSPIREReferencePart B 8
NameConstraint Related To Access And Use
Observations 

The Constraints property wraps four values: Use Constraint, Access Condition, Other Constraints and Access Classification.

1.3.1.15.1. Use Constraint Property

Table 1.25. Use Constraint property description

ESPON MetadataNameUse Constraint
Name literalUseConstraint
ParentConstraints
Obligation / conditionMandatory
Multiplicity1
DescriptionAccess and use constraints applied to ensure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the resource.
Data typeCharacter string restricted to a list of values
Example(s)"Copyright", "Patent", "Trademark"
INSPIREReferencePart B 8.2
NameLimitations on public access
ObservationsAccording to [7], the following values can be applied to the Use Constraint property:
  • copyright - exclusive right to the publication, production, or sale of the rights to a literary, dramatic, musical, or artistic work, or to the use of a commercial print or label, granted by law for a specified period of time to an author, composer, artist, distributor.

  • patent - government has granted exclusive right to make, sell, use or license an invention or discovery.

  • patentPending - produced or sold information awaiting a patent.

  • trademark - a name, symbol, or other device identifying a product, officially registered and legally restricted to the use of the owner or manufacturer.

  • license - formal permission to do something.

  • intellectualPropertyRights - rights to financial benefit from and control of distribution of non-tangible property that is a result of creativity.

  • restricted - withheld from general circulation or disclosure.

  • otherRestrictions - limitation not listed


1.3.1.15.2. Access Condition Property

Table 1.26. Access Condition property description

ESPON MetadataNameAccess Condition
Name literalAccessCondition
ParentConstraints
Obligation / conditionMandatory
Multiplicity1
DescriptionTextual description of the conditions to be applied in order to access and/or use the dataset. If no conditions apply, should be set to the no conditions apply value.
Data typeCharacter string without length restriction
Example(s)No conditions apply
INSPIREReferencePart B 8.1
NameCondition applying to access and use
Observations 

1.3.1.15.3. Other Constraints Property

Table 1.27. Other Constraints property description

ESPON MetadataNameOther Constraints
Name literalOtherConstraints
ParentConstraints
Obligation / conditionMandatory
Multiplicity1
DescriptionTextual description of any other constraints and legal prerequisites to access and/or use the dataset. Must be specified especially if the Use Constraint property is set to otherRestrictions value. If no other constraints are applied, must be set to the no limitations value.
Data typeCharacter string without length restriction
Example(s)No limitations
INSPIREReferencePart B 8.2
NameLimitations on public access
Observations 

1.3.1.15.4. Access Classification Property

Table 1.28. Access Classification property description

ESPON MetadataNameAccess Classification
Name literalAccessClassification
ParentConstraints
Obligation / conditionMandatory
Multiplicity1
DescriptionClassification of the access rule applied to the dataset.
Data typeCharacter string restricted to a list of values
Example(s)"unclassified", "restricted", "confidential"
INSPIREReferencePart B 8.2
NameLimitations on public access
ObservationsAccording to [7], the following values can be applied to the Access Classification property:
  • unclassified - available for general disclosure.

  • restricted - not for general disclosure.

  • confidential - available for someone who can be entrusted with information.

  • secret - kept or meant to be kept private, unknown, or hidden from all but a select group of people.

  • topSecret - of the highest secrecy.


1.3.1.16. Responsible Party Property

The Responsible Party property reflects the "identification of, and means of communication with, person and organization associated with the resource" [INSPIRE Metadata Implementing Rules[2], page 44]. That is the contact point that is considered to be responsible for the entire dataset. The Responsible Party property is a requirement of the INSPIRE Directive, Part B 9.

Table 1.29. Responsible Party property description

ESPON MetadataNameResponsible Party
Name literalResponsibleParty
ParentDataset Information
Obligation / conditionMandatory
Multiplicity1
DescriptionOrganization or person responsible for the entire dataset.
Data typeContact
Example(s)-
INSPIREReferencePart B 9.1, part B 9.2
NameResponsible party
Observations 

1.3.1.17. Metadata Contact Property

The Metadata Contact property describes the person who created the metadata for the dataset. This may be the same person as the Responsible Party, but may be a person working on behalf of the responsible party as well. The Metadata Contact property is a requirement of the INSPIRE Directive, Part B 10.1.

Table 1.30. Metadata Contact property description

ESPON MetadataNameMetadata Contact
Name literalMetadataContact
ParentDataset Information
Obligation / conditionMandatory
Multiplicity1
DescriptionOrganization or person who created the metadata for the dataset.
Data typeContact
Example(s)-
INSPIREReferencePart B 10.1
NameMetadata point of contact
ObservationsThe value of the Role property must be set to pointOfContact according to the INSPIRE Directive and ISO 19115 standard.

1.3.1.18. Distributor Property

The Distributor property describes the contact point that is responsible for the distribution of the dataset. In ESPON Metadata, this value is always constant and refers to the ESPON Coordination Unit (ESPON CU) in Luxembourg.

Table 1.31. Distributor property description

ESPON MetadataNameDistributor
Name literalDistributor
ParentDataset Information
Obligation / conditionMandatory
Multiplicity1
DescriptionOrganization that provides the distribution of the dataset. The Address property must be specified for this contact.
Data typeContact
Example(s)-
INSPIREReferenceNo INSPIRE reference
Name-
Observations

This property has a constant value in ESPON Metadata, because according to the Terms and Conditions Agreement [9], the ESPON CU provides the distribution of the data published in the ESPON 2013 Database. This contact property must be the following for any ESPON dataset:

  • individualName: Marjan van Herwijnen

  • organizationName: ESPON Coordination Unit

  • phones: +352545580700, +352545580701

  • email: [email protected]

  • deliveryPoint: UCRP HT - P.O. Box 144

  • city: Esch-sur-Alzette

  • administrativeArea: Cedex 13

  • postalCode: L-4221

  • country: Grand-Duché de Luxembourg


1.3.1.19. Point of Contact Property

This property groups the information specifying all the persons or organizations that participated in the creation of the dataset. This is the only optional Contact property of the Dataset Information element.

Table 1.32. Point of Contact property description

ESPON MetadataNamePointOfContact
Name literalPoint of Contact
ParentDataset Information
Obligation / conditionOptional
Multiplicity0... *
DescriptionPersons or organizations that may be contacted for different issues related to the dataset.
Data typeContact
Example(s)-
INSPIREReferenceNo INSPIRE reference
Name-
Observations 

1.3.1.20. Indicators Aggregation Property

If a dataset contains aggregated indicators, it must refer to all of these aggregations.

Table 1.33. Indicators Aggregation property description

ESPON MetadataNameIndicators Aggregation
Name literalIndicatorsAggregation
ParentDataset Information
Obligation / conditionOptional
Multiplicity0... *
Description References all the indicators aggregations that compose semantic groups of indicators. Please see the Section 1.5.2 for more details.
Data typeA list of Indicator Aggregation elements
Example(s)-
INSPIREReferenceNo INSPIRE reference
Name-
Observations 

1.3.2. Summary of the Dataset Information Element

The Dataset Information element can be summarized by the following UML diagram:

Figure 1.3. Dataset Information element structure

Dataset Information element structure