conditions for access and usage
type: AnnotationProperty
type: Property
type: ObjectProperty
domain includes: RightsStatement
range includes: Concept
comment: This property SHOULD be used to indicate the conditions if any contracts, licences and/or are applied for the use of the dataset. 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 § 5.2 Controlled vocabularies to be used is provided. The values can be logically mapped with the property dct:identifier from class dct:LicenseDocument.
term status: stable
scope note: In mobilityDCAT-AP, this is a mandatory property to be used for Rights Statement.
scope note: This property refers to a type of the Agent that makes the Catalogue, Catalogue Record, Data Service, or Dataset available
status: CURRENT

notation
scope note: This property contains a string that is an identifier in the context of the identifier scheme referenced by its data type.

title
type: AnnotationProperty
scope note: This property contains a name given to the mobility data portal, a name of the Category Scheme, a name given to the Data Service, a 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 name - see § 8. Accessibility and Multilingual Aspects. The language versions 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.

intended information service
type: Property
type: ObjectProperty
domain includes: Dataset
range includes: Concept
comment: This property MAY describe predefined information services, 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 2017/1926 [EC-MMTIS-DR]. 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 about a road network. A controlled vocabulary § 5.2 Controlled vocabularies to be used is provided.
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Datasets.
status: CURRENT

endpointDescription
scope note: This property contains a description of the Data Services available via the endpoints, including their operations, parameters etc. The property gives specific details of the actual endpoint instances, while dct:conformsTo is used to indicate the general standard or specification that the endpoints implement.

phone
type: Property
type: ObjectProperty
domain includes: Kind
range includes: Thing
comment: This property MAY be used to provide the phone number of the Kind, specified using fully qualified tel: URI scheme [RFC3966]. This property is analogue to an addition by [GEODCAT-AP-v2.0.0].
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Kind.
status: CURRENT

name
type: DatatypeProperty
domain includes: Kind
range includes: Literal
comment: This property contains a name of the Kind. This property can be repeated for different versions of the name (e.g., the name in different languages) - see § 8. Accessibility and Multilingual Aspects. This property is analogue to an addition by [GEODCAT-AP-v2.0.0].
term status: stable
scope note: In mobilityDCAT-AP, this is a recommended property to be used for Kind.
status: CURRENT

accrualPeriodicity
scope note: This property 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 data services, e.g., data feeds, the frequency should correspond to the technical upload / data push frequency. For static data sets, 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 § 5.2 Controlled vocabularies to be used is provided. The obligation of this property is raised to “mandatory”, compared to [DCAT-AP-v2.0.1].

mobilityDCAT-AP
type: Vocabulary
type: Ontology
type: Asset
abstract: mobilityDCAT-AP is an extension of the DCAT application profile for data portals in Europe (DCAT-AP) [DCAT-AP]. It allows for a structured, interoperable and harmonised way to describe and exchange metadata about datasets and data services with a mobility relevance.
alternative: mobilityDCAT-AP - Version 3.0.0: A mobility extension for the DCAT application profile for data portals in Europe
standard name: r5r
standard name: process-and-methodology-developing-semantic-agreements
standard name: change-and-release-management-policy-dcat-ap
standard name: vocab-dcat-3
creation date: 2023-05-11
creator: NAPCORE SWG 4.4
date copyrighted: 2023
issued: 2023-05-11
license: https://creativecommons.org/licenses/by/4.0/
modified: 2025-04-02
publisher: napcore.eu
rights holder: napcore.eu
conditions for access and usage: c 89b4bdb7
conditions for access and usage: APROF
conditions for access and usage: ONTOLOGY
editor: Lina Molinas Comet
editor: Daham Mohammed Mustafa
preferred namespace prefix: mobilitydcatap
relies on: r5r
relies on: terms
relies on: terms#
relies on: rdf-schema#
relies on: owl#
relies on: core#
relies on: ns#
relies on: content#
relies on: adms#
relies on: dcat#
relies on: dqv#
relies on: locn#
relies on: org#
relies on: prov#
relies on: http://xmlns.com/foaf/0.1/
relies on: ontology#
backward compatible with: https://w3id.org/mobilitydcat-ap/releases/1.1.0/
prior version: https://w3id.org/mobilitydcat-ap/releases/1.1.0/
version IRI: latest
version: 3.0.0
alternative label: mobilityDCAT-AP - Version 3.0.0: A mobility extension for the DCAT application profile for data portals in Europe
prev: https://w3id.org/mobilitydcat-ap/releases/1.1.0/
status: COMPLETED
version notes: Version 3.0.0 extends DCAT-AP v3.0.0, adds DatasetSeries, aligns with geoDCAT-AP v3.0.0, and includes new properties for Dataset and Distribution.
distribution: JSON-LD
  type: AssetDistribution
  format: JSON LD
  format: JSON-LD
  download URL: https://w3id.org/mobilitydcat-ap/drafts/latest/mobilitydcat-ap.jsonld
  media type: ld+json
distribution: Turtle
  type: AssetDistribution
  format: RDF TURTLE
  format: Turtle
  download URL: https://w3id.org/mobilitydcat-ap/drafts/latest/mobilitydcat-ap.ttl
  media type: turtle
distribution: RDF/XML
  type: AssetDistribution
  format: RDF XML
  download URL: https://w3id.org/mobilitydcat-ap/drafts/latest/mobilitydcat-ap.rdf
  media type: rdf+xml
