Difference between revisions of "Ritmare metadata"
| Line 47: | Line 47: | ||
|dataset / keyword | |dataset / keyword | ||
|<dataset URI> ecodp:keyword "keyword" | |<dataset URI> ecodp:keyword "keyword" | ||
| − | |1) use the originating thesaurus to distinguish between Topic category, Spatial data service type, and keywords; 2)use prefLabel (in the language associated with metadata) for a text representation | + | |1) use the originating thesaurus to distinguish between Topic category, Spatial data service type, and keywords; 2)use prefLabel (in the language associated with metadata) for a text representation |
|- | |- | ||
|Spatial data service type | |Spatial data service type | ||
|dataset / keyword | |dataset / keyword | ||
|<dataset URI> ecodp:keyword "keyword" | |<dataset URI> ecodp:keyword "keyword" | ||
| − | |1) use the originating thesaurus to distinguish between Topic category, Spatial data service type, and keywords; 2)use prefLabel (in the language associated with metadata) for a text representation | + | |1) use the originating thesaurus to distinguish between Topic category, Spatial data service type, and keywords; 2)use prefLabel (in the language associated with metadata) for a text representation |
|- | |- | ||
!colspan="4" | Keyword | !colspan="4" | Keyword | ||
| Line 59: | Line 59: | ||
|dataset / keyword | |dataset / keyword | ||
|<dataset URI> ecodp:keyword "keyword" | |<dataset URI> ecodp:keyword "keyword" | ||
| − | |1) use the originating thesaurus to distinguish between Topic category, Spatial data service type, and keywords; 2) use prefLabel (in the language associated with metadata) for a text representation | + | |1) use the originating thesaurus to distinguish between Topic category, Spatial data service type, and keywords; 2) use prefLabel (in the language associated with metadata) for a text representation |
|- | |- | ||
|Originating controlled vocabulary | |Originating controlled vocabulary | ||
| | | | ||
| | | | ||
| − | |1) implied by keyword value; 2) use prefLabel (in the language associated with metadata) for a text representation | + | |1) implied by keyword value; 2) use prefLabel (in the language associated with metadata) for a text representation, use the thesaurus publication date and type |
|- | |- | ||
!colspan="4" | Geographic location | !colspan="4" | Geographic location | ||
Revision as of 13:11, 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(*) | dataset / type | <dataset URI> ecodp:datasetType <datasetTypeURI> | compare INSPIRE codelist with http://ec.europa.eu/open-data/kos/dataset-type/Taxonomy http://ec.europa.eu/open-data/kos/dataset-type/Thesaurus |
| Resource locator(*) | dataset / distribution / URL | <distribution URI> dcat:accessURL "URL" | a "distribution" entity shall be created for each resource |
| Coupled resource | ? | ? | find suitable ODP metadata field to express this |
| Resource 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 |
| Classification of spatial data and services | |||
| Topic category | dataset / keyword | <dataset URI> ecodp:keyword "keyword" | 1) use the originating thesaurus to distinguish between Topic category, Spatial data service type, and keywords; 2)use prefLabel (in the language associated with metadata) for a text representation |
| Spatial data service type | dataset / keyword | <dataset URI> ecodp:keyword "keyword" | 1) use the originating thesaurus to distinguish between Topic category, Spatial data service type, and keywords; 2)use prefLabel (in the language associated with metadata) for a text representation |
| Keyword | |||
| Keyword value | dataset / keyword | <dataset URI> ecodp:keyword "keyword" | 1) use the originating thesaurus to distinguish between Topic category, Spatial data service type, and keywords; 2) use prefLabel (in the language associated with metadata) for a text representation |
| Originating controlled vocabulary | 1) implied by keyword value; 2) use prefLabel (in the language associated with metadata) for a text representation, use the thesaurus publication date and type | ||
| 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(*) | ? | the ODP format does not reserve a field for the meadata language | |
(*) = mandatory item