mobilityDCAT-AP - Version 3.0.0

Abstract

mobilityDCAT-AP is a mobility-related extension of the DCAT application profile for data portals in Europe DCAT-AP v3.0.0. It allows for a structured, interoperable and harmonised way to describe and exchange metadata about data platforms and datasets with a mobility relevance.

This document is a product of the NAPCORE Metadata Working Group.

Comments and queries should be sent via the issue tracker of the dedicated GitHub repository.

Version	Date	Description	Action	Change Log
3.0.0	xx/xx/2025	Major semantic release	Publication	I.1 Changes since mobilityDCAT-AP 1.1.0 (17 January 2025)
1.1.0	17/01/2025	Minor semantic release	Publication	I.2 Changes since mobilityDCAT-AP 1.0.1 (04 April 2024)
1.0.1	04/04/2024	Bug fix release	Publication	I.3 Changes since mobilityDCAT-AP 1.0.0 (16 October 2023)
1.0.0	16/10/2023	Recommendation	Publication	I.4 Starting point of mobilityDCAT-AP 1.0.0 (01 January 2023)
0.1	11/05/2023	First Public Working Draft	Creation	N/A

Prefix	Namespace URI	Specification
`adms`	`http://www.w3.org/ns/adms#`	[VOCAB-ADMS]
`cnt`	`http://www.w3.org/2011/content#`	[CNT]
`dcat`	`http://www.w3.org/ns/dcat#`	[VOCAB-DCAT-2]
`dcatap`	`http://data.europa.eu/r5r/`	[DCAT-AP]
`dct`	`http://purl.org/dc/terms/`	[DCTERMS]
`dqv`	`http://www.w3.org/ns/dqv#`	[VOCAB-DQV]
`eli`	`http://data.europa.eu/eli/ontology#`	[ELI]
`foaf`	`http://xmlns.com/foaf/0.1/`	[FOAF]
`locn`	`http://www.w3.org/ns/locn#`	[CORE-LOCATION-VOCABULARY]
`oa`	`https://www.w3.org/ns/oa#`	[WEB-ANOTATION-ONTOLOGY]
`org`	`https://www.w3.org/ns/org#`	[CORE-ORGANIZATION-ONTOLOGY]
`owl`	`http://www.w3.org/2002/07/owl#`	[OWL-REF]
`rdf`	`http://www.w3.org/1999/02/22-rdf-syntax-ns#`	[RDF11-CONCEPTS]
`rdfs`	`http://www.w3.org/2000/01/rdf-schema#`	[RDF-SCHEMA]
`skos`	`http://www.w3.org/2004/02/skos/core#`	[SKOS-REFERENCE]
`spdx`	`http://spdx.org/rdf/terms#`	[SPDX]
`vcard`	`http://www.w3.org/2006/vcard/ns#`	[VCARD-RDF]
`xsd`	`http://www.w3.org/2001/XMLSchema#`	[XMLSCHEMA11-2]

A quick reference table of properties per class is included in A. Quick Reference of Classes and Properties.

Definition	An entity (e.g., an individual or an organisation) that is associated with Catalogues, Catalogue Records, or Datasets.
URI	`foaf:Agent`
References	DCAT: Link DCAT-AP: Link geoDCAT-AP: Link
Usage note	If the agent is an organisation, the use of the Organization Ontology is recommended. See 11. Agent Types, Agent Roles and Contact Information for a discussion on Agent types, roles and properties. The agent might be populated with the same information as for a kind, see class `vcard:Kind`. See 11. Agent Types, Agent Roles and Contact Information for further usage notes on that matter. When providing agent information, data publishers SHOULD prioritize organizational information over personal details. The exposure of personal information, such as a personal name and email address, may be restricted to the public. Instead, there might be an anonymous contact channel, e.g. a contact button on the GUI that triggers an email to the agent. See 13. Privacy and security considerations.
Properties	For this entity the following properties are defined: address, affiliation, email, first name, name, phone, surname, type, URL.

Property name and URI	Range	Card.	Definition	Usage note	Reuse
+address `locn:address`	`locn:Address`	0..1	The postal address of the agent.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GA
+affiliation `org:memberOf`	`org:Organization`	0..1	The affiliation of the agent.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GA
+email `foaf:mbox`	`rdfs:Resource`	0..1	The email address of the agent, specified using fully qualified mailto: URI scheme RFC6068.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GA
+first name `foaf:firstName`	`rdfs:Literal`	0..1	The first name of the agent.	To be used if the agent is of type person, see 11. Agent Types, Agent Roles and Contact Information.	P
name `foaf:name`	`rdfs:Literal`	1..*	A name of the agent.	This property can be repeated for different versions of the name (e.g. the name in different languages) - see 12. Accessibility and Multilingual Aspects.	A
+phone `foaf:phone`	`rdfs:Resource`	0..1	The phone number of the agent, specified using fully qualified tel: URI scheme RFC3966.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GA
+surname `foaf:surname`	`rdfs:Literal`	0..1	The surname of the agent.	To be used if the agent is of type person, see 11. Agent Types, Agent Roles and Contact Information.	P
type `dct:type`	`skos:Concept`	0..1	The nature of the agent.	A controlled vocabulary is provided.	E
+URL `foaf:workplaceHomepage`	`rdfs:Resource`	0..1	The Web site of the agent.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GA

Definition	An assessment procedure by an external organisation. This organisation may be a National Body in the context of EU Delegated Regulations. EU Delegated Regulations require Member States to set up procedures to assess the compliance with the applicable Delegated Regulations, e.g. regarding the provisioning of data via a NAP. These assessment processes are handled by National Bodies and installed individually in each Member State.
URI	`mobilitydcatap:Assessment`
References	DCAT: none DCAT-AP: none geoDCAT-AP: none
Usage note	The information is optional and needed for the documentation of the assessment procedure. It may be an internal information, only visible for assessment organisations or other authorised users.
Properties	For this entity the following properties are defined: assessment date, assessment result .

Property name and URI	Range	Card.	Definition	Usage note	Reuse
+assessment date `dct:issued`	`rdfs:Literal`	0..1	The date of the latest assessment procedure.		A
+assessment result `oa:hasBody`	`rdfs:Resource`	0..1	The result of the latest assessment procedure, in form of a URL linking to further details or results. Alternatively, textual information is provided using the Embedded Textual Body construction of the Web Annotation Data Model, which allows to specify text formats and languages which might be relevant for multilingual purposes.		A

Property name and URI

Range

Card.

Definition

Usage note

Reuse

+assessment date

dct:issued

rdfs:Literal

0..1

The date of the latest assessment procedure.

+assessment result

oa:hasBody

rdfs:Resource

0..1

The result of the latest assessment procedure, in form of a URL linking to further details or results. Alternatively, textual information is provided using the Embedded Textual Body construction of the Web Annotation Data Model, which allows to specify text formats and languages which might be relevant for multilingual purposes.

Definition	A concrete mobility data portal, i.e, a web portal, where mobility-related datasets and their distributions are described via metadata and discoverable for data users.
URI	`dcat:Catalog`
References	DCAT: Link DCAT-AP: Link geoDCAT-AP: Link
Usage note
Properties	For this entity the following properties are defined: dataset, description, geographical coverage, has part, homepage, identifier, language, licence, modification date, other identifier, publisher, crecord, release date, themes, title .

Property name and URI	Range	Card.	Definition	Usage note	Reuse
dataset `dcat:dataset`	`dcat:Dataset`	0..*	Links the mobility data portal with a dataset that is described at the mobility data portal.	This is a direct link from the mobility data portal to a dataset. However, in mobilityDCAT-AP, datasets should be linked indirectly, i.e., via the metadata record of this dataset. Thus, it is mandatory to use the property `dcat:record` to link to a data set. The usage of `dcat:dataset` may be then redundant.	E
description `dct:description`	`rdfs:Literal`	1..*	A free-text account of the Catalogue.	This property can be repeated for parallel language versions of the description - see 12. Accessibility and Multilingual Aspects.	E
geographical coverage `dct:spatial`	`dct:Location`	1..*	A geographical area covered by the Catalogue.	For National Access Points (NAPs), this corresponds to the EU Member State or a country that installs such NAP. The property might be used for analyses about available datasets per country, or to identify country-specific metadata in case metadata are federated from multiple national portals into an international portal. It is not to be mixed up with country codes used within the dataset property `dct:spatial`, which might be different. The obligation of this property is raised to “mandatory”, comparing to DCAT-AP v3.0.0.	E
has part `dct:hasPart`	`dcat:Catalog`	0..*	A related Catalogue that is part of the described Catalogue.	This property could be used to link the mobility data portal to another data portal, by e.g. harvesting metadata from this other portal into the mobility data portal.	E
homepage `foaf:homepage`	`foaf:Document`	1..1	A web page that acts as the main page for the Catalogue.	This property could be used to link the mobility data portal to another data portal, by e.g. harvesting metadata from this other portal into the mobility data portal. The obligation of this property is raised to “mandatory”, comparing to DCAT-AP v3.0.0.	E
+identifier `dct:identifier`	`rdfs:Literal`	0..*	The main identifier for the mobility data portal, e.g. the URI or other unique identifier. Allows a unique identification of the individual portal and is used for referencing, e.g., when exchanging metadata between mobility data portals.	This property should populated by the URI used within the RDF statement (via `rdf:about`). This property is analogue to an addition by geoDCAT-AP v3.0.0.	GE
language `dct:language`	`dct:LinguisticSystem`	0..*	Language used in the user interface of the mobility data portal, in particular the textual metadata describing the datasets registered in the portal.	This property can be repeated if the user interface and textual metadata are provided in multiple languages - see 12. Accessibility and Multilingual Aspects.	E
licence `dct:license`	`dct:LicenseDocument`	0..1	A licence under which the Catalogue can be used or reused.		A
modification date `dct:modified`	`rdfs:Literal`	0..1	The most recent date on which the Catalogue was modified. It is recommended to indicate modifications of the portal system as such (e.g., major technical updates of the portal or its features), rather than modifications of the hosted datasets, since datasets on mobility data portals are updaded frequently.		E
+other identifier `adms:identifier`	`adms:Identifier`	0..1	This property may be used as an additional identifier, besides `dct:identifier`.	This property may be referring to a dedicated, EU-wide identificator system of NAPs or other portals, to be introduced in the future. This property is an addition by mobilityDCAT-AP.	A
publisher `dct:publisher`	`foaf:Agent`	1..1	An entity (organisation) responsible for making the Catalogue available. This organisation is the direct contact for platform users, who have questions or issues about the platform and its system.	This information should correspond to the information in the disclaimer of the platform website.	E
record `dcat:record`	`dcat:CatalogRecord`	1..n	A metadata record that is part of the mobility data portal.	mobilityDCAT-AP assumes that metadata records are essential in mobility data portals, so the obligation of this property is raised to “mandatory”, comparing to DCAT-AP v3.0.0.	E
release date `dct:issued`	`rdfs:Literal`	0..1	The date of formal issuance (e.g., publication) of the mobility data portal.		E
themes `dcat:themeTaxonomy`	`skos:ConceptScheme`	0..*	A knowledge organization system used to classify the mobility data portal's datasets.	Recommended to indicate the version of the controlled vocabulary for property `mobilitydcatap:mobilityTheme`, that is used in the mobility data portal.	E
title `dct:title`	`rdfs:Literal`	1..*	A name given to the mobility data portal.	This property can be repeated for parallel language versions of the name - see 12. Accessibility and Multilingual Aspects.	E

Definition	A description of a metadata entry in the mobility data portal, referring to one dataset and its distributions published on the portal.
URI	`dcat:CatalogRecord`
References	DCAT: Link DCAT-AP: Link geoDCAT-AP: Link
Usage note	mobilityDCAT-AP assumes that metadata records are essential in mobility data portals, so the obligation of this class is raised to “mandatory”, comparing to DCAT-AP-v3.0.0.
Properties	For this entity the following properties are defined: language, listing date, modification date, primary topic, publisher, source metadata .

