-
Notifications
You must be signed in to change notification settings - Fork 3
Correspondance TG européen avec le guide national
| INSPIRE Metadata TG v2 | Guide national | Notes |
|---|---|---|
| "TG Requirement C.1: metadata/2.0/req/common/xml-schema -> INSPIRE metadata records shall be encoded in XML format valid against one of the following XML Schemas: - [CSW2 AP ISO] XML Schema13, - [ISO 19139] XML Schema as available in the ISO repository14, or - [ISO 19139] XML Schema as available in the OGC schema repository15. All three of these XML Schemas declare the same namespace http://www.isotc211.org/2005/gmd. The metadata identification info property for INSPIRE Spatial Data Services shall be encoded using the service metadata XML Schema available in the OGC schema repository. This schema is an XML implementation of the [ISO 19119] service metadata, and it declares the namespace http://www.isotc211.org/2005/srv." | Exigence XX | |
| "TG Requirement C.2: metadata/2.0/req/common/root-element | ||
| The metadata for an INSPIRE data set, data set series or service shall be encoded using exactly one gmd:MD_Metadata element as specified in the XML Schema rules and in the TG Requirements of the Conformance Classes in this specification. Additionally the requirements of [ISO 19139], [ISO 19115] and [ISO 19119] shall be followed for describing the metadata records in cases where neither the XML Schemas nor the TG Requirements in this specification require otherwise." | ||
| "TG Requirement C.3: metadata/2.0/req/common/code-list-value | ||
| The code list value shall be encoded using the codeListValue attribute of the relevant ISO 19139 element. The value shall be the identifier of the code list value, as defined in the name column of the tables in [ISO 19115], Annex B." | ||
| "TG Requirement C.4: metadata/2.0/req/common/free-text | ||
| Free text elements of type gco:CharacterString_PropertyType in INSPIRE metadata shall be expressed in one of the following ways: 1. using the gco:CharacterString child element, 2. using gmx:Anchor child element, or 3. re-typing the containing element to gmd:PT_FreeText_PropertyType using the xsi:type attribute and providing both gco:CharacterString and gmd:PT_FreeText child elements. For options 1 and 2 the character string content of elements shall be provided in the language of the metadata. For option 3 the definition of the used locale shall be provided either using an URI pointing to a gmd:MD_Metadata/gmd:locale element within the same document or to an externally provided gmd:PT_Locale element. The character string content shall not be empty unless explicitly allowed in the element specific TG Requirements." | ||
| "TG Requirement 1.2: metadata/2.0/req/datasets-and-series/only-one-md-data-identification | ||
| The first gmd:identificationInfo property of gmd:MD_Metadata element shall contain only one gmd:MD_DataIdentification element for identifying the described INSPIRE data set or data set series." | ||
| "TG Recommendation 1.1: metadata/2.0/rec/datasets-and-series/md-element-id | ||
| The gmd:MD_DataIdentification elements should contain a unique identifier of the element itself to be used for referring from within the Spatial Data Service metadata records to indicate a coupled resource. This identifier should be provided as the value of attribute id of gmd:MD_DataIdentification element. This identifier should be persistent for a particular data set or service, and unique within the all the id elements of the metadata record document and other XML documents it may appear in (like GetRecords responses of Discovery Service). The persistence of the id attributes is important to prevent breaking the coupled resource links between the service metadata and the data set metadata. | ||
| NOTE A unique identifier of the gmd:MD_DataIdentification element is not necessary when building the coupled resource link by providing a Unique Resource Identifier that is resolved to a URL containing an abstract pointer to the gmd:MD_DataIdentification element (see section 4.1.2.4)." | ||
| "TG Requirement C.8: metadata/2.0/req/common/resource-title | ||
| A human readable, non-empty title of the described data set, data set series or service shall be provided. It shall be encoded using the gmd:citation/gmd:CI_Citation/gmd:title element with a Non-empty Free Text Element content in the language of the metadata. The multiplicity of the element is 1." | EXIGENCE INSPIRE E1 : | |
| ● L’intitulé (ou le titre) de la ressource doit être un nom caractéristique et souvent unique sous lequel la ressource est connue. | ||
| ● Cet élément est une chaîne de caractères obligatoire (texte libre) et ne peut pas être répété. | ||
| "TG Recommendation C.3: metadata/2.0/rec/common/resource-title | ||
| The Resource title should be concise and clearly understandable. It should not contain unexplained acronyms or abbreviations. It is recommended a maximum length of 250 characters and keeping the similarity with the original title of the resource, in the sense of the ‘official naming’. | ||
| If the data or service is part of a larger project, it is recommended to indicate the Project at the end of the title, in brackets. In case of Project names, abbreviations are allowed, as long as the rest of the title follows the guidelines above and the abbreviation is spelled out immediately in the abstract." |
"TG Requirement C.9: metadata/2.0/req/common/resource-abstract A non-empty brief narrative summary of the content of the described data set, data set series or service shall be provided. It shall be encoded using the gmd:abstract element with a Non-empty Free Text Element content in the language of the metadata. The multiplicity of this element is 1." "TG Recommendation C.4: metadata/2.0/rec/common/resource-abstract The resource abstract is a succinct description that can include: - A brief summary with the most important details that summarise the data or service - Coverage: linguistic transcriptions of the extent or location in addition to the bounding box - Main attributes - Data sources - Legal references - Importance of the work The most important details of the description should be summarised in the first sentence or the first 256 characters. Unexplained acronyms should not be used."
"TG Requirement 1.1: metadata/2.0/req/datasets-and-series/resource-type The resource type shall be declared as ""dataset"" or ""series"" using the first gmd:hierarchyLevel child element of gmd:MD_Metadata. The gmd:hierarchyLevel shall contain a gmd:MD_ScopeCode element."
/gmd:MD_Metadata/gmd:hierarchyLevel: gmd:hierarchyLevel <gmd:MD_ScopeCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#MD_ScopeCode" codeListValue="dataset" /> </gmd:hierarchyLevel> "TG Requirement 1.8: metadata/2.0/req/datasets-and-series/resource-locator A Resource locator linking to the service(s) providing online access to the described data set or data set series shall be given, if such online access is available. If no online access for the data set or data set series is available, but there is a publicly available online resource providing additional information about the described data set or data set series, the URL pointing to this resource shall be given instead. These links shall be encoded using gmd:transferOptions/gmd:MD_DigitalTransferOptions/gmd:onLine/gmd:CI_OnlineResource/gmd: linkage/gmd:URL element. The multiplicity of this element is 0..n." "A Resource Locator encoded using the gmd:CI_OnlineResource element may also include gmd:name, gmd:description, and gmd:function properties. TG Recommendation 1.8: metadata/2.0/rec/datasets-and-series/resource-locator-additional-info The gmd:name, gmd:description, and gmd:function/gmd:CI_OnLineFunctionCode child elements of gmd:CI_OnlineResource element containing the given gmd:linkage element should also be provided, if possible, to give additional information about the provided URL link. The gmd:name and the gmd:description elements should contain Non-empty Free Text Elements. If provided, the gmd:CI_OnLineFunctionCode element should point to one of the values of the ISO 19139 code list CI_OnLineFunctionCode." "TG Recommendation 1.9: metadata/2.0/rec/datasets-and-series/resource-locator-url The URL provided as the value of the gmd:transferOptions/gmd:MD_DigitalTransferOptions/gmd:onLine/gmd:CI_OnlineResource/gmd: linkage/gmd:URL element should point to one of following type of resources: - direct access for downloading the described data set, - a service metadata (capabilities) document of a Spatial Data Service used for providing this data set, - a service WSDL document of a Spatial Data Service used for providing this data set (if SOAP binding is available), - a client application that directly accesses the described data set, or - a web page with further instructions for accessing the described data set."
/gmd:MD_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:transferOptions: gmd:transferOptions gmd:MD_DigitalTransferOptions gmd:onLine gmd:CI_OnlineResource gmd:linkage gmd:URLhttp://example.com/wfs?VERSION=2.0.0&SERVICE=WFS&REQUEST=GetFeature&STOREDQUERY_ID=urn:ogc:def:query:OGC-WFS::GetFeatureById&ID=123345</gmd:URL> </gmd:linkage> gmd:name gco:CharacterStringWFS GetFeature request for downloading the data set</gco:CharacterString> </gmd:name> gmd:function <gmd:CI_OnLineFunctionCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#CI_OnLineFunctionCode" codeListValue="download" /> </gmd:function> </gmd:CI_OnlineResource> </gmd:onLine> </gmd:MD_DigitalTransferOptions> </gmd:transferOptions>
"TG Requirement 1.3: metadata/2.0/req/datasets-and-series/dataset-uid A unique identifier shall be given for each described dataset or data sets series. This identifier shall be a URI consisting of a namespace uniquely identifying a naming context governed by an identifier authority, and a code unique within this namespace. The identifying URI shall be encoded using gmd:citation/gmd:CI_Citation/gmd:identifier//gmd:code element with a Non-empty Free Text Element content. The multiplicity of this element is 1..." "NOTE The [ISO 19139] xml schemas allow the use of either the MD_Identifier type or its sub-type RS_Identifier, which, in addition to the mandatory code property, also contains an optional codeSpace property. Since many applications only consider the code attribute and semantically RS_Identifier is intended as an ""identifier (…) for reference systems"" [ISO 19115], the MD_Identifier type should be used wherever possible and the complete URI should be encoded in the code element. This also facilitates the implementation of data-service-coupling based on the unique resource identifier (see also 4.1.2.4). TG Recommendation 1.1: metadata/2.0/rec/datasets-and-series/use_md_identifier It is strongly recommended to use the MD_Identifier instead of the the RS_Identifier type and to encode the complete URI in the code element." "TG Recommendation 1.2: metadata/2.0/rec/datasets-and-series/resolvable-uid It is recommended to make the unique resource identifier resolvable into a document providing information about described data set or data sets series. In the case of HTTP URIs34, the public DNS and the usual HTTP URI resolving mechanisms should be used for implementing this resolvability. For other types of URIs, a resolving service should be provided implementing similar functionality. This document retrieved as the result of the resolving process may be, but is not required to be, the metadata description of the described resource. It is also recommended that viewing of the provided document does not require user authentication, authorisation or specialised viewing tools beyond a typical web browser. TG Recommendation 1.3: metadata/2.0/rec/datasets-and-series/persistent-uid The providers of unique resource identifiers should take great care in ensuring that the issued identifiers remain valid and available for the entire availability period of the identified resource, and preferably also after the data set or the data set series has been made unavailable. If a published unique identifier for a resource must be changed during the availability time of the resource, both the old and the new identifier should resolve to the same document described in TG Recommendation 1.2. If this is not possible, the old identifier should resolve to document providing information about the change in the unique identifier and provide the new unique identifier of the described resource. Assigning a published unique resource identifier to another or an extensively restructured data set or data set series should be avoided. Instead a new unique resource identifier should be assigned to the data set in these cases. The persistence and process of preventing breaking the identifier resolvability is crucial for keeping the links between the services and the provided data sets functional."
/gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification: <gmd:MD_DataIdentification id="md-so-1002001"> gmd:citation gmd:CI_Citation gmd:title gco:CharacterStringINSPIRE_Flurstücke_ALKIS_NRW</gco:CharacterString> </gmd:title> gmd:date gmd:CI_Date gmd:date gco:Date2016-07-01</gco:Date> </gmd:date> gmd:dateType <gmd:CI_DateTypeCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication" /> </gmd:dateType> </gmd:CI_Date> </gmd:date> gmd:identifier gmd:MD_Identifier gmd:code <gmx:Anchor xlink:href="https://registry.gdi-de.org/id/de.nw/inspire-cp-alkis">https://registry.gdi-de.org/id/de.nw/inspire-cp-alkis</gmx:Anchor> </gmd:code> </gmd:MD_Identifier> </gmd:identifier> </gmd:CI_Citation> </gmd:citation> ... </gmd:MD_DataIdentification> "TG Requirement 1.6: metadata/2.0/req/datasets-and-series/resource-language For data sets or data set series containing textual information, the language(s) used in the resource shall be given. The language(s) used shall be encoded using one or more gmd:language/gmd:LanguageCode elements pointing to one of the three-letter language codes of the ISO 639-2/B code list35. The multiplicity of the gmd:language element is 1..*. If the described resource does not contain textual information expressed in a natural language the special code value ""zxx"" of the ISO 639-2/B reserved for ""no linguistic content; not applicable"" shall be used."
"TG Recommendation 1.7: metadata/2.0/rec/datasets-and-series/language-name The name of the language(s) of the described resource in the language of the metadata should be used as the text content of the gmd:LanguageCode element."
/gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:language: gmd:language <gmd:LanguageCode codeList="http://www.loc.gov/standards/iso639-2/" codeListValue="fin">Suomi</gmd:LanguageCode> </gmd:language> "TG Requirement 2.6: metadata/2.0/req/isdss/data-encoding The encoding and the storage or transmission format of the provided data sets or data set series shall be given using the gmd:distributionFormat/gmd:MD_Format element. The multiplicity of this element is 1..*. The gmd:name and gmd:version child elements of gmd:MD_Format are mandatory. Both of these elements shall contain Non-empty Free Text Elements. If the version of the encoding is unknown or if the encoding is not versioned, the gmd:version shall be left empty and the nil reason attribute shall be provided with either value ""unknown"" or ""inapplicable"" correspondingly"
/gmd:MD_Metadata/gmd:distributionInfo/gmd:distributionFormat: gmd:distributionFormat gmd:MD_Format gmd:name gco:CharacterStringAddresses GML Application Schema</gco:CharacterString> </gmd:name> gmd:version gco:CharacterString3.0</gco:CharacterString> </gmd:version> gmd:specification gco:CharacterStringD2.8.I.5 Data Specification on Addresses – Technical Guidelines</gco:CharacterString> </gmd:specification> </gmd:MD_Format> </gmd:distributionFormat> gmd:distributionFormat gmd:MD_Format gmd:name <gmx:Anchor xlink:href="http://inspire.ec.europa.eu/media-types/application/x-shapefile">Esri Shapefile</gmx:Anchor> </gmd:name> <gmd:version gco:nilReason="unknown" /> </gmd:MD_Format> </gmd:distributionFormat>
"TG Requirement 2.5: metadata/2.0/req/isdss/character-encoding The character encoding(s) shall be given for data sets and data sets series which use encodings not based on UTF-8 by using element gmd:characterSet/gmd:MD_CharacterSetCode referring to one of the values of ISO 19139 code list MD_CharacterSetCode. The multiplicity of this element is 0..n. If more than one character encoding is used within the described data set or data sets series, all used character encodings, including UTF-8 (code list value ""utf8""), shall be given using this element." NOTE UTF-8 should be used for character encoding of INSPIRE data sets and data set series unless there are compelling and overriding reasons not to use it.
"TG Requirement 2.4: metadata/2.0/req/isdss/spatial-representation-type The spatial representation type shall be given using element gmd:spatialRepresentationType/gmd:MD_SpatialRepresentationTypeCode referring to one of the values of ISO 19139 code list MD_SpatialRepresentationTypeCode and one of the code list values ""vector"", ""grid"", ""tin"" or “textTable”. Multiplicity of this element is 1..*."
/gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:spatialRepresentationType gmd:spatialRepresentationType <gmd:MD_SpatialRepresentationTypeCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#MD_SpatialRepresentationTypeCode" codeListValue="vector" /> </gmd:spatialRepresentationType> "TG Requirement 1.7: metadata/2.0/req/datasets-and-series/topic-category The main theme(s) of the data set shall be described using of the ISO 19115 topic category code list values. The topic categories shall be encoded using gmd:topicCategory/gmd:MD_TopicCategoryCode element36. The multiplicity of this element is 1..*." Note that contrary to many other code lists which are defined in the ISO 19139 XML Schema as references to an external code list, gmd:MD_TopicCategoryCode element is defined as a string enumeration.
/gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:topicCategory: gmd:topicCategory gmd:MD_TopicCategoryCodeenvironment</gmd:MD_TopicCategoryCode> </gmd:topicCategory> "TG Requirement C.15: metadata/2.0/req/common/keyword-originating-cv When using keywords originating from a controlled vocabulary, the originating controlled vocabulary shall be cited using gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:thesaurusName/gmd:CI_Citation element. The title of the vocabulary shall be given using gmd:title element with a Non-empty Free Text Element content. The publication date of the vocabulary shall be given using the gmd:date/gmd:CI_Date/gmd:date/gco:Date and gmd:dateType/gmd:CI_DateTypeCode24 elements" "TG Recommendation C.7: metadata/2.0/rec/common/use-cvs If keyword values are made available as a collection of specific, well-defined terms (controlled vocabularies), those should be preferred over free-text terms. TG Recommendation C.8: metadata/2.0/rec/common/use-anchors-for-cv-keywords If the keywords from controlled vocabularies are used and the individual keywords have a specified canonical URI within that controlled vocabulary, these keywords should be encoded using the gmd:keyword/gmx:Anchor element. The xlink:href attribute of the gmx:Anchor element should be used for referring to the canonical URI of the keyword. TG Recommendation 1.9: metadata/2.0/rec/common/use-anchors-for-thesauri For references to well-known thesauri or controlled vocabularies, the title element of the thesaurusName should be encoded using the gmd:title/gmx:Anchor element. The xlink:href attribute of the gmx:Anchor element should be used for referring to the URI of the thesaurus or controlled vocabulary." "In addition, XML fragment documents containing the CI_Citation elements for commonly used thesauri and controlled vocabularies will be made available in the http://inspire.ec.europa.eu/id/citation/ namespace. References to these CI_Citation fragment documents may be used to encode the specification element by reference, using the xlink:href attribute of the gmd:thesaurusName element (see Example 2.10). NOTE 1 The pre-defined CI_Citation elements will be designed to fulfil TG requirement C.15 and will be made available in different languages. The appropriate language version of the CI_Citation element can be accessed using content negotiation (using the Accept-Language HTTP header). NOTE 2 In order to ensure compatibility with all clients (including those that cannot resolve xlinks), the gmd:thesaurusName can also contain the CI_Citation fragment (see Example 2.11Example 2.19). In this case, according to [ISO 19136], ""if both a link and content are present in an instance of a property element, then the object found by traversing the xlink:href link shall be the normative value of the property. The object included as content shall be used by the data recipient only if the remote instance cannot be resolved; this may be considered to be a ""cached"" version of the object."" The use of gmx:Anchor elements and pre-defined XML fragments for CI_Citations will help avoid issues with spelling errors or similar mistakes when providing the thesaurusName elements. They will also allow the unique identification of controlled vocabularies in the metadata. /"
"TG Requirement 1.4: metadata/2.0/req/datasets-and-series/inspire-theme-keyword The INSPIRE Spatial Data Theme(s), to which the data set belongs to, shall be declared using at least one keyword from the INSPIRE Spatial Data Themes vocabulary of the general environmental multilingual thesaurus (GEMET). The keyword values shall be the exact text values of the terms in this vocabulary. These keywords shall be encoded using an gmd:descriptiveKeywords/gmd:MD_Keywords element referring to the GEMET INSPIRE themes controlled vocabulary as specified in section 2.4.5. The value of the gmd:thesaurusName/gmd:CI_Citation/gmd:title element shall contain value ""GEMET - INSPIRE themes, version 1.0"". For each INSPIRE Spatial Data Theme, a gmd:keyword element shall be included with the title of the theme as a Non-empty Free Text Element content in the language of the metadata." "TG Recommendation 1.4: metadata/2.0/rec/datasets-and-series/use-anchors-for-gemet For references to the GEMET – INSPIRE themes controlled vocabulary, the title element of the thesaurusName should be encoded using the gmd:title/gmx:Anchor element, with the xlink:href attribute referring to http://www.eionet.europa.eu/gemet/inspire_themes. The INSPIRE themes keywords should be encoded using the gmd:keyword/gmx:Anchor element, with the xlink:href attribute referring to the URI of the theme defined in the GEMET – INSPIRE themes controlled vocabulary. NOTE The URIs of the INSPIRE themes are also available in the INSPIRE theme register at http://inspire.ec.europa.eu/theme."
/gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords: gmd:MD_Keywords gmd:keyword <gmx:Anchor xlink:href="http://inspire.ec.europa.eu/theme/ac">Atmospheric conditions</gmx:Anchor> </gmd:keyword> gmd:keyword <gmx:Anchor xlink:href="http://inspire.ec.europa.eu/theme/mf">Meteorological geographical features</gmx:Anchor> </gmd:keyword> gmd:thesaurusName gmd:CI_Citation gmd:title <gmx:Anchor xlink:href="http://www.eionet.europa.eu/gemet/inspire_themes">GEMET - INSPIRE themes, version 1.0</gmx:Anchor> </gmd:title> gmd:date gmd:CI_Date gmd:date gco:Date2008-06-01</gco:Date> </gmd:date> gmd:dateType <gmd:CI_DateTypeCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication" /> </gmd:dateType> </gmd:CI_Date> </gmd:date> </gmd:CI_Citation> </gmd:thesaurusName> </gmd:MD_Keywords>
"TG Recommendation 1.5: metadata/2.0/rec/datasets-and-series/additional-keywords In addition to the required keywords from the GEMET - INSPIRE themes vocabulary, it is recommended to provide at least two other keywords describing the data set or data set series."
"TG Requirement C.19: metadata/2.0/req/common/bounding-box A minimal containing geographic bounding box of the data set or data set series shall be described. This bounding box shall be encoded using one or more gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox elements. The multiplicity of this element is 1..* for data sets and data set series, and 0..n for services. The bounding coordinate values for west and east bound longitudes and south and north bound latitudes shall be given in decimal degree values using WGS 84 Coordinate Reference System, as specified for the EX_GeographicBoundingBox class of the [ISO 19115] data model. The coordinates shall be given with at least 2 decimal precision."
/gmd:MD_Metadata/gmd:identificationInfo//gmd:extent: gmd:extent gmd:EX_Extent gmd:geographicElement gmd:EX_GeographicBoundingBox gmd:westBoundLongitude gco:Decimal-15.00</gco:Decimal> </gmd:westBoundLongitude> gmd:eastBoundLongitude gco:Decimal45.00</gco:Decimal> </gmd:eastBoundLongitude> gmd:southBoundLatitude gco:Decimal35.00</gco:Decimal> </gmd:southBoundLatitude> gmd:northBoundLatitude gco:Decimal72.00</gco:Decimal> </gmd:northBoundLatitude> </gmd:EX_GeographicBoundingBox> </gmd:geographicElement> </gmd:EX_Extent> </gmd:extent> "TG Requirement 2.1: metadata/2.0/req/isdss/crs The coordinate reference system(s) used in the described data set or data set series shall be given using element gmd:referenceSystemInfo/gmd:MD_ReferenceSystem/gmd:referenceSystemIdentifier/gmd:RS_Identifier. The multiplicity of this element is 1... The gmd:code child element of gmd:RS_Identifier is mandatory. The gmd:codeSpace child element shall be used if the code alone does not uniquely identify the referred coordinate reference system. Both gmd:code and gmd:codeSpace element (if given) shall contain Non-empty Free Text Elements. Only the coordinate reference system identifiers specified in a well-known common register shall be used." "TG Recommendation 2.1: metadata/2.0/rec/isdss/source-crs If the data set is provided through a download service that provides coordinate transformation functionality (i.e. allows to provide the data set in any coordinate reference system supported by the service), the source coordinate reference system(s) of the data set should be documented in the metadata." "TG Requirement 2.2: metadata/2.0/req/isdss/crs-id If the coordinate reference system is listed in the table Default Coordinate Reference System Identifiers in Annex D.4, the value of the HTTP URI Identifier column shall be used as the value of gmd:referenceSystemInfo/gmd:MD_ReferenceSystem/ gmd:referenceSystemIdentifier/gmd:RS_Identifier/gmd:code element. The gmd:codeSpace element shall not be used in this case." "Some data sets (e.g. polulation distribution or health statistics) may have no direct spatial reference (i.e. a geometry attribute), but only an indirect one (e.g. to a statistical or administrative unit). In such cases, the data set providing the spatial reference (e.g. a data set of the NUTS statistical regions) should be considered as the spatial reference system for the data set. According to [ISO 19112], such reference systems are called “spatial reference systems using geographic identifiers”, but these are not conisered by [ISO 19139]. TG Recommendation 2.2: metadata/2.0/rec/isdss/srs-using-geographic-identifiers Also spatial reference systems using geographic identifiers should be identified using the element gmd:referenceSystemInfo/gmd:MD_ReferenceSystem/ gmd:referenceSystemIdentifier/gmd:RS_Identifier/gmd:code. A gmx:Anchor element should be used, whose xlink:href attribute refers to a URI that provides further information about the spatial reference systems using geographic identifiers. NOTE Best practices and examples on what URIs to use for spatial reference systems using geographic identifiers should be discussed on the thematic clusters platform /gmd:MD_Metadata/gmd:referenceSystemInfo: gmd:referenceSystemInfo gmd:MD_ReferenceSystem gmd:referenceSystemIdentifier gmd:RS_Identifier gmd:code <gmx:Anchor xlink:href=""http://publications.europa.eu/resource/authority/atu"">Administrative territoral units NAL</gmx:Anchor> </gmd:code> </gmd:RS_Identifier> </gmd:referenceSystemIdentifier> </gmd:MD_ReferenceSystem> </gmd:referenceSystemInfo>"
/gmd:MD_Metadata/gmd:referenceSystemInfo: gmd:referenceSystemInfo gmd:MD_ReferenceSystem gmd:referenceSystemIdentifier gmd:RS_Identifier gmd:code <gmx:Anchor xlink:href="http://www.opengis.net/def/crs/EPSG/0/4258">EPSG:4258</gmx:Anchor> </gmd:code> </gmd:RS_Identifier> </gmd:referenceSystemIdentifier> </gmd:MD_ReferenceSystem> </gmd:referenceSystemInfo> "TG Requirement C.11: metadata/2.0/req/common/temporal-reference At least one temporal reference describing the resource shall be given using gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date element, with one of the following date types: - publication for date of publication of the resource, - revision for the date of last revision of the resource, or - creation for the date of creation of the resource. The date type shall be given using the gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:dateType/gmd:CI_DateTypeCode element and it shall point to the corresponding value of [ISO 19139] code list CI_DateTypeCode mentioned above23. The date values shall be expressed using Gregorian calendar and in accordance with [ISO 8601] with either date precision or date and time precision. For date precision the gmd:CI_Date/gmd:date/gco:Date element, and for date and time precision gmd:CI_Date/gmd:date/gco:DateTime element shall be used." "Additionally the [Regulation 1205/2008] restricts the multiplicity of the date of last revision and the date of creation to the maximum of one. To comply with these Implementation Rules, the following two Requirements must be fulfilled: TG Requirement C.12: metadata/2.0/req/common/max-1-date-of-creation Not more than one date of creation for the described resource shall be given. TG Requirement C.13: metadata/2.0/req/common/max-1-date-of-last-revision Not more than one date of last revision for the described resource shall be given. TG" "TG Recommendation C.6: metadata/2.0/rec/common/date-of-last-revision-dataset In case of spatial data set, at least the date of the last revision of the spatial data set should be reported." "TG Requirement C.14: metadata/2.0/req/common/temporal-extent If a temporal reference is provided using the temporal extent, it shall be encoded using the gmd:extent/gmd:EX_Extent element with one or more gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent child elements. The value of each of these element may be an individual date or a time period between two dates. The multiplicity of this element is 0..*. A single individual date or a time period shall be encoded using one gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent element. For individual dates this element shall contain a gml:TimeInstant/gml:timePosition element with the date value given according to [ISO 8601]. For a single time period the gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent element shall contain a gml:TimePeriod element containing start and end dates of the period. In case the time period is open-ended with either the start or the end date unknown, the elements gml:startPosition or gml:endPosition may be used with an empty value and the attribute indeterminatePosition with value ""unknown"". If the temporal extent is on-going, the gml:endPosition may be used with an empty value and the attribute indeterminatePosition with value ""now"". Individual dates and time periods may be combined to form a complex temporal extent using multiple gmd:temporalElement/gmd:EX_TemporalExtent/gmd:extent elements."
<gmd:MD_Metadata … … gmd:identificationInfo gmd:MD_DataIdentification … gmd:extent gmd:EX_Extent gmd:temporalElement gmd:EX_TemporalExtent gmd:extent <gml:TimePeriod gml:id="IDd2febbb4-e66f-4ac8-ba76-8fd9bc7c8be6"> gml:beginPosition2008-01-01T11:45:30</gml:beginPosition> gml:endPosition2008-12-31T09:10:00</gml:endPosition> </gml:TimePeriod> </gmd:extent> </gmd:EX_TemporalExtent> </gmd:temporalElement> </gmd:EX_Extent> </gmd:extent> … </gmd:MD_DataIdentification> … </gmd:identificationInfo> … </gmd:MD_Metadata>
/gmd:MD_Metadata/gmd:identificationInfo/*/gmd:citation/gmd:CI_Citation: gmd:CI_Citation gmd:title gco:CharacterStringINSPIRE compliant View Service for the Finnish Cadastral Parcels</gco:CharacterString> </gmd:title> gmd:date gmd:CI_Date gmd:date gco:Date2013-02-21</gco:Date> </gmd:date> gmd:dateType <gmd:CI_DateTypeCode codeList="http://standards.iso.org/iso/19139/resources/ gmxCodelists.xml#CI_DateTypeCode" codeListValue="revision">révision</gmd:CI_DateTypeCode> </gmd:dateType> </gmd:CI_Date> </gmd:date> </gmd:CI_Citation> "TG Requirement 2.3: metadata/2.0/req/isdss/temportal-rs The temporal reference system(s) used in the described data set or data set series shall be given using element gmd:referenceSystemInfo/gmd:MD_ReferenceSystem/gmd:referenceSystemIdentifier/gmd:RS_Identifier. The multiplicity of this element is 0..n. The gmd:code child element of gmd:RS_Identifier is mandatory. The gmd:codeSpace child element shall be used if the code alone does not uniquely identify the referred coordinate reference system. Both gmd:code and gmd:codeSpace element (if given) shall contain Non-empty Free Text Elements." "TG Recommendation 2.1: metadata/2.0/rec/isdss/ If a commonly known unique identifier for the referred temporal reference system is available in a common register, the registered identifier should be used as the value of the gmd:referenceSystemInfo/gmd:MD_ReferenceSystem/gmd:referenceSystemIdentifier/gmd:RS_Identifier/gmd:code element."
"TG Requirement 1.11: metadata/2.0/req/datasets-and-series/lineage The lineage statement for the described data set or data set series shall be given. It shall be included in the gmd:dataQualityInfo/gmd:DQ_DataQuality element scoped to the entire described data sets or data sets series as specified by TG Requirement 1.9. The lineage shall be encoded using the gmd:lineage/gmd:LI_Lineage/gmd:statement element with a Non-empty Free Text Element content, and it shall contain the description of the lineage of the described data set or series. The multiplicity of this element is 1." "TG Recommendation 1.12: metadata/2.0/rec/datasets-and-series/use-iso-dq-elements-and-measures If a data provider has a procedure for the quality management of their spatial data set (series) then the appropriate ISO data quality elements and measures should be used to evaluate and report (in the metadata) the results in addition to the Lineage metadata element." "TG Recommendation 1.13: metadata/2.0/rec/datasets-and-series/lineage-avoid-acronyms The use of abbreviations (including acronyms) should be avoided. If used, their meaning should be explained."
"TG Requirement 1.5: metadata/2.0/req/datasets-and-series/spatial-resolution Spatial resolution for data set or data set series shall be given using either equivalent scale or a resolution distance, provided that these have been specified for the described data sets. If both ways have been specified, only one of the ways shall be used. The spatial resolution as equivalent scale shall be encoded using gmd:spatialResolution/gmd:MD_Resolution/gmd:equivalentScale/gmd:MD_RepresentativeFraction/gmd:denominator/gco:Integer element. The spatial resolution as resolution distance shall be encoded using gmd:spatialResolution/gmd:MD_Resolution/gmd:distance/gco:Distance element. The multiplicity of this element is 0..n." "TG Recommendation 1.6: metadata/2.0/rec/datasets-and-series/spatial-resolution-interval If the spatial resolution is an interval, both bounding values of the interval should be given (either as equivalent scale or resolution distance) as two instances of the gmd:spatialResolution/gmd:MD_Resolution element."
"/gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:spatialResolution: gmd:spatialResolution gmd:MD_Resolution gmd:equivalentScale gmd:MD_RepresentativeFraction gmd:denominator gco:Integer50000</gco:Integer> </gmd:denominator> </gmd:MD_RepresentativeFraction> </gmd:equivalentScale> </gmd:MD_Resolution> </gmd:spatialResolution> /gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:spatialResolution: gmd:spatialResolution gmd:MD_Resolution gmd:distance <gco:Distance uom=""dd"">0.25</gco:Distance> </gmd:distance> </gmd:MD_Resolution> </gmd:spatialResolution>
/gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:spatialResolution: gmd:spatialResolution gmd:MD_Resolution gmd:distance <gco:Distance uom=""dd"">0.24</gco:Distance> </gmd:distance> </gmd:MD_Resolution> gmd:MD_Resolution gmd:distance <gco:Distance uom=""dd"">0.26</gco:Distance> </gmd:distance> </gmd:MD_Resolution> </gmd:spatialResolution>" "TG Requirement 2.7: metadata/2.0/req/isdss/topological-consistency-quantitative-results The quantitative results for topological consistency measures shall be reported using the gmd:report/gmd:DQ_TopologicalConsistency element with a gmd:DQ_QuantitativeResult element as the value of its mandatory gmd:result property. The multiplicity of the element is 0... The gmd:valueUnit and gmd:value/gco:Record child elements of gmd:DQ_QuantitativeResult are mandatory and shall be used for giving a numerical or otherwise quantitative value of the evaluated topology consistency measure for the described data set or data set series. The type of the gmd:value/gco:Record element shall be chosen based on the result type of the particular measure, and it shall be declared using the xsi:type attribute of the gco:Record element." "TG Recommendation 2.2: metadata/2.0/rec/isdss/topological-consistency-measure-name The name of the topology consistency measure should be provided using the gmd:nameOfMeasure child element of each of the gmd:DQ_QuantitativeResult elements. This element is a Non-empty Free Text Element. In the case where the result reflects more than one measure, a separate gmd:nameOfMeasure should be given to identify each included measure. TG Recommendation 2.3: metadata/2.0/rec/isdss/topological-consistency-evaluation-method It is recommended to provide a short description of the evaluation method used for topological consistency check using the gmd:evaluationMethodDescription child element of gmd:DQ_QuantitativeResult element. This element is a Non-empty Free Text Element. If applicable, the evaluation method type should be declared using the gmd:evaluationMethodType/gmd:DQ_EvaluationMethodTypeCode child element of gmd:DQ_QuantitativeResult element referring to one of the values of ISO 19139 code list DQ_EvaluationMethodTypeCode. TG Recommendation 2.4: metadata/2.0/rec/isdss/topological-consistency/date It is recommended to provide the date of evaluating the topological consistency check using the gmd:dateTime/gco:DateTime child element of gmd:DQ_QuantitativeResult element. The value shall be expressed using Gregorian calendar and in accordance with [ISO 8601] date and time precision." "Providing descriptive results The descriptive topological consistency measure is properly described in [ISO 19157], but unfortunately there is no obvious element for encoding it in the [ISO 19139] XML Schemas. To make it possible to encode the descriptive results without extending the [ISO 19139] XML Schema, the gmd:DQ_TopologicalConsistency element is used with a specific type of gmd:DQ_ConformanceResult element referring to the INSPIRE Generic Network Model. The actual textual description of the consistency result is reported using the gmd:explanation property. TG Requirement 2.8: metadata/2.0/req/isdss/topological-consistency-descriptive-results If the data set includes types from the Generic Network Model, it does not assure the centreline topology for the network, and the value of the topological consistency checks is not available as quantitative results, the result of the topological consistency shall be reported using the descriptive results. The descriptive topological consistency measures shall be reported using the gmd:report/gmd:DQ_TopologicalConsistency/gmd:result /gmd:DQ_ConformanceResult element citing to the INSPIRE Generic Network Model. The gmd:DQ_ConformanceResult/gmd:specification/gmd:CI_Citation/ gmd:title/gco:CharacterString element shall have the value ""INSPIRE Data Specifications - Base Models - Generic Network Model"" regardless of the metadata language. The gmd:DQ_ConformanceResult/gmd:specification/gmd:CI_Citation/ gmd:date/gmd:CI_Date/gmd:date shall contain the publication date of the INSPIRE Generic Network Model document containing the geometry types used in the data set. The date type code element gmd:DQ_ConformanceResult/ gmd:specification/gmd:CI_Citation/ gmd:date/gmd:CI_Date/gmd:dateType/gmd:CI_DateTypeCode shall be given and it shall point to the value ""publication"" of the ISO 19139 code list CI_DateTypeCode. The value of the gmd:DQ_ConformanceResult/gmd:pass element shall always be ""false"" in this element to indicate that the data set does not assure the centreline topology for the network. The multiplicity of gmd:report/gmd:DQ_TopologicalConsistency/gmd:result/ gmd:DQ_ConformanceResult elements as described above is 0... The textual description of the results of the topological consistency check shall be given using the gmd:DQ_ConformanceResult/gmd:explanation element. This element is a Non-empty Free Text Element." /gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality/gmd:report/gmd:DQ_TopologicalConsistency: gmd:DQ_TopologicalConsistency gmd:nameOfMeasure gco:CharacterStringnumber of faulty point-curve connections</gco:CharacterString> </gmd:nameOfMeasure> gmd:evaluationMethodType <gmd:DQ_EvaluationMethodTypeCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#DQ_EvaluationMethodTypeCode" codeListValue="indirect">Indirect</gmd:DQ_EvaluationMethodTypeCode> </gmd:evaluationMethodType> gmd:evaluationMethodDescription gco:CharacterStringA point-curve connection exists where different curves touch. These curves have an intrinsic topological relationship that shall reflect the true constellation. If the point-curve connection contradicts the universe of discourse, the point-curve connection is faulty with respect to this data quality measure. The data quality measure counts the number of errors of this kind.</gco:CharacterString> </gmd:evaluationMethodDescription> gmd:dateTime gco:DateTime2015-04-01T16:20:00</gco:DateTime> </gmd:dateTime> gmd:result gmd:DQ_QuantitativeResult <gmd:valueUnit xlink:href="http://www.opengis.net/def/uom/OGC/1.0/unity"/> gmd:value <gco:Record xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:type="xs:integer">12</gco:Record> </gmd:value> </gmd:DQ_QuantitativeResult> </gmd:result> </gmd:DQ_TopologicalConsistency> "The declared conformity of the described resource to INSPIRE Implementing Rules and other specifications shall be given in the metadata element Specification and Degree as stated in [Regulation 1205/2008], Part B 7: 7.1. Specification This is a citation of the implementing rules adopted under Article 7(1) of Directive 2007/2/EC or other specification to which a particular resource conforms. A resource may conform to more than one implementing rules adopted under Article 7(1) of Directive 2007/2/EC or other specification. This citation shall include at least the title and a reference date (date of publication, date of last revision or of creation) of the implementing rules adopted under Article 7(1) of Directive 2007/2/EC or of the specification. 7.2. Degree This is the degree of conformity of the resource to the implementing rules adopted under Article 7(1) of Directive 2007/2/EC or other specification. The value domain of this metadata element is defined in Part D. In the Tables 1 and 2 of [Regulation 1205/2008], Part C, the multiplicity of this element is one or more for both data sets and services. These conformity declarations help the users of the Discovery services in finding spatial data sets and services conforming to the INSPIRE or other specifications in the use cases where such conformity is required or preferred. Discovery services may contain metadata for both conforming and not conforming to these specifications. [INSPIRE Directive], Article 11(2)(d) requires this information to be provided as search criteria in INSPIRE Discovery Services. In this specification the above Implementing Rule text is interpreted to mean that the conformity shall be declared at least to the following regulations depending on the described INSPIRE resource type: • Data sets and data set series shall declare conformity to [Regulation 1089/2010]. • Network Services should declare conformity to [Regulation 976/2009]. • Invocable Spatial Data Services (including interoperable and harmonised Spatial Data Services) shall declare conformity to [Regulation 1089/2010]. The specific TG Requirements for adding these conformity declarations are included in the corresponding Conformance Classes for these resource type. The TG Requirements below shall be followed for encoding the conformity for all of these resource types." "TG Requirement C.21: metadata/2.0/req/common/conformity-specification Each gmd:report/gmd:DQ_DomainConsistency/gmd:result/gmd:DQ_ConformanceResult element shall include a citation of the INSPIRE Implementing Rule, specification document or Conformance Class, including its official title and the date of publication of the document, using gmd:specification/gmd:CI_Citation element. The title shall be given using the gmd:title child element of the citation element with a Non-empty Free Text Element content. For the INSPIRE Implementation Rule documents the value of the title element shall match exactly the official title of the cited document in the language of the metadata. The publication date of the cited document shall be given using gmd:date child element. The date value shall be expressed in accordance with ISO 8601 with only the date part included. The date type code element gmd:date/gmd:CI_Date/gmd:dateType/gmd:CI_DateTypeCode shall be given and it shall point to the value ""publication"" of the ISO 19139 code list CI_DateTypeCode30." "TG Requirement C.20: metadata/2.0/req/common/conformity The degree of conformity of the described resource with an INSPIRE Implementing Rule, specification document or Conformance Class, shall be given using one or several gmd:DQ_ConformanceResult elements under gmd:report/gmd:DQ_DomainConsistency/gmd:result. For each conformity statement (i.e. for each specification), a separate gmd:DQ_ConformanceResult element shall be used. The multiplicity of this element is 1..*." "TG Requirement 1.9: metadata/2.0/req/datasets-and-series/one-data-quality-element There shall be exactly one gmd:dataQualityInfo/gmd:DQ_DataQuality element scoped to the entire described data set or data set series. The scoping shall be encoded using gmd:scope/gmd:DQ_Scope/gmd:level/gmd:MD_ScopeCode element referring to value ""dataset"" or ""series"" of ISO 19139 code list MD_ScopeCode. TG Requirement 1.10: metadata/2.0/req/datasets-and-series/conformity Metadata for an INSPIRE data set or data set series shall declare conformity to the Implementing Rules for interoperability of spatial data sets and services, and it shall be encoded using gmd:report/gmd:DQ_DomainConsistency/gmd:result/gmd:DQ_ConformanceResult element as specified in TG Requirement C.2041. This element shall contain citation of the [Regulation 1089/2010] encoded according to TG Requirement C.2142. The degree of conformity shall be encoded as according to TG Requirement C.2243. 40" "TG Recommendation C.11: metadata/2.0/rec/common/use-anchors-for-specifications For references to well-known INSPIRE legal acts, technical guidance documents or conformance classes, the title element of the specification should be encoded using the gmd:title/gmx:Anchor element. The xlink:href attribute of the gmx:Anchor element should be used for referring to the URI of the specification. / In addition, XML fragment documents containing the CI_Citation elements for the INSPIRE legal acts, technical guidance documents and conformance classes will be made available in the http://inspire.ec.europa.eu/id/citation/ namespace. References to these CI_Citation fragment documents may be used to encode the specification element by reference, using the xlink:href attribute of the gmd:specification element (see Example 2.18). NOTE 1 The pre-defined CI_Citation elements will be designed to fulfil TG requirement C.21 and will be made available in different languages. The appropriate language version of the CI_Citation element can be accessed using content negotiation (using the Accept-Language HTTP header). NOTE 2 In order to ensure compatibility with all clients (including those that cannot resolve xlinks), the gmd:specification can also contain the CI_Citation fragment (see Example 2.19). In this case, according to [ISO 19136], ""if both a link and content are present in an instance of a property element, then the object found by traversing the xlink:href link shall be the normative value of the property. The object included as content shall be used by the data recipient only if the remote instance cannot be resolved; this may be considered to be a ""cached"" version of the object."" The use of gmx:Anchor elements and pre-defined XML fragments for CI_Citations will help avoid issues with spelling errors or similar mistakes when providing the specification elements. They will also allow the unique identification of specifications in the metadata. TG Recommendation 1.10: metadata/2.0/rec/datasets-and-series/uri-for-regulation-1089-2010 If providing the specification title as an gmx:Anchor element (as recommended in TG Recommendation C.10), the following URI should be used to refer to [Regulation 1089/2010]: http://data.europa.eu/eli/reg/2010/1089. TG Recommendation 1.11: metadata/2.0/rec/datasets-and-series/uris-for-ats-and-cc If declaring conformity to an abstract test suite or a conformance class using an gmx:Anchor element (as recommended in TG Recommendation C.11), the URI identifying the abstract test suite or a conformance class should be used in the xlink:href attribute of the specification title element. NOTE It is not currently planned to provide pre-defined XML fragments containing the CI_Citation elements for the INSPIRE TG documents in the http://inspire.ec.europa.eu/id/citation/ namespace. However, such fragments can be added if this is deemed useful by INSPIRE data providers." /gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality/gmd:report/gmd:DQ_DomainConsistency/gmd:result/gmd:specification gmd:specification gmd:CI_Citation gmd:title <gmx:Anchor xlink:href="http://data.europa.eu/eli/reg/2010/1089">COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services</gmx:Anchor> </gmd:title> gmd:date gmd:CI_Date gmd:date gco:Date2010-12-08</gco:Date> </gmd:date> gmd:dateType <gmd:CI_DateTypeCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication">publication</gmd:CI_DateTypeCode> </gmd:dateType> </gmd:CI_Date> </gmd:date> </gmd:CI_Citation> </gmd:specification> "TG Requirement C.22: metadata/2.0/req/common/conformity-degree Each gmd:report/gmd:DQ_DomainConsistency/gmd:result/gmd:DQ_ConformanceResult element containing a specification citation described in Requirement C.21 shall also include the degree of declared conformity against this specification using gmd:pass property with gco:Boolean value of ""true"" for a conformant resource and ""false"" for non-conformant resource. If the conformity has not yet been evaluated, the gmd:pass element shall be empty and contain a nil reason attribute with value ""unknown""."
"In the Tables 1 and 2 of [Regulation 1205/2008], Part C, the multiplicity of this element is one or more for both data sets and services. The Article 13 of the [INSPIRE Directive] contains a list of cases where limitations to public access can be set. Concerning providing the metadata for the data sets and services through Discovery services, the limitations on public access can be set on the base of reasons of international relations, public security or national defence. Concerning providing View, Download or Transformation Services, or e-commerce services referred to in Article 14(3) of [INSPIRE Directive], limitations on public access can be set on the base of the following reasons ([INSPIRE Directive], Article 13): (a) the confidentiality of the proceedings of public authorities, where such confidentiality is provided for by law; (b) international relations, public security or national defence; (c) the course of justice, the ability of any person to receive a fair trial or the ability of a public authority to conduct an enquiry of a criminal or disciplinary nature; (d) the confidentiality of commercial or industrial information, where such confidentiality is provided for by national or Community law to protect a legitimate economic interest, including the public interest in maintaining statistical confidentiality and tax secrecy; (e) intellectual property rights; (f) the confidentiality of personal data and/or files relating to a natural person where that person has not consented to the disclosure of the information to the public, where such confidentiality is provided for by national or Community law; (g) the interests or protection of any person who supplied the information requested on a voluntary basis without being under, or capable of being put under, a legal obligation to do so, unless that person has consented to the release of the information concerned; (h) the protection of the environment to which such information relates, such as the location of rare species. ISO 19115 provides a general mechanism for documenting different categories of constraints applicable to the resource (or its metadata). In ISO 19139 XML Schema this mechanism is supported by the element gmd:MD_Constraints and its specifications: • gmd:MD_LegalConstraints for legal constraints; • gmd:MD_SecurityConstraints for security constraints. Since gmd:MD_SecurityConstraints has for many countries only military use, only the element gmd:MD_LegalConstraints is used for this information in the context of this specification. To make the references to the allowed reasons in Article 13 for limiting public access explicit, an INSPIRE code list (Annex D.1 “Limitations on public access) with all the reason values is used in gmd:otherConstraints elements. However, because the domain of the gmd:otherConstraints is a character string (free text), the references to the code list values are done using gmx:Anchor and its xlink:href attribute with the URL pointing to the specified code list value in the INSPIRE Registry." "TG Requirement C.17: metadata/2.0/req/common/limitations-on-public-access Limitations on public access (or lack of such limitations) for the described resource shall be described using exactly one gmd:resourceConstraints/gmd:MD_LegalConstraints element. This element shall not be the same one as used for describing conditions applying to access and use (see 2.4.7). The limitations on public access (or lack of such limitations) based on reasons referred to in point (a) or in points (c) to (h) of Article 13(1) of INSPIRE Directive quoted above, the gmd:resourceConstraints/gmd:MD_LegalConstraints element shall include a combination of
- one instance of gmd:accessConstraints/gmd:MD_RestrictionCode element with code list value ""otherRestrictions""25 and - at least one instance of gmd:otherConstraints/gmx:Anchor pointing to one of the values from the code list for LimitationsOnPublicAccess26. If there are no limitations on public access, the element shall point to the code list value ""noLimitations""." /gmd:MD_Metadata/gmd:identificationInfo/*/gmd:resourceConstraints: gmd:resourceConstraints gmd:MD_LegalConstraints gmd:accessConstraints <gmd:MD_RestrictionCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions" /> </gmd:accessConstraints> gmd:otherConstraints <gmx:Anchor xlink:href="http://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess/INSPIRE_Directive_Article13_1a"> Limitation d’accés public basé sur l’article 13(1) de la directive INSPIRE </gmx:Anchor> </gmd:otherConstraints> </gmd:MD_LegalConstraints> </gmd:resourceConstraints>
"TG Requirement C.18: metadata/2.0/req/common/conditions-for-access-and-use Conditions for access and use of the described resource shall be described using exactly one gmd:resourceConstraints/gmd:MD_LegalConstraints element. This element shall not be the same used for describing limitations on public access (see 2.4.6). The gmd:resourceConstraints/gmd:MD_LegalConstraints element for conditions for access and use shall be encoded as follows: One instance of either gmd:accessConstraints or gmd:useConstraints element shall be given. In both cases this element shall contain a gmd:MD_RestrictionCode element with code list value ""otherRestrictions""27. Additionally at least one instance of gmd:otherConstraints shall be given describing the actual conditions. If no conditions apply the gmd:otherConstraints shall include a gmx:Anchor element pointing to the value ""noConditionsApply"" in the code list ConditionsApplyingToAccessAndUse28. If the conditions are unknown gmd:otherConstraints shall include a gmx:Anchor element pointing to the value ""conditionsUnknown"" in the code list ConditionsApplyingToAccessAndUse29. In other cases gmd:otherConstraints shall include a Non-empty Free Text Element with a textual description of the conditions in the language of the metadata. This text shall include descriptions of terms and conditions, including where applicable, the corresponding fees or an URL pointing to an online resource where these terms and conditions are described." "TG Recommendation C.10: metadata/2.0/rec/common/licences For detailed information about the licensing of the resource it is recommended to provide a link to a license type (e.g. http://creativecommons.org/licenses/by/3.0), a website or to a document containing the necessary information."
"TG Requirement C.10: metadata/2.0/req/common/responsible-organisation The point of contact for the organisation responsible for the establishment, management, maintenance and distribution of the described resource shall be given using element gmd:pointOfContact/gmd:CI_ResponsibleParty. The multiplicity of this element is 1..*. The gmd:CI_ResponsibleParty element shall contain the following child elements: The name of the organisation shall be given as the value of gmd:pointOfContact/gmd:CI_ResponsibleParty/gmd:organisationName element with a Non-empty Free Text Element content. The email address of the organisation shall be provided as the value of gmd:pointOfContact/gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/gmd:electronicMailAddress element with a Non-empty Free Text Element containing a functioning email address of the responsible party. The value of gmd:pointOfContact/gmd:CI_ResponsibleParty/gmd:role/gmd:CI_RoleCode shall point to the most relevant value of ISO 19139 code list CI_RoleCode. Note : Attribute codeList shall be ""http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#CI_RoleCode""."
"TG Recommendation C.5: metadata/2.0/rec/common/responsible-organisation The name of the organisation should be given in full, without abbreviations. It is recommended to use an email address of the organisation instead of personal email address."
"TG Requirement C.6: metadata/2.0/req/common/md-point-of-contact Point of contact for the responsible party for the provided metadata shall be given using element gmd:MD_metadata/gmd:contact/gmd:CI_ResponsibleParty. The multiplicity of this element is 1..*. The gmd:CI_ResponsibleParty element shall contain the following child elements: The name of the responsible organisation shall be provided as the value of gmd:organisationName element with a Non-empty Free Text Element content. The email address of the organisation shall be provided as the value of gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/gmd:electronicMailAddress element with a Non-empty Free Text Element containing a functioning email address of the responsible party. The value of gmd:role/gmd:CI_RoleCode shall point to the value ""pointOfContact"" of [ISO 19139] code list CI_RoleCode21." "TG Recommendation C.2: metadata/2.0/rec/common/organisation-name The name of the organisation should be given in full, without abbreviations. It is recommended to use an email address of the organisation instead of personal email address."
gmd:contact gmd:CI_ResponsibleParty gmd:organisationName gco:CharacterStringEuropean Commission, Joint Research Centregco:CharacterString </gmd:organisationName> gmd:contactInfo gmd:CI_Contact gmd:address gmd:CI_Address gmd:electronicMailAddress gco:CharacterString ies-contact@jrc.ec.europa.eu</gco:CharacterString> </gmd:electronicMailAddress> </gmd:CI_Address> </gmd:address> </gmd:CI_Contact> </gmd:contactInfo> gmd:role <gmd:CI_RoleCode codeList="http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#CI_RoleCode" codeListValue="pointOfContact"></gmd:CI_RoleCode> </gmd:role> </gmd:CI_ResponsibleParty> </gmd:contact> "TG Requirement C.7: metadata/2.0/req/common/md-date The latest update date of the metadata description shall be given for each metadata record. It shall be encoded using the gmd:MD_Metadata/gmd:dateStamp element. If no updates to the metadata have been made since publishing it, the creation date of the metadata shall be used instead. The multiplicity of this element is 1."
"TG Requirement C.5: metadata/2.0/req/common/metadata-language-code The language of the provided metadata content shall be given. It shall be encoded using gmd:MD_Metadata/gmd:language/gmd:LanguageCode element pointing to one of the three-letter language codes of the ISO 639-2/B code list. Only the code values for the official languages of the European Union shall be used. The multiplicity of this element is 1. Note : Attribute codeList shall be ""http://www.loc.gov/standards/iso639-2/"" and the attribute codeListValue shall contain one of the three-letter bibliographic language code values. Note : At the time of writing there are 24 official languages of the EU, see http://ec.europa.eu/languages/policy/linguistic-diversity/official-languages-eu_en.htm" " TG Recommendation C.1: metadata/2.0/rec/common/metadata-language-name The name of the language(s) of the described resource in the language of the metadata should be used as the text content of the gmd:LanguageCode element."
"TG Recommendation C.1: metadata/2.0/rec/common/fileIdentifier The metadata record should contain a globally unique and persistent fileIdentifier element." "TG Recommendation 2.5: metadata/2.0/rec/isdss/recommended-theme-specific-md-elements The recommended metadata elements should be included to metadata describing a spatial dataset or spatial dataset series related to the annex themes specified for the relevant element in Annex C.7."