distribution: HTML
  type: AssetDistribution
  format: HTML
  download URL: https://w3id.org/mobilitydcat-ap/drafts/latest/
  media type: text/html

affiliation
type: DatatypeProperty
domain includes: Kind
range includes: Literal
comment: This property MAY be used to specify the affiliation of the Kind. This property can be repeated for different versions of the name (e.g. the name in different languages) - see § 8. Accessibility and Multilingual Aspects. This property is analogue to an addition by [GEODCAT-AP-v2.0.0].
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Kind.
status: CURRENT

licence text
type: AnnotationProperty
type: DatatypeProperty
domain includes: LicenseDocument
domain includes: RightsStatement
range includes: Literal
comment: This property MAY be used to contain the full text of a Licence Document, as a free text. This 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 name - see § 8. Accessibility and Multilingual Aspects. This property is analogue to an addition by [GEODCAT-AP-v2.0.0].
comment: This property MAY describes in a textual form any additional access, usage or licensing information, besides other information under classes dct:RightsStatement and dct:LicenseDocument. This property can be repeated for parallel language versions of the name - see § 8. Accessibility and Multilingual Aspects. This property is analogue to an addition by [GEODCAT-AP-v2.0.0].
label: Additional information for access and usage
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Licence Document.
scope note: In mobilityDCAT-AP, this is a recommended property to be used for Rights Statement
status: CURRENT

ConceptScheme
scope note: A categorisation scheme, i.e. a classification or a taxonomy, listing all potential categories which might be used for instances of class Category. In mobilityDCAT-AP, this scheme is expressed via a controlled vocabulary for the property ''dcat:theme'' of class Dataset.

Agent
scope note: An entity (e.g., an individual or an organisation) that is associated with Catalogues, Catalogue Records, or Datasets. If the Agent is an organisation, the use of the Organization Ontology [VOCAB-ORG] is recommended. See § 7. Agent Types, Agent Roles and Agent Properties for a discussion on Agent types, roles and properties. The ''foaf:mbox'' mandatory property is not included in [DCAT-AP-v2.0.1]. The ''foaf:workplaceHomepage'' recommended property is not included in [DCAT-AP-v2.0.1], The ''locn:address'', ''org:memberOf'', ''foaf:firstName'', ''foaf:phone'', ''foaf:surname'' optional properties are not included in [DCAT-AP-v2.0.1].

LicenseDocument
scope note: A legal document giving official permission to do something with a resource. The ''dct:identifier'' recommended property is not included in [DCAT-AP-v2.0.1]. The licence type recommended property is removed from [DCAT-AP-v2.0.1]. The ''rdfs:label'' optional property is not included in [DCAT-AP-v2.0.1].

address
type: Property
type: ObjectProperty
domain includes: Kind
range includes: Address
comment: This property MAY be used to specify the postal address of the Kind. This property is analogue to an addition by [GEODCAT-AP-v2.0.0].
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Kind.
status: CURRENT

accessRights
scope note: This property MAY include information regarding access or restrictions based on privacy, security, or other policies. For INSPIRE metadata, this property SHOULD be used with the URIs of the ''Limitations on public access'' code list operated by the INSPIRE Registry [INSPIRE-LPA].

quality annotation target
type: Property
type: ObjectProperty
domain includes: Quality Annotation
range includes: Dataset
comment: This property MAY be used to describe the target of the quality annotation, referring back to the dataset being described. I.e., it is the inverse property of “dqv:hasQualityAnnotation” for class Dataset.
scope note: In mobilityDCAT-AP, this is an optional property to be used for Quality Annotation.
status: CURRENT

Dataset
scope note: 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.

version
type: DatatypeProperty
domain includes: Mobility Data Standard
range includes: Literal
comment: This property describes 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., only “3.2”, without redundant acronyms such as “v”, underscores etc.
scope note: In mobilityDCAT-AP, this is an optional property to be used for Mobility Data Standard.
scope note: Deprecated in v3.0.0. Use dcat:version instead for Dataset and MobilityDataStandard version information.
status: CURRENT

transportation mode
type: Property
type: ObjectProperty
domain includes: Dataset
range includes: Concept
comment: This property describes the transport mode that is covered by the delivered content. Data can be valid for more than one mode, so a multiple choice should be applied. A controlled vocabulary § 5.2 Controlled vocabularies to be used is provided, denoting commonly used transport modes.
term status: stable
scope note: In mobilityDCAT-AP, this is a recommended property to be used for Datasets.
status: CURRENT

email
type: Property
type: ObjectProperty
domain includes: Kind
range includes: Thing
comment: This property contains an email address of the Kind, specified using fully qualified mailto: URI scheme [RFC6068]. This property is analogue to an addition by [GEODCAT-AP-v2.0.0].
term status: stable
scope note: In mobilityDCAT-AP, this is a recommended property to be used for Kind.
status: CURRENT

themeTaxonomy
scope note: The value to be used for this property is the URI of the vocabulary itself, i.e. the concept scheme, not the URIs of the concepts in the vocabulary.

documentation
type: Property
type: ObjectProperty
domain includes: Dataset
domain includes: Distribution
range includes: Document
comment: A page or document about this dataset or distribution.
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Dataset and Distribution.
status: CURRENT