Property name and URI	Range	Card.	Definition	Usage note	Reuse
language `dct:language`	`dct:LinguisticSystem`	1..*	The language used in the textual metadata describing titles, descriptions, etc. of the metadata entry.	The value may be generated automatically by the NAP system, corresponding to the currently used language in the user interface. Some portals offer multilingual user interfaces, e.g., in the local language and additionally in English. For multiple languages - see 12. Accessibility and Multilingual Aspects. The obligation of this property is raised to “mandatory”, comparing to DCAT-AP v3.0.0.	E
+listing date `dct:issued`	`rdfs:Literal`	1..1	The date on which the metadata entry was included in the Catalogue.	It should be generated by the system, whenever a platform user enters the metadata entry.	E
modification date `dct:modified`	`rdfs:Literal`	1..1	The most recent date on which the metadata entry was changed or modified.	It should be generated by the system, whenever a platform user updates the metadata entry. If there has been no update yet, the value from the property `dct:created` should be taken.	E
primary topic `foaf:primaryTopic`	`rdfs:Literal`	1..1	Links the metadata entry to the dataset described in the entry.		E
+publisher `dct:publisher`	`foaf:Agent`	0..1	An entity (an organisation or a person), which is responsible for creation and maintenance of the metadata entry on the data platform. This entity is the direct contact for the data platform operators or data-searching users, who have questions or issues about the metadata entry.	This information can be natively created by a data platform, corresponding to the entity that is registered to the data platform and has the role of a metadata creator. This information can be also harvested from other portals. The information might be identical to the property `dct:publisher` of the corresponding dataset. This property is analogue to an addition by GEODCAT-AP-v3.0.0.	GE
source metadata `dct:source`	`dcat:CatalogRecord`	0..1	The original metadata record that was used in creating the metadata record.	Used for metadata records that are harvested from other portals. Harvesting, i.e., the automated import of metadata information from external portals, seems to be a common case for some NAPs. With these property, a data user can see, if the metadata was harvested, and from where. The property should link to a public URL of the dataset descripton on the original data portal, from where the metadata was harvested.	E

Definition	A dataset is a collection of data, published or curated by a single source, and available for access or download at the mobility data portal in one or more distributions. In the context of mobility-related data exchange, this might be, e.g., a data collection about static parking information for truck drivers, published by a road authority.
URI	`dcat:Dataset`
References	DCAT: Link DCAT-AP: Link geoDCAT-AP: Link
Usage note
Properties	For this entity the following properties are defined: applicable legislation, assessment result, geographical-coverage, contact point, dataset distribution, description, documentation, frequency, geographical coverage, georeferencing method, has version, identifier, in series, intended information service, is referenced by, keyword, language, mobility theme, modification date, network coverage, other identifier, publisher, quality description, reference system, related resource, release date, rights holder, source, temporal coverage, theme, title, transport mode, version, version notes, title .

