Data format version

[mobilitydcat-ap]

Data format version

[peterlubrich]

We checked two approaches to resolve this issue:

1. Include the data model and its versions (e.g. "DATEX II v3.2") as additional values in the EU Controlled Vocabulary "File type": this Vocabulary is listing common syntax formats (e.g. XML), whereas DATEX II is more than that: it combines syntax and semantic elements of a domain model (here road traffic information) and even adds technical rules for data exchange. Thus, we decided to add an own property "mobilitydcatap:dataModel" where we list common data models from the mobility sector (via an own Controlled Vocabulary with values "DATEX II", "TN-ITS", "NeTEx" etc.)
2. To include the version number as a suffix to the values of the above-mentioned vocabulary for "mobilitydcatap:dataModel" ("DATEX II v2.3", "DATEX II v3.0" etc.). However, this would make this vocabulary list quite complex, and some metadata users just want to know the model (only "DATEX II"), without the versioning. Thus, we want to keep the distinct (and optional) property "mobilitydcatap:dataFormatVersion".

However, to deal with potential mis-interpretations of "mobilitydcatap:dataFormatVersion", we will refine this property as follows:

1. We will restrict the typing of the version via the usage notes , e.g. only allow short version identifiers without "v", "underscores" etc.
2. We will rename the property to "mobilitydcatap:dataModelVersion", as we explicitly only want to tell the version of the data models (DATEX II etc), and not the versions of other format information (e.g., versions of the XML language). The usage note will be refined accordingly.