algorithm
scope note: This property identifies the algorithm used to produce the subject Checksum. Currently, SHA-1 is the only supported algorithm. It is anticipated that other algorithms will be supported at a later time.

assessment result
type: Property
type: ObjectProperty
type: DatatypeProperty
domain includes: Assessment
domain includes: Quality Annotation
range includes: Resource
range includes: Literal
comment: This property MAY be used to describe the result of the latest assessment procedure, in form of a URL linking to further details or results. Alternatively, textual information MAY be provided using the Embedded Textual Body construction of the Web Annotation Data Model [Web-Annotation-Data-Model], which allows to specify text formats and languages which might be relevant for multilingual purposes.
comment: This property MAY be used to describe any quality aspects regarding the delivered content, in form of a URL linking to further details or results. Alternatively, textual information MAY be provided using the Embedded Textual Body construction of the Web Annotation Data Model [Web-Annotation-Data-Model], which allows to specify text formats and languages which might be relevant for multilingual purposes.
label: quality annotation resource
scope note: In mobilityDCAT-AP, this is an optional property to be used for Assessment.
scope note: In mobilityDCAT-AP, this is an optional property to be used for Quality Annotation.
status: CURRENT

MediaType
scope note: A media type, e.g. the format of a computer file. This class is not explicitly associated with any property in [DCAT-AP-v2.0.1]. In [DCAT-AP-v2.0.1], this class is only used as the range of the optional properties ''dcat:compressFormat'', ''dcat:mediaType'', and ''dcat:packageFormat'' for class Distribution. In mobilityDCAT-AP, however, these properties are removed. Thus, this class SHOULD NOT be used but is kept for compatibility reasons with [DCAT-AP-v2.0.1]

startDate
scope note: This property contains the start of the Period of Time.

network coverage
type: Property
type: ObjectProperty
domain includes: Dataset
range includes: Concept
comment: 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 [EU-TEN-T]. A controlled vocabulary § 5.2 Controlled vocabularies to be used is provided, denoting commonly used road and infrastructure network classes.
term status: stable
scope note: In mobilityDCAT-AP, this is a recommended property to be used for Datasets.
status: CURRENT

language
scope note: This property refers to a language used in the textual metadata describing titles, descriptions, etc. of the metadata entry. The value should 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 § 8. Accessibility and Multilingual Aspects. A controlled vocabulary § 5.2 Controlled vocabularies to be used is provided.

RightsStatement
scope note: 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. As a minimum, it should include an information on the type of conditions for access and usage. Information about concrete licenses can be provided via class License Document. The ''dct:type'' mandatory property is not included in [DCAT-AP-v2.0.1]. The ''rdfs:label'' recommended property is not included in [DCAT-AP-v2.0.1].

first name
type: DatatypeProperty
domain includes: Address (Agent)
range includes: Literal
comment: If the agent is of type person, this property SHOULD be used to specify the first name of the Agent, see section § 7. Agent Types, Agent Roles and Contact Information.
scope note: In mobilityDCAT-AP, this is an optional property to be used for Agent
status: CURRENT

data format notes
type: DatatypeProperty
domain includes: Distribution
range includes: Literal
comment: This property contains any additional information about the format of the delivered content within the Distribution (see the corresponding properties dct:format, mobilitydcatap:mobilityDataStandard, mobilitydcatap:grammar), in a textual format. This might be about, e.g., extensions being used in a mobilitydcatap:mobilityDataStandard.
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Distributions.
status: CURRENT

CatalogRecord
scope note: A description of a metadata entry in the mobility data portal, referring to one data set and its distributions published on the portal. 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-v2.0.1].

Assessment
type: Class
comment: 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 [NAPCORE-NB] and installed individually in each Member State. 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.
term status: stable
scope note: In mobilityDCAT-AP, this is an optional class.
status: CURRENT

URL
type: Property
type: ObjectProperty
domain includes: Kind
range includes: Thing
comment: This property points to a Web site of the Kind. This property is analogue to an addition by [GEODCAT-AP-v2.0.0].
term status: stable
scope note: In mobilityDCAT-AP, this is a recommended property to be used for Kind.
status: CURRENT

Address (Agent)
type: Class
comment: A postal address of the Agent.A postal address of the Agent.
term status: stable
scope note: In mobilityDCAT-AP, this is an optional class.
status: CURRENT

standard name
type: AnnotationProperty
type: DatatypeProperty
domain includes: Mobility Data Standard
range includes: Concept
comment: This property describes the name of the mobility data standard. This property is necessary for the following CASE 1: A custom instance of mobilitydcatap:MobilityDataStandard is defined. Such custom instance is recommended when the mobility data standard is detailed out via properties owl:versionInfo and/or mobilitydcatap:schema. The property dct:conformsTo would then name the mobility data standard via a controlled vocabulary. In the alternative CASE 2, the name the mobility data standard is directly named as range of mobilitydcatap:MobilityDataStandard, again via the same controlled vocabulary.
scope note: In mobilityDCAT-AP, this is an optional property to be used for Mobility Data Standard.
status: CURRENT

quality description
type: Property
type: ObjectProperty
domain includes: Dataset
range includes: Quality Annotation
comment: This property MAY describe any quality aspects regarding the delivered content, in particular methods, metrics/indicators and results of a quality assessment in the responsibility of the Rights Holder (see property dct:rightsHolder). 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 Packages from the EU EIP and NAPCORE projects [EU-EIP-QP], these frameworks should be referenced.
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Datasets.
status: CURRENT