Property name and URI	Range	Card.	Definition	Usage note	Reuse
applicable legislation `dcatap:applicableLegislation`	`eli:LegalResource`	0..*	A legal framework being relevant for the dataset, e.g., an EC Delegated Regulation which stipulates the provisioning of the corresponding dataset, or some other international or national frameworks, e.g., Open Data regulations.		E
+assessment result `mobilitydcatap:assessmentResult`	`mobilitydcatap:Assessment`	0..1	The results and outcomes from an assessment process by an external organisation, e.g., a National Body in the context of EU Delegated Regulations. EU Delegated Regulations require Member States to set up procedures to assess the compliance of the Delegated Regulations, e.g. regarding the provisioning of data via a NAP. These assessment processes are handled by National Bodies and installed individually in each Member State. The property may point to the most recent assessment procedure, including its date, its result as a free-text and/or a link referring to an assessment report online.	The difference to the property `dqv:hasQualityAnnotation` is that the latter one is provided by the data provider, while the assessment results are provided by an external organisation.	A
contact point `dcat:contactPoint`	`vcard:Kind`	0..*	Contact information that can be used for communication with a company or person responsible for the dataset. Used for questions or issues about a dataset and its provisioning, as raised by a platform user or a platform operator.	When providing contact information, data publishers SHOULD prioritize organizational information over personal details. The exposure of personal information, such as a personal name and email address, may be restricted to the public. Instead, there might be an anonymous contact channel, e.g. a contact button on the GUI that triggers an email to the contact point. See 13. Privacy and security considerations. The contact point might be populated with the same information as for property `dct:publisher`. See 11. Agent Types, Agent Roles and Contact Information for further usage notes on that matter.	E
dataset distribution `dcat:distribution`	`dcat:Distribution`	1..*	An available Distribution for the Dataset.	In mobilityDCAT-AP, it is mandatory that each dataset has at least one distribution. Thus, the obligation of this property is raised to “mandatory”, compared to DCAT-AP v3.0.0.	E
description `dct:description`	`rdfs:Literal`	1..*	Information about the dataset as a free-text description. It is used only for a brief overview, because free-text fields are unsuitable for searches, due to spelling mistakes, different wordings and other aspects. The categorisation and other aspects about the dataset are described within other properties of the dataset.	This property can be repeated for parallel language versions of the description - see 12. Accessibility and Multilingual Aspects. The language version should correspond to property `dct:language` of class Catalogue Record. I.e., if more than one language is provided as a metadata language, there should be as many language versions for the description.	E
documentation `foaf:page`	`foaf:Document`	0..*	A page or document about this dataset.	This property is meant to link to other ressources which document the dataset, e.g., PDF manuals, other websites or similar. In contrast, the property `dct:description` is meant to provide a textual documentation. Please note there is also the same property `foaf:page` on the distribution level. Depending if the documentation is data set- or distribution-dependent, the property should be used on the data set or distribution level.	A
frequency `dct:accrualPeriodicity`	`dct:Frequency`	1..1	Describes how often the delivered content is updated. This information tells a data consumer, how often it is updated on the on the data platform, so the data consumer might align the frequency of data retrieval accordingly.	For dynamic data feeds, the frequency should correspond to the technical upload / data push frequency. For static datasets, it should correspond to the expected change frequency (see property `dct:modified`). The frequency might be a specific time interval, or a general remark such as “updated on occurrence”. A controlled vocabulary is provided. The obligation of this property is raised to “mandatory”, compared to DCAT-AP v3.0.0.	E
geographical coverage `dct:spatial`	`dct:Location`	1..n	A geographic region that is covered by the delivered content.	The obligation of this property is raised to “mandatory”, compared to DCAT-AP v3.0.0.	E
+georeferencing method `mobilitydcatap:georeferencingMethod`	`skos:Concept`	0..n	The georeferencing method used in the delivered content.	A corresponding controlled vocabulary is provided, denoting commonly used georeferencing methods for mobility data.	A
has version `dcat:hasVersion`	`dcat:Dataset`	0..n	A related dataset that is a version, edition, or adaptation of the described dataset	It might be used to host multiple versions of the same dataset in the data portal, also enabling a version history. Multiple versions should be differentiated via the properties `dcat:version` and `adms:versionNotes`.	E
identifier `dct:identifier`	`rdfs:Literal`	0..1	The main identifier for the dataset, e.g. the URI or other unique identifier. Allows a unique identification of the individual dataset and is used for referencing, e.g., when exchanging metadata between mobility data portals.	This property should populated by the URI used within the RDF statement (via `rdf:about`).	E
in series `dcat:inSeries`	`dcat:DatasetSeries`	0..*	A dataset series of which the dataset is part.		A
+intended information service `mmobilitydcatap:intendedInformationService`	`skos:Concept`	0..n	A type of information service, which the data content is intended to support. Such services may be, e.g., information services for multimodal mobility, as specified by EC Delegated Regulation 2024/490. Examples of such services include “location search”, which is based on a datasets with address identifiers, or “trip plan computation”, which is based on datasets on timetables.	A corresponding controlled vocabulary is provided.	A
is referenced by `dct:isReferencedBy`	`rdfs:Resource`	0..*	A related resource, such as a publication, that references, cites, or otherwise points to the dataset.	It may be a link between two individual datasets that complement each other, e.g. one dataset with static parking data, and one with dynamic parking data, both covering the same parking facilities.	E
keyword `dcat:keyword`	`rdfs:Literal`	0..*	A keyword or tag describing the Dataset.	For the purposes of mobility data portals, it is not recommended to use keywords, as they might be ambiguous, language-dependend and make data search difficult. Instead, usage of mobility-related properties with Controlled Vocabularies is recommended, in particular `mobilitydcatap:mobilityTheme`, `mobilitydcatap:networkCoveragemobilitydcatap:transportMode` If there are relevant keywords that are not part of such Controlled Vocabularies, please contact the authors of mobilityDCAT-AP, in order to update the Controlled Vocabularies.	E
language `dct:language`	`dct:LinguisticSystem`	0..*	The language of the content data in a dataset, if this content has a natural language embedded, such as text fields, addresses etc.	This property can be repeated if there are multiple languages in the dataset - see 12. Accessibility and Multilingual Aspects	E
+mobility theme `mobilitydcatap:mobilityTheme`	`skos:Concept`	1..n	This property refers to the mobility-related theme (i.e., a specific subject, category, or type) of the delivered content. A dataset may be associated with multiple themes. A theme is important for data seekers who are interested in a particular type of data content. The theme is described via a controlled vocabulary in two hierarchy levels: The 1st level is a mandatory field labelled "Data content category", describing the classification of the data content on an aggregated level. The 2nd level is an optional field labelled “Data content sub category”, detailing the "Data content category" via one or several sub-categories. When entering the metadata for one dataset, the data provider would first select one or several options of a "Data content category", and then optionally details this with one or more options of corresponding “Data content sub category”. The platform must be able to handle the dependencies between these two levels, i.e., match the allowed options between the 1st and 2nd level.	A corresponding controlled vocabulary is provided. This property is a sub-property of `dcat:theme`, being a further property of Dataset. To distinguish these two theme properties, it is recommended to label `mobilitydcatap:mobilityTheme` as "Mobility Theme", and `dcat:theme` as "EU Open Data Theme". The subject of a dataset may also be described via property `dcat:keyword`. However, the usage of "mobility theme" is preferred, to avoid ambiguity and uncontrolled theme descriptions.	A
modification date `dct:modified`	`rdfs:Literal`	0..1	The most recent date on which the content of the dataset was changed or modified.	This is redundant for high-frequency data feeds (e.g., DATEX II feeds), where the change date can be derived from the time stamp within the data feed.	E
+network coverage `mobilitydcatap:networkCoverage`	`skos:Concept`	0..n	This property describes the part of the transport network that is covered by the delivered content. For road traffic, the property should refer to the network classification for which the data is provided. As a minimum, an international or higher-level classification, e.g., via functional road classes, is recommended to allow data search across different countries. In addition, national classifications are allowed. For other transport modes, the property is meant to refer to the physical infrastructure which is used by the services covered by the data. For all modes, the property should also indicate if the data content relates to the EU’s trans-European transport network.	A corresponding controlled vocabulary is provided, denoting commonly used road and infrastructure network classes.	A
other identifier `adms:identifier`	`adms:Identifier`	0..*	This property may be used as an additional identifier, besides `dct:identifier`.	This property may be referring to a dedicated, EU-wide identificator system of NAP datasets, to be introduced in the future, or other identificator systems such as DataCite, DOI, or W3ID.	E
publisher `dct:publisher`	`foaf:Agent`	1..1	An entity (company and person) that publishes the dataset. This entity is responsible for the provisioning of a dataset. The entity also concludes a contract, if applicable.	This information can be natively created by a data platform, then corresponding to the entity that is registered to the data platform and has the role of a data publisher. The information might be identical to the property `dct:publisher` of class Catalogue Record and/or `dct:rightsHolder` of class Dataset. To establish a contact with a company or person responsible for the dataset, the property `dcat:contactPoint` should be used. However, the publisher and the contact point might be populated with the same information. See 11. Agent Types, Agent Roles and Contact Information for further usage notes on that matter. The obligation of this property is raised to “mandatory”, comparing to DCAT-AP v3.0.0.	E
+quality description `dqv:hasQualityAnnotation`	`dqv:QualityAnnotation`	0..n	Any quality aspects regarding the delivered content, in particular methods, metrics/indicators and results of a quality assessment. This information should assist data consumers in determining the value of data, before actually accessing and processing it. Thus, the information should be publicly available. Furthermore, it can be helpful for validation processes by 3rd parties, e.g., a National Body in context of EU Delegated Regulations.	Quality aspects should be noted via a free text and/or via URLs linking to further quality information. If there is absolutely no quality information, at least a note “quality information is unknown” should be given. If existing quality frameworks have been applied in the quality assessment, e.g., the Quality Frameworks from the NAPCORE project, these frameworks should be referenced.	A
+reference system `geodcatap:referenceSystem`	`skos:Concept`	0..n	The spatial reference system used in the delivered content. To be specified via the “EPSG coordinate reference systems” register operated by OGC.	A corresponding controlled vocabulary is provided. This is a sub-property of `dct:conformsTo`. This property is analogue to an addition by geoDCAT-AP v3.0.0.	GA
related resource `dct:relation`	`rdfs:Resource`	0..*	A reference, citation, or otherwise pointing to another, related resource, such as another dataset.	It may be a link between two individual datasets that complement each other, e.g. one dataset with static parking data, and one with dynamic parking data, both covering the same parking facilities.	E
release date `dct:issued`	`rdfs:Literal`	0..1	The date of formal issuance (e.g., publication) of the dataset.	There might a difference to the creation date of the metadata entry, see the property `dct:created` of Class Catalogue Record. Imagine the dataset is published outside the mobility data portal first, and afterwards published as a metadata entry on the portal, leading to two different dates. However, both dates can also be the same.	E
+rights holder `dct:rightsHolder`	`foaf:Agent`	0..n	An entity that legally owns or holds the rights of the data provided in a dataset. This entity is legally responsible for the content of the data and (if applicable) for the relevance to legal frameworks (see property `dcatap:applicableLegislation`.	The rights holder will be in many cases identical with the publisher of the dataset (see property `dct:publisher`) and/or of the catalogue record (see property `dct:publisher`). In such case, the rights holder data may be copied from the corresponding publisher entries. There might be also cases with non-identical entities: e.g., when one or several rights holders contract a third-party publisher (e.g., an IT service company), which is producing, hosting and publishing a dataset. This property is analogue to an addition by geoDCAT-AP v3.0.0.	GE
source `dct:source`	`dcat:Dataset`	0..*	A related Dataset from which the described Dataset is derived.	There is the same property `dct:source` on the Catalogue Record level. The source of a dataset relates to the content data, whereas the source of a catalogue record relates to the metadata.	E
temporal coverage `dct:temporal`	`dct:PeriodOfTime`	0..n	A temporal period, i.e., the beginning and the end, of the time reference of the delivered content (e.g., validity time of a public-transport time table).		E
theme `dcat:theme`	`skos:Concept`	0..*	The generic theme (i.e., a specific subject, category, or type) of the content of the dataset.	A controlled vocabulary is provided.	E
title `dct:title`	`rdfs:Literal`	1..*	The name given to the dataset in a generic term. The name should be a meaningful, unique and unambiguous label.	This property can be repeated for parallel language versions of the title - see 12. Accessibility and Multilingual Aspects. The language version should correspond to property `dct:language` of class Catalogue Record. I.e., if more than one language is provided as a metadata language, there should be as many language versions for the title.	E
+transport mode `mobilitydcatap:transportMode`	`skos:Concept`	0..n	The transport mode that is covered by the delivered content.	A corresponding controlled vocabulary is provided, denoting commonly used transport modes.	A
version `dcat:version`	`rdfs:Literal`	0..1	The version indicator (name or identifier) of a dataset.	The version number should be updated, whenever there are changes to the dataset noted by the property `dct:modified`. Together with property `adms:versionNotes`, this may also enable a change history (or version history) of the corresponding dataset, which could be hosted and published on the data platform. The property URI has been replaced from `owl:versionInfo`, comparing to DCAT-AP-v2.0.1 and mobilityDCAT-AP-v-1.0.1.	E
version notes `adms:versionNotes`	`rdfs:Literal`	0..*	A textual description of the differences between this version and a previous version of the dataset.	This property should be an addition to the property `dcat:version.` `This property can be repeated for parallel language versions of the version notes - see 12. Accessibility and Multilingual Aspects.`	E

Definition	A collection of datasets that are published separately, but share some characteristics that group them.
URI	`dcat:DatasetSeries`
References	DCAT: Link DCAT-AP: Link geoDCAT-AP: Link
Usage note	It is recommended to avoid Dataset Series without a dataset in the collection. Therefore at least one Dataset should refer to a Dataset Series using the property in series (`dcat:inSeries`). Further instructions on the usage of Dataset Series are given in the mobilityDCAT-AP Wikisection on Dataset Series, the DCAT-AP Usage Guide on Dataset Series, and the DCAT-AP Examples for Dataset Series
Properties	For this entity the following properties are defined: applicable legislation, contact point, description, frequency, geographical coverage, modification date, publisher, release date, temporal coverage, title .

vered content See also the example no. 11 in the Dataset Series examples section of DCAT-AP v3.0.0.

Property name and URI	Range	Card.	Definition	Usage note	Reuse
applicable legislation `dcatap:applicableLegislation`	`eli:LegalResource`	0..*	A legal framework being relevant for the dataset series.		E
contact point `dcat:contactPoint`	`vcard:Kind`	0..*	Contact information that can be used for communication with a company or person responsible for the dataset series. Used for questions or issues about a dataset series and its provisioning, as raised by a platform user or a platform operator.	When providing contact information, data publishers SHOULD prioritize organizational information over personal details. The exposure of personal information, such as a personal name and email address, may be restricted to the public. Instead, there might be an anonymous contact channel, e.g. a contact button on the GUI that triggers an email to the contact point. See 13. Privacy and security considerations.	E
description `dct:description`	`rdfs:Literal`	1..*	Information about the dataset series as a free-text description.	It is recommended to provide an indication about the dimensions the Dataset Series evolves, e.g., if the dataset seriesevolves according to the time, geolocation or other dimensions. This property can be repeated for parallel language versions of the description - see 12. Accessibility and Multilingual Aspects. The language version should correspond to property `dct:language` of class Catalogue Record. I.e., if more than one language is provided as a metadata language, there should be as many language versions for the description.	E
frequency `dct:accrualPeriodicity`	`dct:Frequency`	0..1	Describes how often the dataset series is updated.	The frequency of a dataset series is understood differently to the frequency of the dataset in the collection, as declared via property `dct:accrualPeriodicity`. See the examples no. 5 and 6 in the Dataset Series examples section of DCAT-AP v3.0.0.	A
geographical coverage `dct:spatial`	`dct:Location`	0..*	A geographic region that is covered by the dataset series.	When spatial coverage is a dimension in the dataset series then the spatial coverage of each dataset in the collection should be part of the spatial coverage of the dataset series. In that case, the value of the spatial coverage of the dataset series should be as wide as possiblie. E.g., if datasets in a collection are about different regions in a country, the spatial coverage of the dataset series should note the entire country. See also the examples no. 7 and 8 in the Dataset Series examples section of DCAT-AP v3.0.0.	E
+mobility theme `mobilitydcatap:mobilityTheme`	`skos:Concept`	0..n	This property refers to the mobility-related theme (i.e., a specific subject, category, or type) of the dataset series. A theme is important for data seekers who are interested in a particular type of data content. It is recommended that the theme does not change among datasets in the collection, i.e., the theme of the dataset series should be equal to the theme of each dataset in the collection.	A corresponding controlled vocabulary is provided.	P
modification date `dct:modified`	`rdfs:Literal`	0..1	The most recent date on which the dataset series was changed or modified.	This should correspond to the most recent modification date of all datasets in the collection, as declared via property `dct:modified`.	E
publisher `dct:publisher`	`foaf:Agent`	1..1	An entity (company and person) that publishes the dataset series. This entity is also responsible for ensuring the coherency of the dataset series.	The publisher of the dataset series may or may be not the publisher of all datasets, as declared via property `dct:publisher`. E.g. a digital archive could take over the publishing of older datasets in the series. The obligation of this property is raised to “mandatory”, comparing to DCAT-AP v3.0.0.	E
release date `dct:issued`	`rdfs:Literal`	0..1	The date of formal issuance (e.g., publication) of the dataset series.	The moment when the dataset series was established as a managed resource. This might correspond to the earliest release date of the dataset in the collection, as declared via property `dct:issued`. See also the examples no. 9 and 10 in the Dataset Series examples section of DCAT-AP v3.0.0.	E
temporal coverage `dct:temporal`	`dct:PeriodOfTime`	0..n	A temporal period, i.e., the beginning and the end, of the time reference that the Dataset Series covers.	When temporal coverage is a dimension in the dataset series then the temporal coverage of each dataset in the collection should be part of the temporal coverage. In that case, an open ended value is recommended, e.g. "after 2012".	E
title `dct:title`	`rdfs:Literal`	1..*	The name given to the dataset series in a generic term. The name should be a meaningful, unique and unambiguous label.	This property can be repeated for parallel language versions of the title - see 12. Accessibility and Multilingual Aspects.	E

Definition	A distribution describes the data formats and communication methods for a dataset. There may be one or multiple distributions for one dataset. For example, the same dataset (e.g. static parking information for truck drivers) can be provided in different ways e.g. as downloadable zip file or as XML using a REST web service. These are two distributions based on one dataset.
URI	`dcat:Distribution`
References	DCAT: Link DCAT-AP: Link geoDCAT-AP: Link
Usage note	For the context of mobility data portals, it can be expected that all datasets have one or more distributions. Thus, there must be at least one instance of class Distribution related to one dataset. This is in contrast to DCAT-AP v3.0.0, which allows for datasets without distributions.
Properties	For this entity the following properties are defined: access url, application layer protocol, applicable legislation, character encoding, communication method, data format notes, description, documentation, download url, format, language, licence, linked schemas, mobility data standard, modification date, release date, rights, sample, status, temporal coverage, title.

Property name and URI	Range	Card.	Definition	Usage note	Reuse
access url `dcat:accessURL`	`rdfs:Resource`	1..1	A URL that gives access to a distribution of the dataset.	Depending on the type of data provision, there are different options for describing the URL. For data services, e.g., API, broker services, data feeds, etc., the URL may be the end point of such service. If some agreements between the data provider and the data user need to be established first, the access URL may link to web page, where the access is further arranged, e.g., initiating a a subscription process. For data which can be downloaded directly, the download URL should be copied from the property `dcat:downloadURL`. For other cases, where data cannot be directly accessed or downloaded via the platform, the access URL may be a link to an external service or a website which enables access to the data.	E
+application layer protocol `mobilitydcatap:applicationLayerProtocol`	`skos:Concept`	0..1	The transmitting channel, i.e., the Application Layer Protocol, of the distribution.	A corresponding controlled vocabulary is provided.	P
applicable legislation `dcatap:applicableLegislation`	`eli:LegalResource`	0..*	A legal framework being relevant for the distribution.	The legal framework is usually provided on the dataset level, see property `dcatap:applicableLegislation`. However, there is a special case of if a High Value Dataset (HVD) is provided on a portal. Here, the DCAT-AP profile for HVD stipulates that this property links to the EC regulation 2013/138 on HVD both on the dataset and distribution levels. In other words, a RDF statement is required under the dataset and distribution class, if a HVD is published on the portal. For other cases outside HVD, the use of this property is not recommended.	E
+character encoding `cnt:characterEncoding`	`rdfs:Literal`	0..1	The technical encoding format of the delivered content within the distribution.	It SHOULD be expressed using a character set name defined in the IANA character sets register. This property is analogue to an addition by geoDCAT-AP v3.0.0.	GE
+communication method `mobilitydcatap:communicationMethod`	`skos:Concept`	0..1	Indicates for dynamically provided distributions, e.g., data feeds, if the data interface of the data provider system functions in a push or pull mode.	A corresponding controlled vocabulary is provided.	P
+data format notes `mobilitydcatap:dataFormatNotes`	`rdfs:Literal`	0..*	Any additional information about the format of the delivered content within the distribution in a textual format.	This property can be repeated for parallel language versions of the data format notes - see 12. Accessibility and Multilingual Aspects.	P
description `dct:description`	`rdfs:Literal`	0..*	A free-text account of the Distribution.	This property can be repeated for parallel language versions of the description - see 12. Accessibility and Multilingual Aspects.	E
documentation `foaf:page`	`foaf:Document`	0..*	A page or document about the distribution.	This property is meant to link to other ressources which document the data distribution, e.g., PDF manuals, other websites or similar. In contrast, the property `dct:description` is meant to provide a textual documentation. Please note there is also the same property `foaf:page` on the dataset level. Depending if the documentation is data set- or distribution-dependent, the property should be used on the data set or distribution level.	A
download url `dcat:downloadURL`	`rdfs:Resource`	0..1	A URL that is a direct link to a downloadable file in a given format.		A
format `dct:format`	`dct:MediaTypeOrExtent`	1..1	The technical syntax of the delivered content within the distribution. It describes the base standard that specifies syntactically correct documents. On this level, base elements are properly specified on how to build a document. The resulting document can then be validated by syntax checks.	A controlled vocabulary is provided. The obligation of this property is raised to “mandatory”, compared to DCAT-AP v3.0.0. There is a similar property in DCAT-AP v3.0.0 called `dcat:mediaType`. This one is not used in mobilityDCAT-AP. The reason is the use of Controlled vocabularies: `dct:format` uses the EU Authority List about file types, whereas `dcat:mediaType` uses the IANA media types list. The first one, however, is sufficient to describe the syntaxes commonly used in mobility data portals.	E
language `dct:language`	`dct:LinguisticSystem`	0..*	The language of the content data in a distribution, if this content has a natural language embedded, such as text fields, addresses etc.	There is the same property `dct:language` under class Dataset. Language information on the distribution level is only recommended, if there are multiple distributions for the same dataset with a different language each. This property can be repeated if there are multiple languages in the distribution - see 12. Accessibility and Multilingual Aspects	E
licence `dct:license`	`dct:LicenseDocument`	0..1	The licence under which the distribution is made available. This should be a reference to a concrete (standard) licence.	A controlled vocabulary is provided.	E
linked schemas `dct:conformsTo`	`dct:Standard`	0..*	An established schema to which the described Distribution conforms.	To inform about a mobility data standard (and also related profiles) applied to the delivered data, property `mobilitydcatap:mobilityDataStandard` should be preferably used. In addition, property `dct:conformsTo` can be used to serve the needs of standard DCAT/DCAT‑AP open data portals. Such portals usually cannot process information exposed indirectly via property `mobilitydcatap:mobilityDataStandard`, i.e., they cannot dereference or validate such references. Thus, this property would expose the standards/profiles information directly at the Distribution.	E
+mobility data standard `mobilitydcatap:mobilityDataStandard`	`mobilitydcatap:MobilityDataStandard`	1..*	The mobility data standard, as applied for the delivered content within the distribution. A mobility data standard, e.g., DATEX II, combines syntax and semantic definitions of entities in a certain domain (e.g., for DATEX II: road traffic information), and optionally adds technical rules for data exchange. This is a sub-property of `dct:conformsTo`.	A corresponding controlled vocabulary is provided, listing common mobility data standards. At least one value from this controlled vocabulary is required. If no suitable standard is found in this vocabulary, the "other" entry should be used. Optionally, a new individual instance of class `mobilitydcatap:MobilityDataStandard` can be provided. This instance might be used to (a) reference a mobility data standard that is not listed in the controlled vocabulary; or (b) provide additional information on an applied mobility data standard (even if listed in the controlled vocabulary), such as version or schema details. See the Wiki page for a code example with a reference to a mobility data standard (listed in the controlled vocabulary), and detailed information via an individual instance of class `mobilitydcatap:MobilityDataStandard`.	P
modification date `dct:modified`	`rdfs:Literal`	0..1	The most recent date on which the Distribution was changed or modified.	There is the same property `dct:modified` under the Dataset level. Under the distribution level, this property describes temporal changes in the characteristics of a distribution, e.g., a new data format or similar.	E
release date `dct:issued`	`rdfs:Literal`	0..1	The date of formal issuance (e.g., publication) of the Distribution.	There is the same property `dct:issued` at the Dataset level. Under the distribution level, this property relates to the release time of a distribution, which might be different than the release time of a dataset.	E
rights `dct:rights`	`dct:RightsStatement`	1..1	A statement that specifies rights associated with the distribution. In particular, a statement about the intellectual property rights (IPR). As a minimum, it should include an information on the type of conditions for access and usage.	A concrete (standard) license can be referred via the recommended property `dct:license`. The obligation of this property is raised to “mandatory”, compared to DCAT-AP v3.0.0.	E
+sample `adms:sample`	`rdfs:Resource`	0..*	A sample of the delivered content, using the same conditions (e.g., the same format and licence) as the regular disctribution. A sample allows data users to investigate the data content and data structure, without subscribing to a data feed or downloading a complete data set.	In DCAT-AP v3.0.0, there is a property `adms:sample` under class Dataset, with class Distribution as the range. This implies that all mandatory properties for a distribution, e.g., the applied Mobility Data Standard, must be applied for a sample. To simplify the description of the sample, mobilityDCAT-AP recommends to describe the sample via a property under class Distribution, instead under class Dataset.	P
status `adms:status`	`skos:Concept`	0..1	The status of the distribution in the context of maturity lifecycle.	It must take one of the values Completed, Deprecated, Under Development, Withdrawn. A corresponding controlled vocabulary is provided.	A
+temporal coverage `dct:temporal`	`dct:PeriodOfTime`	0..1	The time interval when a distribution is facilitated (i.e., activated) technically via the data platform. Might be used if data access via a distribution is limited in time.	If there is no entry it means that the distribution has no explicit start time (i.e., it is facilitated immediately) and has no end time (i.e., it is facilitated infinitely).	P
title `dct:title`	`rdfs:Literal`	0..*	A name given to the distribution.	This property can be repeated for parallel language versions of the title - see 12. Accessibility and Multilingual Aspects.	E

Definition	A description following the VCARD-RDF specification, e.g., to provide telephone number and e-mail address for a contact point.
URI	`vcard:Kind`
References	DCAT: none DCAT-AP: Link geoDCAT-AP: Link
Usage note	This class is the parent class for the four explicit types of vCards (`vcard:Individual`, `vcard:Organization`, `vcard:Location`, `vcard:Group`). The contact point might be populated with the same information as for an agent, see class `foaf:Agent`. See 11. Agent Types, Agent Roles and Contact Information for further usage notes on that matter. When providing contact information, data publishers SHOULD prioritize organizational information over personal details. The exposure of personal information, such as a personal name and email address, may be restricted to the public. Instead, there might be an anonymous contact channel, e.g. a contact button on the GUI that triggers an email to the agent. See 13. Privacy and security considerations.
Properties	For this entity the following properties are defined: address, affiliation, email, name, phone, URL .

Property name and URI	Range	Card.	Definition	Usage note	Reuse
+address `vcard:hasAddress`	`vcard:Address`	0..1	The postal address of the kind, i.e., of an individual, an organization, a location or a group.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GA
+affiliation `vcard:organization-name`	`rdfs:Literal`	0..1	The affiliation of the kind, i.e., of an individual, an organization, a location or a group.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GA
+email `vcard:hasEmail`	`vcard:Email`	1..1	The email address of the kind (i.e., an individual, an organization, a location or a group), specified using fully qualified mailto: URI scheme RFC6068.	This property is analogue to an addition by geoDCAT-AP v3.0.0, however, with an raised obligation level.	GE
+name `vcard:fn`	`rdfs:Literal`	1..1	A name of the kind, i.e., a unique name of an individual, an organization, a location or a group.	This property is analogue to an addition by geoDCAT-AP v3.0.0, however, with an raised obligation level.	GE
+phone `vcard:hasTelephone`	`rdfs:Resource`	0..1	The phone number of the kind (i.e., an individual, an organization, a location or a group), specified using fully qualified tel: URI scheme RFC3966.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GA
+URL `vcard:hasURL`	`rdfs:Resource`	0..1	A web site of the kind., i.e., of an individual, an organization, a location or a group.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GA

Definition	A legal document, e.g., a concrete license, giving official permission to do something with a resource.
URI	`dct:LicenseDocument`
References	DCAT: none DCAT-AP: Link geoDCAT-AP: Link
Usage note	This property is used to reference an applicable (standard) licence via an IRI, so a data user can assess the license conditions in machine- and human-readable formats, before using the data. Via an instance of this class, a reference to a standard or a organisation-specific license can be given. For standard licenses, a Controlled Vocabulary is provided. See the Wiki page on Rights and Licenses for further guidance.
Properties	This specification does not impose any additional requirements to properties for this entity.

Definition	A spatial region or named place.
URI	`dct:Location`
References	DCAT: none DCAT-AP: Link geoDCAT-AP: Link
Usage note	It can be represented via a named place (controlled vocabulary) or with geographic coordinates, according to DCAT-AP guidelines. For mobility data portals, usage of a named place is preferred. Many mobility data providers represent public authorities such as states, regions, municipalities etc, which can be easily represented via named places. In contrast, defining of coordinates per dataset might be error-prone and inconsistent. As named spaces, identifiers should be used via property `dct:identifier`. These are coded via controlled vocabularies such as the EU authority tables, NUTS (Nomenclature des unités territoriales statistiques) or Geonames. Alternatively, geographic clear names may be used via property `skos:prefLabel`.
Properties	For this entity the following properties are defined: bounding box, centroid, gazetteer, geographic identifier, geographic name, geometry .

Property name and URI	Range	Card.	Definition	Usage note	Reuse
bounding box `dcat:bbox`	`rdfs:Literal`	0..1	The geographic bounding box of the location.		A
centroid `dcat:centroid`	`rdfs:Literal`	0..1	The geographic center (centroid) of the location.		A
+gazetteer `skos:inScheme`	`skos:ConceptScheme`	0..1	The gazetteer, i.e., a codelist to which the location belongs.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GA
+geographic identifier `dct:identifier`	`rdfs:Literal`	0..*	This property contains the geographic identifier for the location, e.g., the URI or other unique identifier in the context of the relevant gazetteer.	Corresponding controlled vocabularies are provided, denoting commonly used geographic identifiers. This property is analogue to an addition by geoDCAT-AP v3.0.0.	GA
+geographic name `skos:prefLabel`	`rdfs:Literal`	0..*	A preferred label of the location.	This property can be repeated for parallel language versions of the label - see 12. Accessibility and Multilingual Aspects. This property is analogue to an addition by geoDCAT-AP v3.0.0.	GA
geometry `locn:geometry`	`locn:Geometry`	0..1	The corresponding geometry for the location.		A

Error

Cannot GET /src/tables/class-mobility-data-standard

Property name and URI	Range	Card.	Definition	Usage note	Reuse
+specific content model `mobilitydcatap:specificContentModel`	`skos:Concept`	0..1	The specific content model of applied mobility data standard.	A corresponding controlled vocabulary is provided. Content models of mobility data standards can cover wide range of applications so the information about used standard is rather broad information. These standards already have more specific content models, which provide much more specific information about what content can be expected. In case of DATEX II there are content models like SituationPublication, ParkingTablePublication, ParkingStatusPublication etc.	P
+conforms to `dct:conformsTo`	`dct:Standard`	0..*	Reference to the applied mobility data standard, as well as to individual/national/content-specific profiles or representations of the applied standard.	This property is necessary if a custom instance of class `mobilitydcatap:MobilityDataStandard` is defined. This property would then reference a common mobility data standard (e.g., "NeTeX" via the controlled vocabulary), as well as additionally further individual/national/content-specific profiles or representations of the applied standard (e.g., an Italian NeTEx profile).	P
+title `dct:title`	`rdfs:Literal`	0..*	A name given to the mobility data standard.	This property can be repeated for parallel language versions of the title - see 12. Accessibility and Multilingual Aspects.	P
+version `dcat:version`	`rdfs:Literal`	0..1	The version of the mobility data standard, as applied within the delivered content. A version might be, e.g., DATEX II v3.2.	This information is provided in a textual format. To avoid ambiguity, only short version identifiers should be used, e.g., "3.2", without redundant acronyms such as "v", underscores etc.	P

Definition	An annotation about any quality aspects regarding the delivered content, in particular methods, metrics/indicators and results of a quality assessment in the responsibility of the Data Owner.
URI	`dqv:QualityAnnotation`
References	DCAT: none DCAT-AP: none geoDCAT-AP: none
Usage note	There is a similar class Quality Measurement" in geoDCAT-AP v3.0.0. Both "Quality Annotation" are "Quality Measurement" are reusing the Data Quality Vocabulary. "Quality Measurement is referring to concrete metrics, like sub-types of spatial resolutions being used in GeoDCAT-AP. At mobility data portals, however, the practice so far is to provide a more generic quality description, e.g., via a free-text report. Thus, the "Quality Annotation" refers to an unspecified form of quality annotation.
Properties	For this entity the following properties are defined: quality annotation resource, quality annotation target .

Property name and URI	Range	Card.	Definition	Usage note	Reuse
+quality annotation resource `oa:hasBody`	`rdfs:Literal`	0..1	Any quality aspects regarding the delivered content, in form of a URL linking to further details or results, or textual information.	Textual information should be provided using the Embedded Textual Body construction of the Web Annotation Data Model, which allows to specify text formats and languages which might be relevant for multilingual purposes.	A
+quality annotation target `oa:hasTarget`	`dcat:Dataset`	0..1	the target of the quality annotation, referring back to the dataset being described.	It is the inverse property of `dqv:hasQualityAnnotation` for class Dataset.	A

Property name and URI

Range

Card.

Definition

Usage note

Reuse

+quality annotation resource

oa:hasBody

rdfs:Literal

0..1

Any quality aspects regarding the delivered content, in form of a URL linking to further details or results, or textual information.

Textual information should be provided using the Embedded Textual Body construction of the Web Annotation Data Model, which allows to specify text formats and languages which might be relevant for multilingual purposes.

+quality annotation target

oa:hasTarget

dcat:Dataset

0..1

the target of the quality annotation, referring back to the dataset being described.

It is the inverse property of dqv:hasQualityAnnotation for class Dataset.

Definition	A postal address used for agent information.
URI	`locn:Address`
References	DCAT: none DCAT-AP: none geoDCAT-AP: Link
Usage note	See Address in the Core Location Vocabulary. This class is analogue to an addition by geoDCAT-AP v3.0.0.
Properties	For this entity the following properties are defined: administrative area, city, country, postal code, street address.

Property	URI	Range	Card.	Definition	Usage note	Reuse
+administrative area	`locn:adminUnitL2`	`rdfs:Literal`	0..1	The administrative area of an address. Depending on the country, this corresponds to a province, a county, a region, or a state.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GE
+city	`locn:postName`	`rdfs:Literal`	0..1	The name of the city of the address.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GE
+country	`locn:adminUnitL1`	`rdfs:Literal`	0..1	The country of an address.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GE
+postal code	`locn:postCode`	`rdfs:Literal`	0..1	The postal code of an address.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GE
+street address	`locn:thoroughfare`	`rdfs:Literal`	0..1	The street name and civic number of the address.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GE

Definition	A postal address used for contact point information.
URI	`vcard:Address`
References	DCAT: none DCAT-AP: none geoDCAT-AP: Link
Usage note	This class is analogue to an addition by geoDCAT-AP v3.0.0.
Properties	For this entity the following properties are defined: administrative area, city, country, postal code, street address.

Property	URI	Range	Card.	Definition	Usage note	Reuse
+administrative area	`vcard:region`	`rdfs:Literal`	0..1	The administrative area of an address. Depending on the country, this corresponds to a province, a county, a region, or a state.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GA
+city	`vcard:locality`	`rdfs:Literal`	0..1	The name of the city of the address.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GA
+country	`vcard:country-name`	`rdfs:Literal`	0..1	The country of an address.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GA
+postal code	`vcard:postal-code`	`rdfs:Literal`	0..1	The postal code of an address.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GA
+street address	`vcard:street-address`	`rdfs:Literal`	0..1	The street name and civic number of the address.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GA

Definition	An idea or notion; a unit of thought.
URI	`skos:Concept`
References	DCAT: none DCAT-AP: Link geoDCAT-AP: Link
Usage note	A Concept is used to denote codes within a codelist. In section 10. Controlled Vocabularies, the expectations are elaborated in more detail.
Properties	For this entity the following properties are defined: preferred label, concept scheme .

Property name and URI	Range	Card.	Definition	Usage note	Reuse
preferred label `skos:prefLabel`	`rdfs:Literal`	1..*	A preferred label of the concept.	This property can be repeated for parallel language versions of the label - see 12. Accessibility and Multilingual Aspects.	A
+concept scheme `skos:inScheme`	`skos:ConceptScheme`	0..1	Relates a concept to a concept scheme in which it is included.	This property is analogue to an addition by geoDCAT-AP v3.0.0.	GE

Property name and URI

Range

Card.

Definition

Usage note

Reuse

preferred label

skos:prefLabel

rdfs:Literal

1..*

A preferred label of the concept.

This property can be repeated for parallel language versions of the label - see 12. Accessibility and Multilingual Aspects.

+concept scheme

skos:inScheme

skos:ConceptScheme

0..1

Relates a concept to a concept scheme in which it is included.

This property is analogue to an addition by geoDCAT-AP v3.0.0.

Definition	An aggregation of one or more SKOS concepts, see class `skos:Concept`. Semantic relationships (links) between those concepts may also be viewed as part of a concept scheme.
URI	`skos:ConceptScheme`
References	DCAT: none DCAT-AP: Link geoDCAT-AP: Link
Usage note	A Concept Scheme is used to denote a codelist. In section 10. Controlled Vocabularies, the expectations are elaborated in more detail.
Properties	For this entity the following properties are defined: title .

Property name and URI	Range	Card.	Definition	Usage note	Reuse
title `dct:title`	`rdfs:Literal`	1..*	A name of the concept scheme.	This property can be repeated for parallel language versions of the name - see 12. Accessibility and Multilingual Aspects.	A

Property name and URI

Range

Card.

Definition

Usage note

Reuse

title

dct:title

rdfs:Literal

1..*

A name of the concept scheme.

This property can be repeated for parallel language versions of the name - see 12. Accessibility and Multilingual Aspects.

Definition	A textual resource intended for human consumption that contains information, e.g. a web page about a Dataset.
URI	`foaf:Document`
References	DCAT: none DCAT-AP: Link geoDCAT-AP: Link
Usage note	N/A
Properties	This specification does not impose any additional requirements to properties for this entity.

Definition	The electronic mail address for communication with the object.
URI	`vcard:Email`
References	DCAT: none DCAT-AP: none geoDCAT-AP: Link
Usage note	See Email in the VCard Ontology. This class is analogue to an addition by geoDCAT-AP v3.0.0.
Properties	This specification does not impose any additional requirements to properties for this entity.

Definition	A rate at which something recurs, e.g., the update rate of a dataset.
URI	`dct:Frequency`
References	DCAT: none DCAT-AP: Link geoDCAT-AP: Link
Usage note	none
Properties	This specification does not impose any additional requirements to properties for this entity.

Definition	The means to identify a location as a point, line, polygon, etc. expressed using coordinates in some coordinate reference system.
URI	`locn:Geometry`
References	DCAT: none DCAT-AP: Link geoDCAT-AP: Link
Usage note	none
Properties	This specification does not impose any additional requirements to properties for this entity.

Definition	This is based on the UN/CEFACT Identifier class.
URI	`adms:Identifier`
References	DCAT: none DCAT-AP: Link geoDCAT-AP: Link
Usage note	An identifier in a particular context, consisting of the content string that is the identifier; an optional identifier for the identifier scheme; an optional identifier for the version of the identifier scheme; an optional identifier for the agency that manages the identifier scheme.
Properties	For this entity the following properties are defined: notation .

Property name and URI	Range	Card.	Definition	Usage note	Reuse
notation `skos:notation`	`rdfs:Literal`	1..1	A string that is an identifier in the context of the identifier scheme referenced by its datatype.		A

Property name and URI

Range

Card.

Definition

Usage note

Reuse

notation

skos:notation

rdfs:Literal

1..1

A string that is an identifier in the context of the identifier scheme referenced by its datatype.

Definition	The legislation, policy or policies that lie behind the rules that govern the service.
URI	`eli:LegalResource`
References	DCAT: none DCAT-AP: Link geoDCAT-AP: Link
Usage note	The definition and properties of the Legal Resource class are aligned with the ontology included in "Council conclusions inviting the introduction of the European Legislation Identifier (ELI)". For describing the attributes of a Legal Resource (labels, preferred labels, alternative labels, definition, etc.) we refer to the ELI ontology. In this data specification the use is restricted to instances of this class that follow the ELI URI guidelines.
Properties	This specification does not impose any additional requirements to properties for this entity.

Definition	A system of signs, symbols, sounds, gestures, or rules used in communication, e.g. a language.
URI	`dct:LinguisticSystem`
References	DCAT: none DCAT-AP: Link geoDCAT-AP: Link
Usage note
Properties	This specification does not impose any additional requirements to properties for this entity.

Definition	A literal value such as a string or integer; Literals may be typed, e.g. as a date according to xsd:date. Literals that contain human-readable text have an optional language tag as defined by BCP 47 rfc5646.
URI	`rdfs:Literal`
References	DCAT: none DCAT-AP: Link geoDCAT-AP: Link
Usage note
Properties	This specification does not impose any additional requirements to properties for this entity.

Definition	A media type or extent.
URI	`dct:MediaTypeOrExtent`
References	DCAT: none DCAT-AP: Link geoDCAT-AP: Link
Usage note	In mobilityDCAT-AP, this class is only used as the range of property `dct:format` for class Distribution.
Properties	This specification does not impose any additional requirements to properties for this entity.

Definition	Represents a collection of people organized together into a community or other social, commercial or political structure. The group has some common purpose or reason for existence which goes beyond the set of people belonging to it and can act as an Agent. Organizations are often decomposable into hierarchical structures.
URI	`org:Organization`
References	DCAT: none DCAT-AP: none geoDCAT-AP: Link
Usage note	See Organization in The Organization Ontology. This class is analogue to an addition by geoDCAT-AP v3.0.0.
Properties	This specification does not impose any additional requirements to properties for this entity.

Definition	An interval of time that is named or defined by its start and end dates.
URI	`dct:PeriodOfTime/code>`
References	DCAT: none DCAT-AP: Link geoDCAT-AP: Link
Usage note	None
Properties	For this entity the following properties are defined: end date, start date .

Property name and URI	Range	Card.	Definition	Usage note	Reuse
end date `dcat:endDate`	`rdfs:Literal`	0..1	The end of the period.		A
start date `dcat:startDate`	`rdfs:Literal`	0..1	The start of the period		A

Property name and URI

Range

Card.

Definition

Usage note

Reuse

end date

dcat:endDate

rdfs:Literal

0..1

The end of the period.

start date

dcat:startDate

rdfs:Literal

0..1

The start of the period

Definition	Anything described by RDF.
URI	`rdfs:Resource`
References	DCAT: none DCAT-AP: Link geoDCAT-AP: Link
Usage note	none
Properties	This specification does not impose any additional requirements to properties for this entity.

Definition	A statement about the intellectual property rights (IPR) held in or over a resource, a legal document giving official permission to do something with a resource, or a statement about access rights.
URI	`dct:RightsStatement`
References	DCAT: none DCAT-AP: Link geoDCAT-AP: Link
Usage note	Reference to concrete (standard) licenses can be provided via another class `dct:LicenseDocument`. See the Wiki page on Rights and Licenses for further guidance.
Properties	For this entity the following properties are defined: conditions for access and usage, rights statement text .

Property name and URI	Range	Card.	Definition	Usage note	Reuse
+conditions for access and usage `dct:type`	`skos:Concept`	1..*	An indication of the conditions if any contracts, licences and/or are applied for the use of the distribution. The conditions are declared on an aggregated level: whether a free and unrestricted use is possible, a contract has to be concluded and/or a licence has to be agreed on to use a dataset.	A controlled vocabulary is provided. The values can be logically mapped with the property `dct:identifier` from class Licence Document, denoting a concrete standard license. For example, if the property `dct:identifier` is referring to standard licence "CC BY 4.0", the property `dct:type` can be given the value "Licence provided, free of charge".	P
+Rights statement text `dct:description`	`rdfs:Literal`	0..*	The text of the Rights Statement. I.e., any textual information about access, usage or licensing conditions, beyond information given via other properties under classes `dct:RightsStatement` and `dct:LicenseDocument`.	This property can be repeated for parallel language versions of the information - see 12. Accessibility and Multilingual Aspects. This property is analogue to an addition by geoDCAT-AP v3.0.0.	GE

Property name and URI

Range

Card.

Definition

Usage note

Reuse

+conditions for access and usage

dct:type

skos:Concept

1..*

An indication of the conditions if any contracts, licences and/or are applied for the use of the distribution. The conditions are declared on an aggregated level: whether a free and unrestricted use is possible, a contract has to be concluded and/or a licence has to be agreed on to use a dataset.

A controlled vocabulary is provided.

The values can be logically mapped with the property dct:identifier from class Licence Document, denoting a concrete standard license. For example, if the property dct:identifier is referring to standard licence "CC BY 4.0", the property dct:type can be given the value "Licence provided, free of charge".

+Rights statement text

dct:description

rdfs:Literal

0..*

The text of the Rights Statement. I.e., any textual information about access, usage or licensing conditions, beyond information given via other properties under classes dct:RightsStatement and dct:LicenseDocument.

This property can be repeated for parallel language versions of the information - see 12. Accessibility and Multilingual Aspects.

This property is analogue to an addition by geoDCAT-AP v3.0.0.

Definition	A standard or other specification to which a resource conforms.
URI	`dct:Standard`
References	DCAT: none DCAT-AP: Link geoDCAT-AP: Link
Usage note	To inform about a mobility data standard applied to the delivered data, mobilityDCAT-AP introduces a separate class `mobilitydcatap:MobilityDataStandard`. This class `mobilitydcatap:MobilityDataStandard` is a sub-class of `dct:Standard` and used as the range of property `mobilitydcatap:mobilityDataStandard` of class Distribution. In contrast, class `dct:Standard` can be applied to refer to (other or more precise) data standards/specifications/profiles at the Distribution and/or the Mobility Data Standard levels. In such case, this class is used as the range of property `dct:conformsTo` of class Distribution and/or of property `dct:conformsTo` of class Mobility Data Standard.
Properties	This specification does not impose any additional requirements to properties for this entity.

Class	Definition	URI	Reference DCAT-AP	Reference geoDCAT-AP
Temporal Literal	`rdfs:Literal` encoded using the relevant ISO8601 Date and Time compliant string and typed using the appropriate XML Schema datatype (`xsd:gYear`, `xsd:gYearMonth`, `xsd:date`, or `xsd:dateTime`).	`rdfs:Literal`	Link	Link

This section provides a condensed tabular overview of the mentioned classes and properties in mobilityDCAT-AP. The properties are grouped under headings mandatory, recommended, optional and deprecated. These terms have the following meaning.

Mandatory property: a receiver must be able to process the information for that property; a sender must provide the information for that property.
Recommended property: a receiver must be able to process the information for that property; a sender should provide information for that property if such information is available.
Optional property: a receiver must be able to process the information for that property; a sender may provide the information for that property but is not obliged to do so.
Deprecated property: a receiver should be able to process information about instances of that property; a sender should not provide the information about instances of that property.

Class	Mandatory prop.	Optional prop.
+`locn:Address`		+`locn:adminUnitL2` +`locn:postName` +`locn:adminUnitL1` +`locn:postCode` +`locn:thoroughfare`
`foaf:Agent`	`foaf:name`	+`locn:address` +`org:memberOf` +`foaf:mbox` +`foaf:firstName` +`foaf:phone` +`foaf:surname` `dct:type` +`foaf:workplaceHomepage`
+`mobilitydcatap:Assessment`		+`dct:issued` +`oa:hasBody`
`dcat:Catalog`	`dct:description` `dct:spatial` `foaf:homepage` `dct:publisher` `dcat:record` `dct:title`	`dcat:dataset` `dct:hasPart` +`dct:identifier` `dct:language` `dct:license` `dct:modified` +`adms:identifier` `dct:issued` `dcat:themeTaxonomy`
`dcat:CatalogRecord`	+`dct:created` `dct:language` `dct:modified` `foaf:primaryTopic`	+`dct:publisher` `dct:source`
`skos:Concept`	`skos:prefLabel`	+`skos:inScheme`
`skos:ConceptScheme`	`dct:title`
`dcat:Dataset`	`dcat:distribution` `dct:description` `dct:accrualPeriodicity` `dct:spatial` +`mobilitydcatap:mobilityTheme` `dct:publisher` `dct:title`	+`dcatap:applicableLegislation` +`mobilitydcatap:assessmentResult` `dcat:contactPoint` `foaf:page` +`mobilitydcatap:georeferencingMethod` `dct:hasVersion` `dct:identifier` `dcat:inSeries` +`mobilitydcatap:intendedInformationService` `dct:isReferencedBy` `dcat:keyword` `dct:language` `dct:modified` +`mobilitydcatap:networkCoverage` `adms:identifier` +`dqv:hasQualityAnnotation` +`geodcatap:referenceSystem` `dct:relation` `dct:issued` +`dct:rightsHolder` `dcat:theme` +`mobilitydcatap:transportMode` `dcat:version` `adms:versionNotes`
`dcat:Distribution`	`dcat:accessURL` +`mobilitydcatap:mobilityDataStandard` `dct:format` `dct:rights`	+`mobilitydcatap:applicationLayerProtocol` +`dcatap:applicableLegislation` +`cnt:characterEncoding` +`mobilitydcatap:communicationMethod` +`mobilitydcatap:dataFormatNotes` `dct:description` `foaf:page` `dcat:downloadURL` +`mobilitydcatap:grammar` `dct:license` +`adms:sample` `adms:status` +`dct:temporal` `dct:title`
`foaf:Document`
`dct:Frequency`
`adms:Identifier`	`skos:notation`
`vcard:Kind`	+`vcard:hasEmail` +`vcard:fn`	+`vcard:hasAddress` +`vcard:organization-name` +`vcard:hasTelephone` +`vcard:hasURL`
`dct:LicenseDocument`	+`dct:identifier`	+`rdfs:label`
`dct:LinguisticSystem`
`rdfs:Literal`
`dct:Location`		`dcat:bbox` `dcat:centroid` +`skos:inScheme` +`dct:identifier` +`skos:prefLabel` `locn:geometry`
+`mobilitydcatap:MobilityDataStandard`		+`mobilitydcatap:specificContentModel` +`dct:conformsTo` +`dcat:version` +`mobilitydcatap:schema`
`dct:PeriodOfTime`	`dcat:endDate` `dcat:startDate`
+`dqv:QualityAnnotation`		+`oa:hasBody` +`oa:hasTarget`
`rdfs:Resource`
`dct:RightsStatement`	+`dct:type`	+`dct:description`

The following properties from mobilityDCAT-AP v.1.1.0 have been deprecated.

Elements that are deprecated will continue to be accepted until an upcoming major release of mobilityDCAT-AP. However, it is not recommended to introduce them at new mobilityDCAT-AP deplyoments.

Class	Property name and URI	Range	Card.	Definition	Usage note	Reuse
Catalogue Record	+creation date `dct:created`	`rdfs:Literal`	1..1	The date stamp when the metadata entry was created for the first time.	It should be generated by the system, whenever a platform user enters the metadata entry. This property is analogue to an addition by GEODCAT-AP-v3.0.0.	GE
Distribution	+grammar `mobilitydcatap:grammar`	`skos:Concept`	0..1	The technical data grammar format of the delivered content within the Distribution. It describes the standard on top of the elementary syntax that describe data structures in the dataset.	A corresponding controlled vocabulary is provided. This is a sub-property of `dct:conformsTo`.	P
Licence Document	+standard licence `dct:identifier`	`skos:Concept`	0..1	A concrete standard license.	A controlled vocabulary is provided.	A
Licence Document	+licence text `rdfs:label`	`rdfs:Literal`	0..*	The full text of a licence document, as a free text. May be used when there is no standard license that can be linked via property `dct:identifier`.	This property can be repeated for parallel language versions of the licence text - see 12. Accessibility and Multilingual Aspects.	A
Mobility Data Standard	+schema `mobilitydcatap:schema`	`rdfs:Resource`	0..*	The schema of the mobility data standard, as applied within the delivered content. E.g., an XDS representation of a specific DATEX II profile.	This is a sub-property of `dct:conformsTo`. There are different options how to reference the schema. It might be a reference to a platform-hosted catalogue of schemas. In such case, the data platform should keep an own catalogue of commonly used schemas. The data provider should then be able to select an applicable schema from this catalogue when providing the metadata. It might be also a reference to an individual schema that is provided by the data publisher, or a reference to an schema that is hosted externally (like a stakeholder-based DATEX II profile published on the datex2.eu page). In such case, the data provider should be able to upload an own, individual schema, or to link to an external one. . In any case, the schema should be available as a resource.	P

mobilityDCAT-AP is reusing many of the DCAT-AP classes and properties. The selection of the used classes and properties is based on the mobilityDCAT-AP Conceptual Model, defining essential metadata elements for NAPs and mobility data portals, see the Documentation of the preparatory activities. Thus, mobilityDCAT-AP is leaving out many classes/properties from DCAT-AP model, also keeping the data model compact. The following tables show an overview of classes/properties that are not used from DCAT-AP, with addional notes on the reasoning and alternative approaches.

Class	URI	Reference DCAT-AP	Note
Catalogued Resource	`dcat:Resource`	Link	According to DCAT-AP-v3.0.0, this as an abstract class. Only subclasses should be used in a data exchange, such as `dcat:Dataset`. Thus, the Catalogued Resource is not listed expilicitely in mobilityDCAT-AP.
Checksum	`spdx:Checksum`	Link	In DCAT-AP-v3.0.0, this class is only used as the range for the optional property `spdx:checksum` of class Distribution. However, in mobilityDCAT-AP, this property is removed. So, the class is without function in mobilityDCAT-AP.
Data Service	`dcat:DataService`	Link	In DCAT-AP-v3.0.0, a Data Service is a collection of operations that provides access to one or more datasets or data processing functions. After discussions in mobility DCAT-AP and an analysis of potential use cases of this class in DCAT-AP-v3.0.0, it has been decided not to introduce Data Service for the following reasons. 1. Potential use as the range to property `dcat:accessService` of class Distribution. This property might describe additional information about an end point of one distribution. However, looking at today's set-ups of NAPs and mobility data portals, the characteristics and mechanisms of a distribution's end point are sufficiently described via property `dcat:accessURL` of class Distribution. 2. Potential use as the range to property `foaf:primaryTopic` of class Catalogue Record This implies a metadata entry about one Data Service. However, all analysed mobility data portals, including NAPs, store only metadata about datasets, and not about data services. Thus, such relationship is irrelevant for mobilityDCAT-AP as of today, but might be used in the future when such portals also explicitely list data services.
Relationship	`dcat:Relationship`	Link	In DCAT-AP-v3.0.0, this class is only used as the range of the optional property `dcat:qualifiedRelation` of class Dataset. In mobilityDCAT-AP, this property is removed. So, the class is without function in mobilityDCAT-AP.
Activity	`prov:Activity`	Link	In DCAT-AP-v3.0.0, this class is only used as the range of the optional property `prov:wasGeneratedBy` of class Dataset. In mobilityDCAT-AP, this property is removed. So, the class is without function in mobilityDCAT-AP.
Attribution	`prov:Attribution`	Link	In DCAT-AP-v3.0.0, this class is only used as the range of the optional property `prov:qualifiedAttribution` of class Dataset. In mobilityDCAT-AP, this property is removed. So, the class is without function in mobilityDCAT-AP.
Checksum Algorithm	`spdx:ChecksumAlgorithm`	Link	In DCAT-AP-v3.0.0, this class is only used as the range of the optional property `spdx:algorithm` of class Checksum. In mobilityDCAT-AP, the entire class Checksum is removed (see above). So, the class Checksum Algorithm is without function in mobilityDCAT-AP.
Media Type	`dct:MediaType`	Link	In DCAT-AP-v3.0.0, this class is only used as the range of the optional properties `dcat:compressFormat`, `dcat:mediaType` and `dcat:packageFormat"`. of class Distribution. In mobilityDCAT-AP, these properties are removed. So, the class is without function in mobilityDCAT-AP.
Policy	`odrl:Policy`	Link	In DCAT-AP-v3.0.0, this class is only used as the range of the optional property `odrl:hasPolicy` of class Distribution. In mobilityDCAT-AP, this property is removed. So, the class is without function in mobilityDCAT-AP.
Provenance	`dct:ProvenanceStatement`	Link	In DCAT-AP-v3.0.0, this class is only used as the range of the optional property `dct:provenance` of class Dataset. In mobilityDCAT-AP, this property is removed. So, the class is without function in mobilityDCAT-AP.
Role	`dcat:Role`	Link	In DCAT-AP-v3.0.0, this class is only used as the range of the optional property `dcat:hadRole` of class Relationship. In mobilityDCAT-AP, the entire class Relationship is removed (see above). So, the class Role is without function in mobilityDCAT-AP.

Class	Property	URI	Reference DCAT-AP	Note
Catalogue	applicable legislation	`dcatap:applicableLegislation`	Link	In mobilityDCAT-AP, a reference to the applicable legislation is only made on the Dataset Level (see property `dcatap:applicableLegislation`).
Catalogue	catalogue	`dcat:catalog`	Link	No use case for cross-referecing of catalogues identified for mobility data portals or NAPs.
Catalogue	creator	`dct:creator`	Link	In mobilityDCAT-AP, an agent description on the Catalogue level is only provided in property `dct:publisher`.
Catalogue	rights	`dct:rights`	Link	In mobilityDCAT-AP, rights and license information is only provided on the Distribution level (see property `dct:rights`).
Catalogue	service	`dcat:service`	Link	In mobilityDCAT-AP, end points of services are only provided on the Distribution level (see property `dcat:accessURL`).
Catalogue	temporal coverage	`dct:temporal`	Link	In mobilityDCAT-AP, we assume mobility data portals and NAPs are installed permanently.
Catalogue Record	application profile	`dct:conformsTo`	Link
Catalogue Record	change type	`adms:status`	Link
Catalogue Record	descriptione	`dct:description`	Link
Catalogue Record	title	`dct:title`	Link
Dataset	access rights	`dct:accessRights`	Link	In mobilityDCAT-AP, rights and license information is only provided on the Distribution level (see property `dct:rights`).
Dataset	conforms to	`dct:conformsTo`	Link	In mobilityDCAT-AP, information on standards related to the content data is only provided on the Distribution level (see property `mobilitydcatap:mobilityDataStandard`).
Dataset	creator	`dct:creator`	Link	In mobilityDCAT-AP, information about agents related to datasets is provided in properties `dct:publisher` and `dct:rightsHolder`.
Dataset	documentation	`foaf:page`	Link
Dataset	landing page	`dcat:landingPage`	Link	In mobilityDCAT-AP, information on the access to the content data is only provided on the Distribution level (see property `dcat:accessURL`).
Dataset	provenance	`dct:provenance`	Link	In mobilityDCAT-AP, information on the lineage to the content data is provided via properties `dcat:version` and`adms:versionNotes`.
Dataset	qualified attribution	`prov:qualifiedAttribution`	Link	In mobilityDCAT-AP, information about agents related to datasets is provided in properties `dct:publisher` and `dct:rightsHolder`.
Dataset	qualified relation	`dcat:qualifiedRelation`	Link	In mobilityDCAT-AP, information on how datasets are related to each other is provided in properties `dcat:hasVersion`, `dct:isReferencedBy` and `dct:relation`.
Dataset	sample	`adms:sample`	Link	In mobilityDCAT-AP, information on data samples is only provided on the Distribution level (see property `adms:sample`).
Dataset	spatial resolution	`dcat:spatialResolutionInMeters`	Link	In mobilityDCAT-AP, such information might be provided as a free text via property `dct:description`.
Dataset	temporal resolution	`dcat:temporalResolution`	Link	In mobilityDCAT-AP, such information might be provided as a free text via property `dct:description`.
Dataset	type	`dct:type`	Link	In mobilityDCAT-AP, such information might be provided as a theme or category via properties `mobilitydcatap:mobilityTheme` and `dcat:theme`.
Dataset	was generated by	`prov:wasGeneratedBy`	Link	In mobilityDCAT-AP, information about activities related to datasets is provided in properties `dct:publisher` and `dct:rightsHolder`.
Distribution	access service	`dcat:accessService`	Link	In mobilityDCAT-AP, the class `dcat:DataService`, as well as all properties using this class as a range, are not used.
Distribution	availability	`dcatap:availability`	Link
Distribution	byte size	`dcat:byteSize`	Link
Distribution	check sum	`spdx:checksum`	Link
Distribution	compression format	`dcat:compressFormat`	Link
Distribution	has policy	`odrl:hasPolicy`	Link
Distribution	media type	`dcat:mediaType`	Link	In mobilityDCAT-AP, format information is only given via property `dct:format`.
Distribution	packaging format	`dcat:packageFormat`	Link
Distribution	spatial resolution	`dcat:spatialResolutionInMeters`	Link
Distribution	temporal resolution	`dcat:temporalResolution`	Link
Licence Document	type	`dct:type`	Link	In mobilityDCAT-AP, the type of a licence is only provided on the level of a rights statement via property `dct:type`.
Period of Time	beginning	`time:hasBeginning`	Link	In mobilityDCAT-AP, the beginnnin gof a period is only provided via property `dcat:startDate`.
Period of Time	end	`time:hasEnd`	Link	In mobilityDCAT-AP, the end of a period is only provided via property `dcat:endDate`.

Section 1. Introduction is shortened . Generic description about mobilityDCAT-AP is now compiled at the Wikipage. See issue #59.
Section 5. Terminology used in mobilityDCAT-AP is restructured with several subsections and cleaned up, removing ambigous terms like "Publication". See issue #51 and #52.
The organisation and the layout of the elements of the ReSpec documentation are modified, with the goal of alignment with the ReSpec pages of DCAT-AP v3 and geoDCAT-AP v3. In particular, the class and property definitions are now under new sections 7. Main entities, 8. Supportive entities and 9. Datatypes. Further, all property tables are reformatted with new columns for "Definition", "Usage notes" and "Reusage". See issue #108.
Class additions with the goal to expand the expressiveness of mobilityDCAT-AP. These classes have been already defined in DCAT-AP v3.0.0, but now are also explicitly used in mobilityDCAT-AP.

Class dcat:DatasetSeries is added to reflect the new notions in DCAT 3. See issue #115.
Class dct:Standard is added to allow the necessary ranges for property dct:conformsTo of class Distribution and property dct:conformsTo of class Mobility Data Standard. See issue #153.

Property additions with the goal to expand the expressiveness of mobilityDCAT-AP. These properties have been already defined in DCAT-AP v3.0.0, but now are also explicitly used in mobilityDCAT-AP.

Property dct:issued of class Catalogue Record added, replacing the semantically similar property dct:created. See issue #167.
Property dcat:inSeries of class Dataset added, to allow for relating a dataset to a dataset series. See issue #115.
Property foaf:page of class Dataset added. See issue #121.
Property dct:source of class Dataset added. See issue #122.
Property foaf:page of class Distribution added. See issue #89.
Property dct:language of class Distribution added. See issue #92.
Property dct:conformsTo of class Distribution added. See issue #153.
Property dct:modified of class Distribution added. See issue #94.
Property dct:issued of class Distribution added. See issue #94.
Property adms:status of class Distribution added. See issue #96.
Property dct:title of class Mobility Data Standard added. See issue #153.
Property dct:description of class Rights Statement added. See issue #165.

Other changes of existing classes:

Usage notes revised for classes foaf:Agent and vcard:Kind. See issue #61.

Other changes of existing properties:

Cardinality of property mobilitydcatap:dataFormatNotes of class Distribution changed from 0..1 to 0..*, to allow for multilingual versions of such notes. See issue #120.
Usage notes revised for property dcat:contactPoint of classes Dataset and DatasetSeries. See issue #61.
Property mobilitydcatap:mobilityDataStandard of class Distribution is defined as a sub-property of dct:conformsTo. See issue #153.
Cardinality of property mobilitydcatap:mobilityDataStandard of class Distribution changed from 1..1 to 1..*, to allow for information about an applied common mobility data standard PLUS information about individual/national/content-specific profiles or representations of the applied standard. See issue #153.
Usage notes revised for property mobilitydcatap:mobilityDataStandard of class Distribution. See issue #153.
New semantic concept for property dct:conformsTo of class Mobility Data Standard: Label changed from "standard name" to "conforms to". Range changed from skos:Concept to dct:Standard. Cardinality changed from "0..1" to "0..*". Usage notes revised. See issue #153.

Changes in classes and properties, with the goal of alignment with the DCAT-AP v3 and geoDCAT-AP v3 data models. See issue #18.

Classes aligned with the DCAT-AP v3 data model:

Class skos:Concept is renamed from previously "Category".
Class skos:ConceptScheme is renamed from previously "Category Scheme".

Properties aligned with the DCAT-AP v3 data model:

Property foaf:homepage of class Catalogue: range changed from previously rdfs:Resource to foaf:Document.
Property dcat:dataset of class Catalogue: cardinality relaxed from previously "1..*" to "0..*".
Property dct:spatial of class Catalogue: label changed from previously "spatial/geographic" to "geographical coverage".
Property dcatap:applicableLegislation of class Dataset: property is now directly reused from DCAT-AP v3. Previously it was an addition by mobilityDCAT-AP. In this context, the range of this property is changed from previously skos:Concept to eli:LegalResource.
Property dcat:version of class Dataset: URI changed from previously owl:versionInfo to dcat:version.
Property dcatap:applicableLegislation of class Distribution: property added (reason: accordance with the DCAT-AP profile for HVD).
Property locn:geometry of class Location: range changed from previously "rdfs:Literal typed as gsp:wktLiteral or gsp:gmlLiteral" to locn:Geometry.
Property dcat:version of class Mobility Data Standard: URI changed from previously owl:versionInfo to dcat:version.
Property dcat:endDate of class Period of Time: range changed from previously "rdfs:Literal typed as xsd:date or xsd:dateTime" to a new datatype Temporal Literal.
Property dcat:startDate of class Period of Time: range changed from previously "rdfs:Literal typed as xsd:date or xsd:dateTime" to a new datatype Temporal Literal.

Properties aligned with the geoDCAT-AP v3 data model:

Property locn:address of class Agent: cardinality fixed from previously "0..*" to "0..1".
Property org:memberOf of class Agent: cardinality fixed from previously "0..*" to "0..1".
Property foaf:mbox of class Agent: cardinality fixed from previously "0..*" to "0..1", at the same time range changed from previously owl:Thing to rdfs:Resource.
Property foaf:phone of class Agent: cardinality fixed from previously "0..*" to "0..1", at the same time range changed from previously owl:Thing to rdfs:Resource.
Property dct:identifier of class Catalogue: cardinality relaxed from previously "0..1" to "0..*".
Property geodcatap:referenceSystem of class Dataset: URI changed from previously dct:conformsTo, at the same time range changed from previously dct:Standard to skos:Concept.
Property vcard:hasEmail of class Kind: range changed from previously owl:Thing to vcard:Email.
Property vcard:hasEmail of class Kind: cardinality fixed from previously "1..*" to "1..1".
Property vcard:fn of class Kind: cardinality fixed from previously "1..*" to "1..1".
Property vcard:hasURL of class Kind: range changed from previously owl:Thing to rdfs:Resource.

Removals and deprecations of classes and properties:

Property dct:isPartOf of class Catalogue removed, being an inverse property to dct:hasPart. This adheres to the rule of DCAT-AP v3 not to use the inverse of properties."
Property dct:isVersionOf of class Dataset removed, being an inverse property to dcat:hasVersion. This adheres to the rule of DCAT-AP v3 not to use the inverse of properties."
Classes spdx:Checksum, dcat:DataService, dct:MediaType, dct:ProvenanceStatement, dcat:Relationship are removed. These were listed in mobilityDCAT-AP v1 for compatibility reasons, but they are without function in mobilityDCAT-AP. See A.3 Classes and properties not used from DCAT-AP.
Property dcat:accessService of class Distribution removed, because the class dcat:DataService, as well as all properties using this class as a range, are not used in mobilityDCAT-AP. See A.3 Classes and properties not used from DCAT-AP.
Property dct:created of class Catalogue Record is deprecated. See issue #167.
Property mobilitydcatap:grammar of class Distribution is deprecated. See issue #90.
Property mobilitydcatap:schema of class Mobility Data Standard is deprecated. See issue #153.
Property dct:identifier of class Licence Document is deprecated. See issue #165.
Property rdfs:label of class Licence Document is deprecated. See issue #165.

Property dct:source added under optional properties for Class Catalogue Record. This property was used at DCAT-AP v2.0.1, but removed in mobilityDCAT-AP 1.0.1. However, it is used again for harvesting use cases, see the usage note for dct:source. See issue #57.
Cardinality of property "schema" changed from from 0..1 to 0..n. Reason: allow for naming multiple schemas. See issue #56
Property dct:conformsTo added under optional properties for Class Mobility Data Standard. This property describes the name of the mobility data standard. This property is used when a custom instance of class mobilitydcatap:MobilityDataStandard is defined, see the usage note for this property. See issue #65.
Errata and editorial improvements:

Corrected usage note for property cnt:characterEncoding (now linking to IANA register [IANA-CHARSETS]). See issue #34.
Corrected all figures showing UML diagrams (new arrow types). See issue #37.
Corrected reference to [NUTS-CODES] under controlled vocabularies for property dct:spatial. See issue #58.
All controlled vocabularies that are referenced at class and property descriptions are now directly hyperlinked to the specific controlled vocabulary. Before, a generic link to chapter 5.2 Controlled Vocabularies was only given.
several typos corrected

Appendix F (mobilityDCAT-AP Serialisation Files) added.
Appendix G (mobilityDCAT-AP Validation Guidance) added.
Appendix H (mobilityDCAT-AP Enterprise Architect files) added.
Changes in controlled vocabularies:

Frequency: The original controlled vocabulary "update frequency" by mobilityDCAT-AP is deprecated, as it is not needed any longer. Only the EU Authority Table "Frequency" is now used, as it now contains all necessary values. See issue #11.
Mobility Theme: Added references to EC Delegated Regulations via additional dcatap:applicableLegislation properties for all values used in this vocabulary. This allows for an automated tagging of EC Regulations to individual datasets. See issue #8.
Conditions for access and usage: Value list extended to allow for constellations such as "Licence provided, free of charge". See issue #27

Ongoing refinements and additions in mobilityDCAT-AP Wikipage

Errata:
- Figure 2 corrected
- Class mobilitydcatap:MobilityDataStandard was sometimes misspelled as mobilitydcatap:mobilityDataStandard, corrected
- Property mobilitydcatap:mobilityDataStandard of class dcat:Distribution had the range skos:Concept instead of mobilitydcatap:MobilityDataStandard, corrected
- URL linking to Controlled Vocabulary "http://publications.europa.eu/resource/authority/licence" repaired
- text at the beginning of the properties section was leading to a wrong directory with examples, removed (examples are now published under Appendix D)
- several typos corrected
SHACL file updated:
- validations for the controlled vocabularies added (so that the user does not have to add such specifications to their metadata)
- all constraints (Mandatory, Recommended, Optional) added (previously only the Mandatory ones were covered)
UML Class Diagram with focus on mandatory classes and properties added, see section 2.2 mobilityDCAT-AP Overview
Appendix C (mobilityDCAT-AP minimum profile) added
Appendix D (mobilityDCAT-AP example populations) added
Appendix E (mobilityDCAT-AP Wikipage) added

Document completely re-written starting from the [DCAT-AP-v2.0.1] and [GEODCAT-AP-v2.0.0] specifications, with the purpose of using a consistent document structure across DCAT-AP specifications.

Property URI	Used for Class	Vocabulary name and URI	Usage note
+`mobilitydcatap:mobilityTheme`	`dcat:Dataset`	+Mobility Theme	This is a vocabulary created by mobilityDCAT-AP. There are two hierarchical levels: "Data content category" (mandatory) and "Data content sub-catagory” (optional), see the usage note for property `mobilitydcatap:mobilityTheme`.
`dcat:theme`	`dcat:Dataset`	EU Authority Table "Data Theme"	This is a vocabulary by the Publications Office of the European Union. In most cases, it is assumed that the relevant value for mobility data portals is Transport, see the usage note for property `dcat:theme`.
`dct:accrualPeriodicity`	`dcat:Dataset`	EU Authority Table "Frequency"	This is a vocabulary by the Publications Office of the European Union.
+`geodcatap:referenceSystem`	`dcat:Dataset`	+OGC EPSG Coordinate Reference Systems Register	This is a vocabulary added by mobilityDCAT-AP, analogue to an addition by geoDCAT-AP-v3.0.0.
`dct:format`	`dcat:Distribution`	EU Authority Table "File Type"/a>	This is a vocabulary by the Publications Office of the European Union. Please note that mobilityDCAT-AP has different properties related to the format, including `mobilitydcatap:mobilityDataStandard`, `dct:format`, `cnt:characterEncoding`, `mobilitydcatap:grammar`. This controlled vocabulary relates only to `dct:format`, i.e., the base standard that specifies syntactically correct documents.
`dct:language` `dct:language` `dct:language`	`dcat:Catalog` `dcat:CatalogRecord` `dcat:Dataset`	EU Authority Table "Language"	This is a vocabulary by the Publications Office of the European Union.
`dct:identifier`	`dct:LicenseDocument`	EU Authority Table "Licence"	This is a vocabulary by the Publications Office of the European Union.
`dct:publisher` `dct:publisher` `dct:publisher`	`dcat:Catalog` `dcat:CatalogRecord` `dcat:Dataset`	EU Authority Table "Corporate body"	This is a vocabulary by the Publications Office of the European Union. It must be used for European institutions and a small set of international organisations. In case of other types of organisations, national, regional or local vocabularies about organisations should be used, if available.
`dct:spatial` `dct:spatial` `dct:spatial`	`dcat:Catalog` `dcat:Dataset` `dcat:DatasetSeries`	EU Authority Table "Continent" EU Authority Table "Countries and territories" EU Authority Table "Places" GeoNames geographical database EU Taxonomy "Nomenclature of Territorial Units for Statistics" (NUTS)	The EU Authority Tables must be used for continents, countries and places that are in those lists; if a particular location is not in one of the mentioned Named Authority Lists, Geonames URIs must be used. In addition to the EU Authority Tables or Geonames, NUTS URIs may be used.
`dct:type`	`foaf:Agent`	ADMS publisher type vocabulary	This is a vocabulary "Publisher Type", based on the ADMS specification.
+`mobilitydcatap:georeferencingMethod`	`dcat:Dataset`	+mobilityDCAT-AP Vocabulary "Georeferencing method"	This is a vocabulary created by mobilityDCAT-AP.
+`mobilitydcatap:networkCoverage`	`dcat:Dataset`	+mobilityDCAT-AP Vocabulary "Network coverage"	This is a vocabulary created by mobilityDCAT-AP.
+`mobilitydcatap:transportMode`	`dcat:Dataset`	+mobilityDCAT-AP Vocabulary "Transport mode"	This is a vocabulary created by mobilityDCAT-AP.
+`mobilitydcatap:intentedInformationService`	`dcat:Dataset`	+mobilityDCAT-AP Vocabulary "Intended information service"	This is a vocabulary created by mobilityDCAT-AP.
+`mobilitydcatap:mobilityDataStandard`	`dcat:Distribution`	+mobilityDCAT-AP Vocabulary "Mobility data standard"	This is a vocabulary created by mobilityDCAT-AP.
+`mobilitydcatap:grammar`	`dcat:Distribution`	+mobilityDCAT-AP Vocabulary "Grammar"	This is a vocabulary created by mobilityDCAT-AP. As property `mobilitydcatap:grammar` is deprecated, this vocabulary is also deprecated.
+`mobilitydcatap:applicationLayerProtocol`	`dcat:Distribution`	+mobilityDCAT-AP Vocabulary "Application layer protocol"	This is a vocabulary created by mobilityDCAT-AP.
+`mobilitydcatap:communicationMethod`	`dcat:Distribution`	+mobilityDCAT-AP Vocabulary "Communication method"	This is a vocabulary created by mobilityDCAT-AP.
+`dct:type`	`dct:RightsStatement`	+mobilityDCAT-AP Vocabulary "Conditions for access and usage"	This is a vocabulary created by mobilityDCAT-AP.
`adms:status`	`dcat:Distribution`	EU Authority Table "Distribution Status"	This is a vocabulary by the Publications Office of the European Union.

CMC section	CMC element name	Class	Class URI	Property	Property URI
2.2.1.1	Metadata date	Catalogue Record	`dcat:CatalogRecord`	creation date update / modification date	`dct:created` `dct:modified`
2.2.1.2	Metadata language	Catalogue Record	`dcat:CatalogRecord`	language	`dct:language`
2.2.1.3	Metadata point of contact	Catalogue Record Dataset	`dcat:CatalogRecord` `dcat:Dataset`	publisher contact point	`dct:publisher` `dcat:contactPoint`
2.2.2.1	Name of dataset	Dataset	`dcat:Dataset`	title	`dct:title`
2.2.2.2	Description of dataset	Dataset	`dcat:Dataset`	description	`dct:description`
2.2.2.3	Resource Type	Not used in mobilityDCAT-AP.
2.2.2.4	Dataset type category	Dataset	`dcat:Dataset`	theme / category	`mobilitydcatap:mobilityTheme`
2.2.2.5	Dataset detailed type	Dataset	`dcat:Dataset`	theme / category	`mobilitydcatap:mobilityTheme`
2.2.2.6	Service type category	Dataset	`dcat:Dataset`	theme / category	`mobilitydcatap:intentedInformationService`
2.2.2.7	Dataset language	Dataset	`dcat:Dataset`	language	`dct:language`
2.2.2.8	Georeferencing method	Dataset	`dcat:Dataset`	reference system georeferencing method	+`dct:conformsTo` +`mobilitydcatap:georeferencingMethod`
2.2.3.1	Valid from	Dataset Distribution	`dcat:Dataset` `dcat:Distribution`	temporal coverage temporal coverage	`dct:temporal` `dct:temporal`
2.2.3.2	Valid to	Dataset Distribution	`dcat:Dataset` `dcat:Distribution`	temporal coverage temporal coverage	`dct:temporal` `dct:temporal`
2.2.4.1	Area covered by publication	Dataset	`dcat:Dataset`	spatial / geographic coverage	`dct:spatial`
2.2.4.2	Network coverage	Dataset	`dcat:Dataset`	spatial / geographic coverage	`mobilitydcatap:networkCoverage`
2.2.4.3	Network coverage description	Not used in mobilityDCAT-AP.
2.2.5.1	Transportation modes covered	Dataset	`dcat:Dataset`	transportation mode	`mobilitydcatap:transportMode`
2.2.6.1	Publisher	Dataset	`dcat:Dataset`	publisher	`dct:publisher`
2.2.6.2	Data owner	Dataset	`dcat:Dataset`	rights holder	+`dct:rightsHolder`
2.2.7.1	Contract or licence	Distribution	`dcat:Distribution`	rights	`dct:rights`
2.2.7.2	Condition for use	Distribution	`dcat:Distribution`	licence	`dct:license`
2.2.8.1	Data Format- Encoding	Distribution	`dcat:Distribution`	character encoding	+`cnt:characterEncoding`
2.2.8.2	Data Format- Syntax	Distribution	`dcat:Distribution`	format	`dct:format`
2.2.8.3	Data Format- Grammar	Distribution	`dcat:Distribution`	grammar	`mobilitydcatap:grammar`
2.2.8.4	Data Format- Data Model	Distribution	`dcat:Distribution`	mobility data standard	`mobilitydcatap:mobilityDataStandard`
2.2.8.5	Data format description	Distribution	`dcat:Distribution`	data format notes	`mobilitydcatap:dataFormatNotes`
2.2.8.6	Access interface / application layer protocol	Distribution	`dcat:Distribution`	application layer protocol	`mobilitydcatap:applicationLayerProtocol`
2.2.8.7	Communication method	Distribution	`dcat:Distribution`	communication method	`mobilitydcatap:communicationMethod`
2.2.8.8	Access URL	Distribution	`dcat:Distribution`	access URL download URL	`dcat:accessURL` `dcat:downloadURL`
2.2.9.1	Update frequency	Dataset	`dcat:Dataset`	frequency	`dct:accrualPeriodicity`
2.2.9.2	Quality Description	Dataset	`dcat:Dataset`	quality description	`dqv:hasQualityAnnotation`
2.2.9.3	National Body assessment status	Dataset	`dcat:Dataset`	assessment result	`mobilitydcatap:assessmentResult`

mobilityDCAT-AP - Version 3.0.0

A mobility extension for the DCAT application profile for data portals in Europe

Abstract

1. Introduction

1.1 Context

1.2 Scope of this DCAT-AP extension: Enhancing DCAT-AP for Mobility

1.3 Revision history

2. Status

3. License

4. Conformance Statement

4.1 Provider requirements

4.2 Receiver requirements

5. Terminology used in mobilityDCAT-AP

5.1 RDF core definitions

5.2 SEMIC core definitions

5.3 mobilityDCAT-AP core definitions

5.4 Namespaces

6. Overview

6.1 Application profile diagram

7. Main entities

7.1 Agent

7.2 +Assessment

7.3 Catalogue

7.4 Catalogue Record

7.5 Dataset

7.6 Dataset Series

7.7 Distribution

7.8 Kind

7.9 Licence Document

7.10 Location

7.11 +Mobility Data Standard

7.12 +Quality Annotation

8. Supportive entities

8.1 +Address (Core Location)

8.2 +Address (vCard)

8.3 Concept

8.4 Concept Scheme

8.5 Document

8.6 +Email (vCard)

8.7 Frequency

8.8 Geometry

8.9 Identifier

8.10 Legal Resource

8.11 Linguistic System

8.12 Literal

8.13 Media Type or Extent

8.14 +Organisation

8.15 Period of Time

8.16 Resource

8.17 Rights Statement

8.18 Standard

9. Datatypes

10. Controlled Vocabularies

10.1 Requirements for controlled vocabularies

10.2 Controlled vocabularies to be used

10.3 Other controlled vocabularies

11. Agent Types, Agent Roles and Contact Information

12. Accessibility and Multilingual Aspects

13. Privacy and security considerations

14. Acknowledgements

A. Quick Reference of Classes and Properties

A.1 Classes and Properties used in mobilityDCAT-AP

A.2 Properties deprecated from previous version of mobilityDCAT-AP

A.3 Classes and properties not used from DCAT-AP

B. Mapping to Coordinated Metadata Catalogue (CMC)

C. mobilityDCAT-AP minimum profile

D. mobilityDCAT-AP example populations

E. mobilityDCAT-AP Wikipage

F. mobilityDCAT-AP Serialisation Files

G. mobilityDCAT-AP Validation Guidance

H. mobilityDCAT-AP Enterprise Architect files

I. Change Log

I.1 Changes since mobilityDCAT-AP 1.1.0 (17 January 2025)

I.2 Changes since mobilityDCAT-AP 1.0.1 (04 April 2024)

I.3 Changes since mobilityDCAT-AP 1.0.0 (16 October 2023)

I.4 Starting point of mobilityDCAT-AP 1.0.0 (01 January 2023)

J. References

J.1 Normative references

J.2 Informative references