2.4.46 Language of the metadata
From Geostandards
- 2.1.1 What is metadata?
- 2.1.2 Why metadata?
- 2.1.3 What can you do with it?
- 2.1.4 Where can you find metadata?
- 2.1.5 Applications
- 2.1.6 Discovery discovery
- 2.2.1 What is a standard for?
- 2.2.2 Standards for geo-information
- 2.2.3 Metadata standards
- 2.2.4 INSPIRE
- 2.2.5 Discovery standards
2.3 Metadata in the working process
- 2.3.1 How do you make metadata?
- 2.3.2 How do you make metadata from services?
- 2.3.3 Where in the working process?
- 2.3.4 Tips for gathering metadata
- 2.3.5 Publishing metadata
- 2.3.6 Harvesting
- 2.3.7 Validating
- 2.3.8 Discovery working process
- 2.4.0 Overview of metadata elements
- 2.4.1 Title of the resource
- 2.4.2 Summary
- 2.4.3 Status
- 2.4.4 Level of hierarchy
- 2.4.5 URL
- 2.4.6 Protocol
- 2.4.7 Name
- 2.4.8 Unique Identifier of the resource
- 2.4.9 Language of the resource
- 2.4.10 Subject
- 2.4.11 Keyword
- 2.4.12 Thesaurus
- 2.4.13 Thesaurus date
- 2.4.14 Thesaurus date type
- 2.4.15 Minimum x-coordinate
- 2.4.16 Maximum x-coordinate
- 2.4.17 Minimum y-coordinate
- 2.4.18 Maximum y-coordinate
- 2.4.19 Temporal cover
- 2.4.20 Date of the resource
- 2.4.21 Date type of the resource
- 2.4.22 Grade of the description of quality
- 2.4.23 General description of origin
- 2.4.24 Scale of application
- 2.4.25 Resolution
- 2.4.26 Code Reference system
- 2.4.27 Responsible organisation for namespace reference system
- 2.4.28 Conformity indication with the specification
- 2.4.29 Clarification
- 2.4.30 Specification
- 2.4.31 Specification date
- 2.4.32 Specification date type
- 2.4.33 Legal restrictions to accessibility
- 2.4.34 Other constraints
- 2.4.35 Security restrictions
- 2.4.36 User constraints
- 2.4.37 Responsible organisation resource
- 2.4.38 Responsible organisation resource: email
- 2.4.39 Responsible organisation resource: role
- 2.4.40 Metadata unique identifier
- 2.4.41 Parent unique identifier
- 2.4.42 Responsible organisation metadata
- 2.4.43 Responsible organisation metadata: role
- 2.4.44 Responsible organisation metadata: email
- 2.4.45 Metadata date
- 2.4.46 Language of the metadata
- 2.4.47 Metadata standard name
- 2.4.48 Metadata Standard version
- 2.4.49 Discovery metadata for data
2.5 Metadata elements for services
- 2.5.0 Metadata elements for services overview
- 2.5.1 Resource Title
- 2.5.2 Resource abstract
- 2.5.3 Resource type
- 2.5.4 Resource locator
- 2.5.5 Connect Point Linkage
- 2.5.6 Coupled resource
- 2.5.7 Scoped Name
- 2.5.8 Coupling Type
- 2.5.9 Spatial data service type
- 2.5.10 Service Type Version
- 2.5.11 Operation Name
- 2.5.12 DCP
- 2.5.13 Keyword value
- 2.5.14 Originating controlled vocabulary
- 2.5.15 Geographic location
- 2.5.16 Temporal Reference
- 2.5.17 Spatial resolution
- 2.5.18 Degree
- 2.5.19 Specification
- 2.5.20 Constraints
- 2.5.21 Conditions applying to access and use
- 2.5.22 Responsible party
- 2.5.23 Responsible party role
- 2.5.24 Metadata point of contact
- 2.5.25 Metadata language
- 2.5.26 Metadata date
- 2.5.27 The link to the metadata of the dataset and dataset series from the service
- 2.5.28 Discovery metadata for services
In this element ‘Language of the metadata’ the language that the metadata has been described in is given. Use only the three-letter codes for this from 639-2/B (bibliographic codes), as defined on http://www.loc.gov/standards/iso639-2/.
For the Netherlands the default value is in general: dut.
The codes for the 23 official EU languages are:
2.4.47 Metadata Standard name
The metadata element ‘Standard name’ is necessary for interpreting the increases in the profiles. This element contains the name of the standard.
Example: ISO 19115
2.4.48 Metadata standard version
The metadata element ‘Standard version’ is needed to indicate increases in standards. This element contains the version (profile) of the metadata standard that is used.
Example:
Dutch metadata profile on ISO 19115 for geography 1.2
2.4.49. Discovery metadata of data
2.4.5 URL
The metadata element ‘URL’ contains a valid URL for online access to the resource, i.e. to a WMS or a zip file, or if there is no direct link available to the resource, then to the location where information about the resource is available such as an office or in a catalog.
By making a link to a data service, it is possible to search the metadata of the data and to show the data via its service. The service also has metadata; however that does not include information about the content of the data. By using the element protocol one knows what kind of information it is, be it a file to download, or a service etc.
In this element ‘URL’ the link is only made once for each service type (WMS, WFS), which represents the dataset as a service, in order to make it possible to approach the dataset via a service. It is not intended that a link be made to each service which the dataset is included in.
However it is possible to adopt both a URL to a file to download and a URL to a WMS. The elements protocol and name should therefore be entered more than once.
The URL for a service should be equal to the metadata element resource locator of the Dutch metadata profile on ISO19119 for services.
The element URL is conditional. It is mandatory if there is a link to (more information about) the resource. For example to a zip file, a catalog, a data office, WMS or WFS.
Examples:
1. -
2. http://www.dinoservices.nl/wms/dinomap/M09M0817
3. \\COM5494\G$\nwb_wegen\geogegevens\shapefile\nederland_totaal\hectopunten\hectopunten.shp
4. http://geoservice.pbl.nl/website/gcn/Stikstofdioxide/2020
2.4.6 Protocol
The metadata element ‘Protocol’ contains the protocol for dealing with the URL. The URL can be both a link to a file to download, and/or to a service or a catalog. The element protocol indicates what kind of URL it is. Downloaded files are, for example, zip, PDF and Word documents.
The element protocol is important for enabling the dataset to be downloaded automatically, and/or for approaching the service representing the dataset. It uses a list of codes recorded by the Dutch metadata profile on ISO19119, however the element is an ISO19115 element. By using this list of codes the completion of the element software is independent.
This element is conditional. It is mandatory if a URL is indicated. For example to a zip file, WMS or WFS.
The following values may be used for protocol;
| Name | Description | MD IR Name |
| OGC:CSW | Web Catalog service | Discovery Service |
| OGC:WMS | Web Map service | View Service |
| OGC:WFS | Web Feature Service | Download Service |
| OGC:WCS | Web Coverage Service | Download Service |
| OGC:WCTS | Web Coordinate Transformation Service | Transformation Service |
| OGC:WPS | Web Processing Service | Invoke Spatial Data Service |
| UKST | Unknown Service Type | Other Services |
| OGC:WMC | Web Map Context | |
| OGC:KML | Keyhole Mark-up Language | |
| OGC:GML | Geography Markup Language | |
| OGC:WFS-G | Gazzetteer service | |
| OGC:SOS | Sensor Observation Service | |
| OGC:SPS | Sensor Planning Service | |
| OGC:SAS | Sensor Alert Service | |
| OGC:WNS | Web Notification Service | |
| OGC:ODS | OpenLS Directory Service | |
| OGC:OGS | OpenLS Gateway Service | |
| OGC:OUS | OpenLS Utility Service | |
| OGC:OPS | OpenLS Presentation Service | |
| OGC:ORS | OpenLS Route Service | |
| website | website | |
| download | download |
Examples: 1. - 2. OGC:WMS 3. Download 4. website
| ← previous | 2 Metadata | next → |