dataset
scope note: This property links the mobility data portal with a data set 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 also mandatory to use the property dcat:record.

endDate
scope note: This property contains the end of the Period of Time.

homepage
scope note: This property refers to a Web page that acts as the main page for the mobility data portal. The obligation of this property is raised to “mandatory”, comparing to [DCAT-AP-v2.0.1].

hasVersion
scope note: This property refers to a related dataset that is a version, edition, or adaptation of the described dataset. Corresponds to the property ''dct:isVersionOf'', with a contrary relationship. It might be used to host multiple versions of the same data set in the data portal, also enabling a version history. Multiple versions should be differentiated via the properties ''dcat:version'' and ''adms:versionNotes''.

creation date
type: AnnotationProperty
type: DatatypeProperty
domain includes: CatalogRecord
range includes: Literal
comment: This property contains the date stamp (date and time) 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-v2.0.0].
scope note: In mobilityDCAT-AP, this is a mandatory property to be used for Catalogue Record. Its range is rdfs:Literal typed as xsd:date or xsd:dateTime.
status: CURRENT

surname
type: DatatypeProperty
domain includes: Address (Agent)
range includes: Literal
comment: If the agent is of type person, this property SHOULD be used to specify the surname of the Agent, see section 7.
scope note: In mobilityDCAT-AP, this is an optional property to be used for Agent
status: CURRENT

checksumValue
scope note: This property provides a lower case hexadecimal encoded digest value produced using a specific algorithm.

applicable legislation
type: Property
type: ObjectProperty
domain includes: Dataset
range includes: LegalResource
comment: This property MAY refer to one or several legal frameworks being relevant for the dataset, e.g., an EC Delegated Regulation which constitutes the purpose of the corresponding data platform (here called National Access Point/NAP), or some other international or national frameworks, e.g., Open Data regulations. For European legal frameworks, it is recommended to use the European Legislation Identifier [ELI] to refer to legislation whenever possible. This property is derived from the DCAT-AP HVD extension [DCAT-AP-HVD].
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Datasets.
status: CURRENT

Relationship
scope note: An association class for attaching additional information to a relationship between DCAT Resources

qualifiedRelation
scope note: In GeoDCAT-AP, this property is used as in DCAT and DCAT-AP.

assessment result
type: Property
type: ObjectProperty
domain includes: Dataset
range includes: Assessment
comment: This property MAY refer to the results and outcomes from an assessment process by some 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 [NAPCORE-NB] 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.
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Datasets.
status: CURRENT

ProvenanceStatement
scope note: A statement of any changes in ownership and custody of a resource since its creation that are significant for its authenticity, integrity, and interpretation. This class is not explicitly associated with any property in [DCAT-AP-v2.0.1]. In [DCAT-AP-v2.0.1], this class is only used as the range of the optional property ''dct:provenance'' for class Dataset. In mobilityDCAT-AP, however, this property is removed. Thus, this class SHOULD NOT be used but is kept for compatibility reasons with [DCAT-AP-v2.0.1].

reference system
type: Property
type: ObjectProperty
domain includes: Dataset
range includes: Concept
comment: The spatial reference system used in the dataset. Spatial reference systems SHOULD be specified using URIs from the EPSG coordinate reference systems register operated by OGC.
term status: stable
scope note: In mobilityDCAT-AP, this is a recommended property to be used for Dataset.
status: CURRENT

specific content model
type: Property
type: ObjectProperty
domain includes: Mobility Data Standard
range includes: Concept
comment: The specific content model of the applied mobility data standard, e.g., SituationPublication or ParkingTablePublication for DATEX II.
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Mobility Data Standard.
status: CURRENT

isReferencedBy
scope note: This property references, cites, or otherwise points to another, related dataset. Corresponds to the property dct:relation, with a contrary relationship. 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.

Concept
scope note: A category of a dataset, i.e. a specific subject, theme, or a class about its content. The category is described via a categorisation scheme, i.e. a classification or a taxonomy. Such scheme lists all potential categories, see class ''Category Scheme''. In mobilityDCAT-AP, this class SHOULD only be used in the context of a data set (via property ''dcat:theme''). In other contexts, e.g. under [geoDCAT-AP-v2.0.0], this might also be used to describe the theme of a Catalogue or Data Service.

format
scope note: This property refers to the technical syntax of the delivered content within the Distribution. It describes the base standard that specifies syntactically correct documents. On this level, only base elements of building documents properly are specified and can be proved by syntax checks. A controlled vocabulary § 5.2 Controlled vocabularies to be used is provided. The obligation of this property is raised to “mandatory”, compared to [DCAT-AP-v2.0.1]. There is a similar property in [DCAT-AP-v2.0.1] dcat:mediaType, which is removed in mobilityDCAT-AP. There reason is the use of Controlled vocabularies: dct:format uses the EU Authority List [EUV-FT], whereas dcat:mediaType uses the IANA media types [IANA-MEDIA-TYPES]. The first one, however, is sufficient to describe the syntaxes commonly used in mobility data portals.

modified
type: AnnotationProperty
scope note: This property contains the most recent date on which the content of a dataset was changed or modified. This is redundant for high-frequency data services, e.g., via a data feed service, where the change date can be derived from the time stamp within the data feed.

