Skip to content

DATEX II v3.6 Downloads

Release notes

Platform Independent Model

The TrafficRegulation and ControlledZone namespaces have been significantly revised in line with the current revision process for CEN TS 16157-11. The changes address issues of functionality and quality that had been raised in a CEN TC review, and the 3.6 model matches the updated version submitted for formal vote through CEN. These namespaces are now considered stable in version 3.

Model elements in the CommonExtension and LocationExtension namespaces that were created for use in the TrafficRegulation or ControlledZone namespaces and were therefore in “Draft” packages until the latter pair of namespaces achieved stability have been moved from “Draft” into “Final” packages within their respective namespaces. That change has no effect on schemas. Some CommonExtension elements for describing kinds of vehicles have had minor improvements arising from the CEN TC review of TS 16157-11. All these extension elements are now considered stable in version 3.

The TrafficManagementPlan namespace has one bugfix allowing activation conditions for a Strategy or Measure to be composite. The model matches the version of CEN TS 16157-8 submitted for 2nd formal vote through CEN. A new extension namespace SituationExtension has been added, containing a simple extension of the enumeration RoadOrCarriagewayOrLaneManagementTypeEnum to identify length and width restrictions.

Minor backwards-compatible changes

  • There are very minor editorial changes to definitions in the FaultAndStatus namespace to align with changes made by CEN editors when preparing CEN TS 16157-13 for publication.
  • Typo fix in a Situation enumeration definition.

Model Files

As planned, 3.6 is the first release where the old EAP format of Enterprise Architect is not supported and only the current QEA format is provided. This change only affects users of assembled model files.

JSON Schema mapping

The JSON schema mapping has had further detailed changes to fix small issues after its significant change for release 3.5 to support current code generation tools.

  • The version of the JSON schema specification used has been upgraded to “2020-12”.
  • Some generated property names have a namespace prefix for disambiguation.
  • Generated schema elements for super-classes contain description metadata advising that only one of the subclass properties shall be populated.
  • An abstract class no longer results in a redundant schema element of the same name.

The mapping is currently being standardised in CEN TS 16157-15 and its stability should be confirmed after CEN TC review.

DATEX II individual modules

DATEX II data models are available as modules for engineers to select and build for their own applications.

Note

From version 16 of Enterprise Architect, the EAP file format is no longer supported, and the default file format is now QEA. In DATEX II release 3.6 only QEA format is provided.

  • DatexIIEmptyPIM.qea - the shell of the DATEX II data model, as an Enterprise Architect .qea model. Use this as a base and then import modules or add your own extensions.
  • DatexIICommon.xml - the DATEX II "Common" namespace, as an XMI file for import to an Enterprise Architect UML model.
  • DatexIILocation.xml - the DATEX II "LocationReferencing" namespace, as an XMI file for import to an Enterprise Architect UML model.
  • DatexIIEnergyInfrastructure.xml - the DATEX II "EnergyInfrastructure" namespace, as an XMI file for import to an Enterprise Architect UML model.
  • DatexIIParking.xml - the DATEX II "Parking" namespace, as an XMI file for import to an Enterprise Architect UML model.
  • DatexIISituation.xml - the DATEX II "Situation" namespace, as an XMI file for import to an Enterprise Architect UML model.
  • DatexIIRoadTrafficData.xml - the DATEX II "RoadTrafficData" namespace, as an XMI file for import to an Enterprise Architect UML model.
  • DatexIIVms.xml - the DATEX II "VMS" namespace, as an XMI file for import to an Enterprise Architect UML model.
  • DatexIITrafficManagementPlan.xml - the DATEX II "TrafficManagementPlan" namespace, as an XMI file for import to an Enterprise Architect UML model.
  • DatexIIUrbanExtensions.xml- the DATEX II "UrbanExtensions" namespace, as an XMI file for import to an Enterprise Architect UML model.
  • DatexIIReroutingManagementEnhanced.xml - the DATEX II "ReroutingManagementEnhanced" namespace, as an XMI file for import to an Enterprise Architect UML model.
  • DatexIIFacilities.xml - the DATEX II "Facilities" namespace, as an XMI file for import to an Enterprise Architect UML model.
  • DatexIIStatus.xml - the DATEX II "Fault and Status" namespace, as an XMI file for import to an Enterprise Architect UML model.
  • DatexIIControlledZone.xml- the DATEX II "ControlledZone" namespace, as an XMI file for import to an Enterprise Architect UML model.
  • DatexIITrafficRegulation.xml - the DATEX II "TrafficRegulation" namespace, as an XMI file for import to an Enterprise Architect UML model.

Note

The following two modules each contain two kinds of content:

  • Content needed for stable namespaces – this is placed in a package named “Final” and will remain backwards compatible in all version 3 releases.
  • Content needed for namespaces yet to reach their final version 3 forms – this is placed in a package named "Draft" and may change in a future version 3 release.

New content may be added to these modules in future version 3 releases

  • DatexIILocationExtension.xml - the DATEX II "CommonExtension" namespace, as an XMI file for import to an Enterprise Architect UML model.
  • DatexIICommonExtension.xml - the DATEX II "LocationExtension" namespace, as an XMI file for import to an Enterprise Architect UML model.

Warning

The following modules have not been confirmed as stable by a CEN standardisation, although no changes are planned at present.

  • DatexIIGnssExtension.xml - the DATEX II "GNSSExtension" namespace, as an XMI file for import to an Enterprise Architect UML model.
  • DatexIIOpenlrBinary.xml - the DATEX II "OpenlrBinary" namespace, as an XMI file for import to an Enterprise Architect UML model.
  • DatexIISituationExtension.xml - the DATEX II "SituationExtension" namespace, as an XMI file for import to an Enterprise Architect UML model.

DATEX II XML Schema

DATEX II XML Schemas are provided for reference, but note that these contain the full content of their corresponding namespace. Software developers are encouraged to use the DATEX II UML models and the DATEX II schema generation tool to create profiled XML Schemas for their specific application, containing only the elements required.

DATEX II JSON Schema

DATEX II JSON Schemas are provided for reference, but note that these contain the full content of their corresponding namespace. Software developers are encouraged to use the DATEX II UML models and the DATEX II schema generation tool to create profiled JSON Schemas for their specific application, containing only the elements required.

DATEX II Schema generation tool

On demand a Windows version is available for expert use. Please contact helpdesk@datex2.eu

DATEX II pre-assembled models for convenience

For convenience there also pre-assembled models with common selections. These can be viewed or managed by the Enterprise Architect Tool that can be downloaded from Sparxsystems.com.

Note

From version 16 of Enterprise Architect, the EAP file format is no longer supported, and the default file format is now QEA. In DATEX II release 3.6 only QEA formats is provided.

QEA Files

HTML Model of DATEX II v3.6

Note

When accessed as files from the local file system, the HTML may not render correctly in all browsers - see sparxsystems.com for further details

Go back to the previous page