Spreadsheet: 339b478c-bfe7-42eb-a61f-fae8fbdbec80
Sheet: Sheet1

Unnamed: 0 | Unnamed: 1 | OPEN DATA PORTAL Metadata defintions | Unnamed: 3 | Unnamed: 4 | Unnamed: 5 | Unnamed: 6 | Unnamed: 7 | Annex 1
 | [NAME] field | [NAME] field description | Value example | Cardinality | Datatype | Controlled vocabulary (NAL) | Multi lingual support | Comments
 | Notes: 1. Any valid dataset [NAME] can be accepted using the RDF input. [NAME] that corresponds to the model elements below will be validated and made available from DAR (dataset and applications register). All of the RDF metadata will be made available from TRS (triple store). 2. EuroVoc integration is planned  3. The PO NALs that will be used  are corporate bodies, countries and languages 4. The ADMS mapping state is provisional – the ADMS specification although version 0.98 leaves many questions open (e.g. RDF mapping missing, controlled vocabularies not yet published) 5. ODP triple store will contain only metadata about datasets for M6. Datasets will linked to through the DAR. They are normally hosted by the publisher but ODP offers the possibility to upload and host datasets in any data format (e.g. RDF, XLS, CSV files). Linking is the preference. Hosting should only be provided for publishers who don't have the infrastructure ready for publishing. 6. If  [NAME] is uploaded using RDF, it has to be updated using the RDF channel (i.e. no updates from the UI)