endpointURL
scope note: The root location or primary endpoint of the Service (an IRI).

source
type: AnnotationProperty
type: Property
type: ObjectProperty
domain includes: CatalogRecord
range includes: CatalogRecord
comment: This property is 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.
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Catalogue Record.
status: CURRENT

packageFormat
scope note: In GeoDCAT-AP, this property is used as in DCAT and DCAT-AP.

Kind
scope note: A description following the [VCARD-RDF] specification, e.g. to provide telephone number and e-mail address for a contact point. Note that the class vcard:Kind is the parent class for the four explicit types of vCards (vcard:Individual, vcard:Organization, vcard:Location, vcard:Group). This class is not explicitly associated with any property in [DCAT-AP-v2.0.1]. In [DCAT-AP-v2.0.1], this class is only used as the range of the recommended property ''dcat:contactPoint'' for class Dataset. In mobilityDCAT-AP, however, this property is removed, and any contact details are compiled under the Agent class, see § 7. Agent Types, Agent Roles and Agent Properties. Thus, this class SHOULD NOT be used but is kept for compatibility reasons with [DCAT-AP-v2.0.1].

administrative area
type: DatatypeProperty
domain includes: Address (Agent)
range includes: Literal
comment: The administrative area of an Address of the Agent. Depending on the country, this corresponds to a province, a county, a region, or a state.
scope note: In mobilityDCAT-AP, this is a recommended property to be used for Address (Agent)
status: CURRENT

in series
type: Property
type: ObjectProperty
domain includes: Dataset
range includes: Dataset Series
comment: A dataset series of which the dataset is part.
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Dataset.
scope note: Links a dataset to a dataset series of which it is part.
status: CURRENT

schema
type: Property
type: ObjectProperty
domain includes: Mobility Data Standard
range includes: Resource
comment: This property describes the schema of the mobility data standard, as applied within the delivered content. There are differet optiions how to reference the schema. It might be a reference to a portal-internal catalogue of schemas, a reference to an individual schema (that is provided by the data publisher), or a reference to an external catalogue of schemas (like a stakeholder-based DATEX II profile published on the datex2.eu page). The data platform SHOULD keep an archive of commonly used schemas. The data provider SHOULD be able to select an applicable schema from this archive, or to upload an own, individual schema. In any case, the schema should be available as a resource. This is a sub-property of dct:conformsTo.
sub property of: standard name
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Mobility Data Standard.
status: CURRENT

address
type: Property
type: ObjectProperty
domain includes: Address (Agent)
range includes: Address (Agent)
comment: This property MAY be used to specify the postal address of the Agent. This property is analogue to an addition by [GEODCAT-AP-v2.0.0].
scope note: In mobilityDCAT-AP, this is an optional property to be used for Agent
status: CURRENT

email
type: Property
type: ObjectProperty
domain includes: Address (Agent)
range includes: Thing
comment: This property SHOULD be used to provide the email address of the Agent, specified using fully qualified mailto: URI scheme [RFC6068]. The email SHOULD be used to establish a communication channel to the agent. This property is analogue to an addition by [GEODCAT-AP-v2.0.0].
scope note: In mobilityDCAT-AP, this is a mandatory property to be used for Agent
status: CURRENT

spatial
scope note: This property refers to a country code where the data platform is hosted. For National Access Points (NAPs), this corresponds to the EC Member State or a country that installs such NAP. The property might be used for analyses about available data sets 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-v2.0.1].

communication method
type: Property
type: ObjectProperty
domain includes: Distribution
range includes: Concept
comment: This property indicates for data services, e.g., data feeds, if the data interface of the data provider system functions in a push or pull mode. A controlled vocabulary § 5.2 Controlled vocabularies to be used is provided.
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Distributions.
status: CURRENT

Quality Annotation
type: Class
comment: 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. There is a similar class “Quality Measurement” in [GEODCAT-AP-v2.0.0]. Both “Quality Annotation” are “Quality Measurement” are reusing the Data Quality Vocabulary [VOCAB-DQV]. Quality Measurement is referring to concrete metrics, like sub-types of spatial resolutions being used [GEODCAT-AP-v2.0.0]. At mobility data portals, however, the practice so far is to provide some free text about quality aspects. Thus, the Quality Annotation refers to an unspecified form of quality annotation, which MAY be a free text.
term status: stable
scope note: In mobilityDCAT-AP, this is an optional class.
status: CURRENT

Standard
scope note: A standard or other specification to which a Catalogue, Catalogue Record, Data Service, Dataset, or Distribution conforms.. This class is not explicitly associated with any property in [DCAT-AP-v2.0.1]. In [DCAT-AP-v2.0.1], this class is used as the range of property ''dct:conformsTo'' for class Catalogue Record (context ''application profile''); for class Dataset (context' 'conforms to''); and for class Distribution (context ''linked schemas''). In mobilityDCAT-AP, these properties are removed. However, mobilityDCAT-AP uses this class as the range of an added property ''dct:conformsTo'' for class Dataset in a different context ''reference system'', analogue to a property addition by [GEODCAT-AP-v2.0.0]. [GEODCAT-AP-v2.0.0] adds several properties to the class Standard. These describe any standards via an identifier, type, release date etc. However, describing standards is not a main use case of mobilityDCAT-AP, so no properties are added here. If necessary, the properties for class Standard, as added by [GEODCAT-AP-v2.0.0], MAY be used.

