Jump to: navigation, search

Difference between revisions of "Ritmare metadata"

Line 5: Line 5:
 
!Notes
 
!Notes
 
|-
 
|-
!colspan="2" | Identification
+
!colspan="4" | Identification
 
|-
 
|-
 
|Resource title(*)
 
|Resource title(*)
Line 22: Line 22:
 
|
 
|
 
|-
 
|-
|Resource Type(*)
+
|(Resource Type(*)) not here
 
|...
 
|...
 
|-
 
|-

Revision as of 12:31, 12 November 2013

INSPIRE ODP RDF mapping Notes
Identification
Resource title(*) dataset / title <dataset URI> dct:title "title"
Unique resource identifier(*) dataset / URI <dataset URI> rdf:type dcat:Dataset 1) INSPIRE mandates a unique identifier, ODP metadata refer to a DCAT dataset, 2) not mandatory for services
Resource abstract(*) dataset / description <dataset URI> dct:description "description"
(Resource Type(*)) not here ...
Resource locator ...
(Coupled resource) not here ...
Resource language ...
Classification of spatial data and services
Topic category ...
Spatial data service type ...
Keyword
Keyword value ...
Originating controlled vocabulary ...
Geographic location
Geographic bounding box ...
Temporal reference
Temporal extent ...
Date of publication ...
Date of last revision ...
Date of creation ...
Conformity
Degree ...
Specification ...
Constraints related to access and use
Limitations on public access ...
Conditions applying to access and use ...
Responsible organisation
Responsible party ...
Responsible party role ...
Metadata on metadata
Metadata point of contact(*) dataset / contact point <dataset URI> ecodp:contactPoint <contactPointURI> the ODP metadata format requires this value to be a resource: using the FOAF entity describing a RITMARE individual provides the data items required by INSPIRE (organisation name, E-mail)
Metadata date dataset / catalog record / issued <record URI> dct:issued <datetime>
Metadata language(*) dataset / language <dataset URI> dct:language "<NAL code>" NAL codes are different from those used in INSPIRE metadata, requires mapping between the two SKOS thesauri

(*) = mandatory item