Nr | Descriptive metadata
1 | dataset / title | A short descriptive primary title for the dataset. It should not be a description though - save that for the [NAME] field. Do not give a trailing full stop. Do not use allcaps. | Digital [NAME] | 1..1 | RDF Literal | No | Yes | The cardinality is set on the values, not translations of values. So there can be many entries for the title, but each must be in a different language.
2 | dataset / alternative title | Alternative title | Scoreboard | 0..* | RDF Literal | No | Yes
3 | dataset / description | The main description of the dataset. | European Commission services selected around 60 indicators, divided into thematic groups, which illustrate some key dimensions of the European information society (Broadband, Internet usage, Internet services, eGovernment, eCommerce, eBusiness). These indicators allow a comparison of progress across European countries as well as over time. You can also browse the data with the help of a visualisation tools going at http://scoreboard.lod2.eu/ (where you are also able to download selected information in CSV and RDF). The database with the selected indicators of the Digital Agenda Scoreboard is made of three tables:  • a data table, with codes for the indicators, countries, years and values  • an indicators table, with labels for indicators' codes, definition and scope, and a source code  • a sources table, with details about sources and links to more methodological information The codes allow the creation of relations between the tables. | 1..* | RDF Literal | No | Yes | IMPORTANT: request came in to make this field required to be filled in; rationale: the user cannot judge based on the title alone if a set is relevant for his information need. It is often displayed with the package title. In particular, it should start with a short sentence that describes the data set succinctly, because the first few words alone may be used in some views of the data sets. You can use Markdown (http://daringfireball.net/projects/markdown/syntax) formatting here. In ODP prototype 2 there were 2 properties "description" and "note", was decided to drop "note" with the intention to simplify the model
4 | dataset / [NAME] | Word/phrase that describes the dataset. | e-commerce broadband e-government inclusion information-society benchmarking internet | 0..* | RDF Literal | No | Yes | For more information on conventions, see this wiki (http://wiki.okfn.org/ckan/doc/faq#TagConventions) page. e.g. pollution rivers water-quality Tags must be alphanumeric characters or symbols: -_. Tags must not be uppercase words in phrases connected with hyphen.  [NAME], when EuroVoc integration is present, keywords will also be based on terms. Then dct:subject and dct:theme also become relevant.
5 | dataset / identifier | Assigned other identifiers | Literal identifiers, e.g. CELEX number, etc. | 0..* | RDF Literal | No | No
6 | dataset / URI | Uniform resource identifier | http://ec.europa.eu/open-data/dataset123 | 1..1 | URI | No | No
7 | dataset / interoperability level | Interoperability level for which the dataset is relevant | http://purl.org/adms/interoperabilitylevel/Political | 0..1 | NAL code | Yes | Yes (using NAL) | Based on ADMS definition: http://purl.org/adms/interoperabilitylevel/Political http://purl.org/adms/interoperabilitylevel/Legal http://purl.org/adms/interoperabilitylevel/Organisational http://purl.org/adms/interoperabilitylevel/Semantic http://purl.org/adms/interoperabilitylevel/Technical
8 | dataset / type | Type of the dataset | http://purl.org/adms/assettype/Taxonomy http://purl.org/adms/assettype/Thesaurus | 0..* | NAL code | Preferable (to be defined), partly ADMS | Yes (using NAL) | ADMS specifies a NAL but it's incomplete and based on interoperability level. Can be used for Semantic interoperability level: http://purl.org/adms/assettype/CoreComponent http://purl.org/adms/assettype/Ontology http://purl.org/adms/assettype/DomainModel http://purl.org/adms/assettype/Schema http://purl.org/adms/assettype/InformationExchangePackageDescription http://purl.org/adms/assettype/Thesaurus http://purl.org/adms/assettype/Taxonomy http://purl.org/adms/assettype/CodeList http://purl.org/adms/assettype/NameAuthorityList http://purl.org/adms/assettype/Mapping http://purl.org/adms/assettype/SyntaxEncodingScheme http://purl.org/adms/assettype/ServiceDescription
 | Links and resources
9 | dataset / documentation | Documentation or specification of the dataset |  | 0..* | Resource | No | No
10 | dataset / documentation / type | Type of the documentation | main related webpage... | 1..1 | NAL code | Preferable (to be defined) | Yes (using NAL) | Based on ADMS, which introduces in V 0.98 the concepts: main documentation, related documentation and related web page.
11 | dataset / documentation / URL | URL to access the documentation |  | 1..1 | URL | No | No
12 | dataset / documentation / title | Title of the documentation | documents API usage | 1..1 | RDF Literal | No | Yes | ADMS specifies 1..*, not supported for now. It is supposed that ADMS defines 1..* to support multilingualism, which is implicit for the ODP (see "title").
13 | dataset / distribution | The files containing the data or address of the APIs for accessing it. These can be repeated as required. For example if the data is being supplied in multiple formats, or split into different areas or time periods, each file is a different 'resource' which should be described differently. They will all appear on the dataset page on CKAN together. |  | 0..* | Resource | No | No
14 | dataset / distribution / URL | This is the Internet link directly to the data - by selecting this link in a web browser, the user will immediately download the full data set. | http://scoreboard.lod2.eu/data/digital_scoreboard_01_june_2011.xls | 1..1 | URL | No | No | Note that datasets are in general not hosted by the ODP, but by the publisher of the data. Alternatively the URL can point to an API server such as a SPARQL endpoint or JSON-P service.  ADMS specifies 1..*, not supported for now
15 | dataset / distribution / type | Type of the distribution | Feed WebService Download ... | 1..1 | NAL code | Preferable (to be defined) | Yes (using NAL)
16 | dataset / distribution / format | This should give the file format in which the data is supplied. | xls | 1..1 | NAL code | Preferable (to be defined) | Yes (using NAL) | Proposal to use the file extension in lowercase examples: xls, csv, rdf/xml, sql, turtle, n-triples if compressed, used nested format examples: zip:xls, gz:csv if api, then prefixed by 'api/' examples: api/sparql, api/json
17 | dataset / distribution / description | Any information you want to add to describe the distribution | 3 worksheets with the indicators, sources and data tables | 0..1 | RDF Literal | No | Yes | ADMS specifies 0..*, not supported for now
18 | dataset / distribution / issued date | issued date of the resource | 24.03.2001 | 0..1 | Datetime | No | No
19 | dataset / distribution / last modification date | last modification date of the resource | 24.03.2001 | 0..1 | Datetime | No | No
20 | dataset / catalog record | [NAME] about the dataset's entry in the catalog. |  | 0..* | Resource | No |  | To be able to make a distinction between metadata about the dataset and metadata about the dataset's entry in the catalog.
21 | dataset / catalog record / issued | issued date of the catalog record | 24.03.2001 | 0..1 | Datetime | No | No | dcat definition not yet stable. To be adapted to dcat.
22 | dataset / catalog record / last modification date | last modification date of the catalog record | 24.03.2001 | 0..1 | Datetime | No | No
 | Applicability
23 | dataset / geographical coverage | Geographic region or jurisdiction to which the dataset applies | EU27, Norway | 0..* | NAL code | Yes (countries and/or places and/or NUTs) | Yes (using NAL)
 | Provenance
24 | dataset / publisher | the publisher of the dataset | INFSO | 1..1 | NAL code | Yes (corporate bodies) | Yes (using NAL)
25 | dataset / contact point | The name of the main contact, for enquiries about this particular dataset REMARK: it is against EC policies to publicize names of collaborators. SUGGESTION: use the full name of the responsible unit | Unit C4 - Economic and statistical analysis | 0..1 | Resource | No | No
26 | dataset / contact / full address | the full address of the contact point |  | 0..1 | RDF Literal | No | No
27 | dataset / contact / e-mail | the e-mail address of the contact point |  | 0..1 | RDF Literal | No | Np
28 | dataset / contact / name | The name of the contact point |  | 1..1 | RDF Literal | No | Yes
29 | dataset / contact / telephone | the telephone of the contact point |  | 0..1 | URI | No | No
30 | dataset / contact / web page | the web page of the contact point |  | 0..1 | URL | No | No
31 | dataset / issued | Date of formal issuance (e.g., publication) of the dataset. | 24.03.2001 | 0..1 | Datetime | No | No
32 | dataset / last modification date | Most recent date on which the dataset was changed, updated or modified. | 24.03.2001 | 1..1 | Datetime | No | No
33 | dataset / version | References to revisions of the dataset |  | 0..1 | URI | No | No | For now, limited to 1 – details the actual version of the dataset in question
34 | dataset / version / identifier | A literal representing the version | 1.2.0a | 0..1 | RDF Literal | No | No
35 | dataset / version / description | Description of changes between this version and the previous version of the dataset | Updated the dataset for new EU countries. | 0..1 | RDF Literal | No | Yes
 | Availablity
36 | dataset / licence | The licence under which the dataset is released. |  | 1..* | NAL code | Preferable (to be defined) | Yes (using NAL)
37 | dataset / status | Dataset status | published/withdrawn/draft/... | 1..1 | NAL code | Yes (ADMS) | Yes (using NAL) | Status was dropped on distribution level (present and mandatory on ADMS). The rationale - disitribution can be any resource, even if the publishing status is unknown. When exporting to ADMS, the mandatory distribution/status would be set to same value as dataset/status
38 | dataset / language | Language coverage | en;fr | 0..* | NAL code | Yes (languages) | Yes (using NAL)
39 | dataset / acrrual periodicity | The frequency with which the dataset is published. | Twice a day | 0..1 | NAL code | Preferable (to be defined) | Yes (using NAL)
40 | dataset / temporal coverage | Dataset applicability period |  | 0..1 | Resource | No | No
41 | dataset / temporal coverage / coverage from | start of temporal series used in dataset | 1981 | 0..1 | Datetime | No | No
42 | dataset / temporal coverage / coverage to | end of temporal series used in dataset | 2010 | 0..1 | Datetime | No | No
43 | dataset / temporal coverage / granularity | day | month | year | month | 0..1 | NAL code | Preferable (to be defined) | Yes (using NAL)