downloadURL
scope note: This property contains a URL that is a direct link to a downloadable file in a given format.

Catalog
scope note: 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.

Mobility Data Standard
type: Class
comment: The mobility data standard applied for the delivered content. 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-class of dct:Standard.
subclass of: Standard
term status: stable
scope note: In mobilityDCAT-AP, this is a mandatory class.
status: CURRENT

Document
scope note: A textual resource intended for human consumption that contains information, e.g., a Web page about a Dataset. This class is not explicitly associated with any property in [DCAT-AP-v2.0.1]. In [DCAT-AP-v2.0.1], this class is only used as the range of the recommended properties ''foaf:homepage'' for class Catalogue; the optional properties ''foaf:page'' and ''dcat:landingPage'' for class Dataset; and the optional property ''foaf:page'' for class Distribution. In mobilityDCAT-AP, however, the range of ''foaf:homepage'' for class Catalogue is changed to the more generic range ''rdfs:Resource''. The other, above-mentioned properties are removed. Thus, this class SHOULD NOT be used, but is kept for compatibility reasons with [DCAT-AP-v2.0.1]

Lina Molinas Comet
type: NamedIndividual
type: Person

assessment date
type: AnnotationProperty
type: DatatypeProperty
domain includes: Assessment
range includes: Literal
comment: This property MAY be used to describe the date of the latest assessment procedure.
scope note: In mobilityDCAT-AP, this is an optional property to be used for Assessment. Its range is rdfs:Literal typed as xsd:date or xsd:dateTime.
scope note: This property contains the date of formal issuance (e.g., publication) of the Catalogue.
status: CURRENT

mobility data standard
type: Property
type: ObjectProperty
domain includes: Distribution
range includes: Mobility Data Standard
comment: This property describes 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. A controlled vocabulary § 5.2 Controlled vocabularies to be used is provided, listing common mobility data standards. If no established mobility data standard is applied, an information “proprietary standard” is requested.
sub property of: format
term status: stable
scope note: In mobilityDCAT-AP, this is a mandatory property to be used for Distributions.
status: CURRENT

rights
scope note: This property links to a Rights Statement, i.e., 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-v2.0.1].

street address
type: DatatypeProperty
domain includes: Address (Agent)
range includes: Literal
comment: The street name and civic number of an Address of the Agent.
scope note: In mobilityDCAT-AP, this is a recommended property to be used for Address (Agent)
status: CURRENT

Location
scope note: A spatial region or named place. It can be represented via a named place (controlled vocabulary) or with geographic coordinates, according to DCAT-AP guidelines [DCAT-AP-guideline-spatial]. 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 data set 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, see § 5.2 Controlled vocabularies to be used. Alternatively, geographic clear names MAY be used via property ''skos:prefLabel''. The ''skos:inScheme'' and ''dct:identifier'' recommended properties are not included in [DCAT-AP-v2.0.1]. The ''skos:prefLabel'' optional property is not included in [DCAT-AP-v2.0.1]. Please note that the order of usage is as follows: use the most specific geospatial relationship by preference. E.g. if the spatial description is a bbox, use ''dcat:bbox'', otherwise use ''locn:geometry'' (see § 4.16.2 Optional properties for Location).

character encoding
type: DatatypeProperty
domain includes: Distribution
range includes: Literal
comment: This property describes the technical encoding format of the delivered content within the Distribution. It is described via a character set standard. A controlled vocabulary § 5.2 Controlled vocabularies to be used is provided. This property is analogue to an addition by [GEODCAT-AP-v2.0.0]. This is a sub-property of dct:conformsTo
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Distributions.
status: CURRENT

Distribution
scope note: 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 data set (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 SOAP web service. These are two distributions based on one data set. In [DCAT-AP-v2.0.1], this class has been classified as ‘Recommended’, to allow for cases that a particular Dataset does not have a Distribution, i.e. . However, for the context of mobility data portals, it can be expected that all datasets have one or more Distributions. Thus, the obligation of class Distribution is raised to mandatory, comparing to [DCAT-AP-v2.0.1].

hasPart
scope note: This property refers to a related Catalogue that is part of the described mobility data portal. 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.

DataService
scope note: A collection of operations that provides access to one or more datasets or data processing functions.

versionNotes
type: AnnotationProperty
scope note: This property contains a textual description of the differences between this version and a previous version of the dataset, as an addition to the property dcat:version. This property can be repeated for parallel language versions of the version notes - see § 8. Accessibility and Multilingual Aspects.

record
scope note: This property refers to 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-v2.0.1].

URL
type: Property
type: ObjectProperty
domain includes: Address (Agent)
range includes: Resource
comment: This property MAY be used to specify the Web site of the Agent.
scope note: In mobilityDCAT-AP, this is a recommended property to be used for Agent
status: CURRENT

category scheme
type: Property
type: ObjectProperty
domain includes: Concept
domain includes: Location
range includes: ConceptScheme
comment: This property MAY be used to specify the Category Scheme to which the Category belongs. This property is analogue to an addition by [GEODCAT-AP-v2.0.0].
comment: This property MAY be used to specify the gazetteer to which the Location belongs. This property is analogue to an addition by [GEODCAT-AP-v2.0.0].
label: gazetteer
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Category.
scope note: In mobilityDCAT-AP, this is a recommended property to be used for Location.
status: CURRENT

