Jump to: navigation, search

Ritmare metadata

Revision as of 10:39, 16 November 2013 by Cfugazza (Talk | contribs)

Notes

  • Elements "identificatore del file" (fileIdentifier) e "id file precedente" (parentIdentifier) allow to link one another individual dataset in a time series.
  • Elements "Identificatore" (identifier) e "Id livello superiore" (series) link dataset in a series (as intended by INSPIRE) and the series itself.

Perhaps it is possible to express the behaviour enabled by these four identifiers with just two of them. As an example, an identifier of type iPA:cod-Ente:yyyymmdd:hhmmss could be extended to include additional information, such as:

iPA:cod-Ente:id-dataset:yyyymmdd:hhmmss

so that individual datasets still have unique identifiers but time series "id-dataset" can be singled out.

  • Elements "Risorsa accoppiata" and "Risorsa on-line", respectively, relate a service to datasets that can be applied as input and a dataset to services that can process it.

Elements may have further purposes.

INSPIRE RNDT SensorML ODP RDF mapping Notes
Identification
Resource title [1](*) Titolo [1](*) dataset / title <dataset URI> dct:title "title"
Unique resource identifier [1...n](*) Identificatore del file [1](*) / Identificatore [1](*) 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, 3) RDF triple for gmd:codeSpace to be added 4) once chosen a codespace for ritmare (es. http://ritmare.cnr.it/), we can use a URN of format iPA:cod-Ente:aaaammgg:hhmmss as Unique resource identifier and codespace+URN as dataset / URI
Resource abstract(*) Descrizione dataset / description <dataset URI> dct:description "description"
Resource Type [1](*) Livello gerarchico [1](*) 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
Id file precedente [1](*) for the first version of a dataset, it is same as Identificatore del file
Id livello superiore [1](*)
Resource language [0...n] Lingua [1](*) 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 [1...n](*) Categoria tematica [1...n](*) 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; 3) need to store a URI
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; 3) need to store a URI
Formato di presentazione [1...n](*) creare thesaurus da 3.4.3.2 - all. 2 DM
Altri dettagli [0...n]
Informazioni supplementari [0...1]
Set di caratteri [0...n]
Tipo di rappresentazione spaziale [1...n](*)
Keyword
Keyword value Parole chiave 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; 3) need to store a URI
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 [1] Localizzazione geografica [1] dataset / geographical coverage <dataset URI> dct:spatial <spatial URI> may not be sufficient to express a bounding box
Estensione verticale [0...1]
Temporal reference
Temporal extent Estensione temporale dataset / temporal coverage / coverage from

dataset / temporal coverage / coverage to

<dataset URI> dct:temporal <period>

<period> ecodp:periodStart <datetime>

<period> ecodp:periodEnd <datetime>

Not mandatory but at least one temporal reference is required
Date of publication Data dataset / issued <dataset URI> dct:issued <datetime> Not mandatory but at least one temporal reference is required
Date of last revision Data dataset / last modification date <dataset URI> dct:modified <datetime> Not mandatory but at least one temporal reference is required
Date of creation Data ? ? Not mandatory but at least one temporal reference is required
Conformity
Degree ? ?
Specification ? ?
Quality and validity
Lineage [1] for data, [0...n] for services Genealogia [1](*)
Spatial resolution [0...n] Risoluzione spaziale [0...n]
Livello di qualità [1](*)
Accuratezza posizionale [1](*)
Constraints related to access and use
Limitations on public access [1...n](*) Vincoli di accesso [1...n](*) dataset / licence <dataset URI> dct:license <license URI> 1) add ISO codelist to thesauri; 2) mismatch with NAL codes
Conditions applying to access and use [1...n](*) Limitazione d’uso [1](*) ? ?
Vincoli di fruibilità [1...n](*)
Altri vincoli [0...n] come per Vincoli di accesso
Vincoli di sicurezza [1] come per Vincoli di accesso
Responsible organisation
Responsible party [1](*) Punto di contatto [1...n](*) <dataset URI> dct:publisher <publisher URI> <dataset URI> ecodp:contactPoint <contactPointURI> 1) verify http://publications.europa.eu/resource/authority/corporate-

body/INFSO; 2) 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)

Responsabile [1..n](*)
Responsible party role ? ?
Metadata on metadata
Metadata point of contact [1...n](*) Responsabile dei metadati [1...n](*) ? ? 1) need to provide: institution, role, website OR telephone number, email 2) add website to RITMARE partners and/or telephone number
Metadata date [1](*) Data dei metadati [1](*) dataset / catalog record / issued <record URI> dct:issued <datetime>
Metadata language [1](*) Lingua dei metadati [1](*) ? ? the ODP format does not reserve a field for the meadata language
Set dei caratteri dei metadati [0...1] we could make if fixed (e.g., utf8); anyway, it's optional
Nome dello Standard [1](*) fixed "DM - Regole tecniche RNDT"
Versione dello Standard [1](*) fixed "10 novembre 2011"

(*) = mandatory item