hadRole
scope note: This property refers to the function of an entity or agent with respect to another entity or resource.

other identifier
type: Property
type: ObjectProperty
domain includes: Catalog
range includes: Identifier
comment: This property MAY be used as an additional identifier, besides dct:identifier. It MAY be referring to a dedicated, EU-wide identificator system of NAPS or other portals, to be introduced in the future.
scope note: In mobilityDCAT-AP, this is an optional property to be used for Catalogue.
status: CURRENT

primaryTopic
scope note: This property links the metadata entry to the dataset described in the entry.

sample
type: Property
type: ObjectProperty
domain includes: Distribution
range includes: Resource
comment: This property refers to a sample Distribution of the Dataset. A data 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-v2.0.1], there is a property adms:sample under the class dcat:Dataset , with a range of dcat:Distribution. This implies, that all mandatory properties from dcat:Distribution, e.g., mobilitydcatap:mobilityDataStandard, must be applied. To simplify the description of the Sample, mobilityDCAT-AP recommends to describe the Sample via a property under class dcat:Distribution. It is assumed that all other properties, as already populated for dcat:Distribution, e.g., mobilitydcatap:mobilityDataStandard, also apply for the description of the data sample.
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Distributions.
status: CURRENT

mobility theme
type: Property
type: ObjectProperty
domain includes: Dataset
range includes: Concept
comment: 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. The corresponding controlled vocabulary § 5.2 Controlled vocabularies to be used is provided. This property is a sub-property of dcat:theme, which is also a further, recommended property of Dataset. To distinguish the both 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 a property dcat:keyword. However, the usage of “theme / category” is preferred, to avoid ambiguity and uncontrolled theme descriptions.
sub property of: theme
term status: stable
scope note: In mobilityDCAT-AP, this is a mandatory property to be used for Dataset.
status: CURRENT

standard licence
type: Property
type: ObjectProperty
type: DatatypeProperty
domain includes: LicenseDocument
domain includes: Catalog
domain includes: Location
range includes: Concept
range includes: Literal
comment: This property MAY be be used to link to a concrete standard license. A controlled vocabulary § 5.2 Controlled vocabularies to be used is provided.
comment: This property MAY contain an identifier for the mobility data portal. 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-v2.0.0].
comment: This property contains the geographic identifier for the Location, e.g., the URI or other unique identifier in the context of the relevant gazetteer. This property is analogue to an addition by [GEODCAT-AP-v2.0.0].
label: identifier
label: geographic identifier
term status: stable
scope note: In mobilityDCAT-AP, this is a recommended property to be used for Licence Document
scope note: In mobilityDCAT-AP, this is an optional property to be used for Catalogue.
scope note: In mobilityDCAT-AP, this is a recommended property to be used for Location.
status: CURRENT

publisher
type: AnnotationProperty
type: Property
type: ObjectProperty
domain includes: CatalogRecord
range includes: Agent
comment: This property refers to 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, then 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. It should include, as a minimum, the name and email address of the entity. The information might be identical to the property “Publisher” of the corresponding dataset. This property is analogue to an addition by [GEODCAT-AP-v2.0.0].
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Catalogue Record.
status: CURRENT

isPartOf
scope note: This property refers to a related Catalogue in which the described mobility data portal is physically or logically included. This property could be used to link the mobility data portal to another data portal, by e.g. harvesting metadata from the mobility data portal into this other portal.

temporal coverage
type: Property
type: ObjectProperty
domain includes: Distribution
range includes: PeriodOfTime
comment: This property describes the beginning and end of the time interval when a data service, e.g., a data feed, is delivered technically via the data platform. If there is no entry it means that the publication gets valid immediately and the timestamp is the same as the metadata timestamp.
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Distributions.
scope note: This property refers to 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).
status: CURRENT

city
type: DatatypeProperty
domain includes: Address (Agent)
range includes: Literal
comment: The city of an Address of the Agent.
scope note: In mobilityDCAT-AP, this is a recommended property to be used for Address (Agent)
status: CURRENT

accessURL
scope note: This property contains 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. However, 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 optional 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. This way, this property is the primary key to link to a data service. There is also specific class dcat:DataService, which can be linked via property dcat:accessService. See § 4.9 Data Service for a usage note about the class Data Service.

geographic name
type: DatatypeProperty
domain includes: Location
range includes: Literal
comment: This property contains a preferred label of the Location. This property can be repeated for parallel language versions of the label - see § 8. Accessibility and Multilingual Aspects. This property is analogue to an addition by [GEODCAT-AP-v2.0.0].
term status: stable
scope note: In mobilityDCAT-AP, this is an optional property to be used for Location.
scope note: This property contains a preferred label of the Category. This property can be repeated for parallel language versions of the label - see § 8. Accessibility and Multilingual Aspects.
status: CURRENT

georeferencing method
type: Property
type: ObjectProperty
domain includes: Dataset
range includes: Concept
comment: This property SHOULD be used to specify the georeferencing method used in the dataset. A controlled vocabulary § 5.2 Controlled vocabularies to be used is provided, denoting commonly used georeferencing methods for mobility data.
term status: stable
scope note: In mobilityDCAT-AP, this is a recommended property to be used for Datasets.
status: CURRENT

geometry
scope note: This property associates any resource with the corresponding geometry.

servesDataset
scope note: This property refers to a Dataset that this Data Service can distribute.

relation
scope note: This property references, cites, or otherwise points to another, related dataset. Corresponds to the property dct:isReferencedBy, with contrary relationship. 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.

phone
type: Property
type: ObjectProperty
domain includes: Address (Agent)
range includes: Thing
comment: This property MAY be used to provide the phone number of the Agent, specified using fully qualified tel: URI scheme [RFC3966]. This property is analogue to an addition by [GEODCAT-AP-v2.0.0].
scope note: In mobilityDCAT-AP, this is an optional property to be used for Agent
status: CURRENT

country
type: DatatypeProperty
domain includes: Address (Agent)
range includes: Literal
comment: The country of an Address of the Agent.
scope note: In mobilityDCAT-AP, this is a recommended property to be used for Address (Agent)
status: CURRENT

name
type: AnnotationProperty
scope note: This property contains a name of the Agent. This property can be repeated for different versions of the name (e.g. the name in different languages) - see § 8. Accessibility and Multilingual Aspects.

license
type: AnnotationProperty
scope note: This property contains the licence under which the Data Service is made available.

centroid
scope note: This property refers to the geographic centre (centroid) of a resource.

accessService
scope note: This property refers to a Data Service that gives access to the Distribution of the Dataset.

temporalResolution
scope note: In GeoDCAT-AP, this property is used as in DCAT and DCAT-AP.

PeriodOfTime
scope note: An interval of time that is named or defined by its start and end dates. Please note that while both properties are recommended, one of the two must be present for each instance of the class ''dct:PeriodOfTime'', if such an instance is present. The start of the period should be understood as the start of the date, hour, minute etc. given (e.g. starting at midnight at the beginning of the day if the value is a date); the end of the period should be understood as the end of the date, hour, minute etc. given (e.g. ending at midnight at the end of the day if the value is a date). The beginning and end properties are removed from [DCAT-AP-v2.0.1].

isVersionOf
scope note: This property refers to a related dataset of which the described dataset is a version, edition, or adaptation. Corresponds to property dct:hasVersion with contrary relationship. It might be used to host multiple versions of the same data set in the data portal, also enabling a version history. Multiple versions should be differentiated via the properties owl:versionInfo and adms:versionNotes.

Checksum
scope note: A value that allows the contents of a file to be authenticated. This class allows the results of a variety of checksum and cryptographic message digest algorithms to be represented. In [DCAT-AP-v2.0.1], this class is defined as the range for the optional property ''spdx:checksum'' of class Distribution. However, in mobilityDCAT-AP, this property is removed. So, the class and its properties are without function but kept for compatibility reasons.

grammar
type: Property
type: ObjectProperty
domain includes: Distribution
range includes: Concept
comment: This property describes 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 controlled vocabulary § 5.2 Controlled vocabularies to be used is provided. This is a sub-property of dct:conformsTo.
sub property of: standard name
deprecated: true
term status: deprecated
scope note: In mobilityDCAT-AP, this is an optional property to be used for Distributions.
status: CURRENT

affiliation
type: Property
type: ObjectProperty
domain includes: Address (Agent)
range includes: Organization
comment: If the agent is of type person, this property SHOULD be used to specify the affiliation of the Agent, see § 7. Agent Types, Agent Roles and Contact Information. This property is analogue to an addition by [GEODCAT-AP-v2.0.0].
scope note: In mobilityDCAT-AP, this is an optional property to be used for Agent
status: CURRENT

postal code
type: DatatypeProperty
domain includes: Address (Agent)
range includes: Literal
comment: The postal code of an Address of the Agent.
scope note: In mobilityDCAT-AP, this is a recommended property to be used for Address (Agent)
status: CURRENT

keyword
scope note: This property contains 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-dependent and make data search difficult. Instead, usage of mobility-related properties with Controlled Vocabularies is recommended, in particular dcat:theme, mobilitydcatap:networkCoverage and mobilitydcatap: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.

Dataset Series
type: Class
comment: A collection of datasets that are published separately, but share some characteristics that group them.
term status: stable
scope note: In mobilityDCAT-AP, this is an optional class added in v3.0.0.
scope note: A collection of datasets sharing common characteristics. Added in mobilityDCAT-AP v3.0.0. It is recommended that at least one Dataset refers to a Dataset Series using dcat:inSeries.
status: CURRENT

description
type: AnnotationProperty
scope note: This property contains a free-text, individual name of the mobility data platform itself. This property MAY be repeated for parallel language versions of the description - see § 8. Accessibility and Multilingual Aspects.

bbox
scope note: This property refers to the geographic bounding box of a resource.

application layer protocol
type: Property
type: ObjectProperty
domain includes: Distribution
range includes: Concept
comment: This property describes the transmitting channel, i.e., the Application Layer Protocol, of the distribution. A controlled vocabulary § 5.2 Controlled vocabularies to be used is provided.
term status: stable
scope note: In mobilityDCAT-AP, this property is recommended to be used for Distributions.
status: CURRENT

theme
scope note: The values to be used for this property are the URIs of the concepts in the vocabulary. This is a vocabulary created by mobilityDCAT-AP. There are two hierarchical levels: ''Data content category'' (mandatory) and ''Data content sub-category'' (optional), see the usage note for property ''dcat:theme''.