Skip to content

DATEX II v3.5 Downloads

Release notes

Platform Independent Model

The TrafficManagementPlan namespace has been significantly revised in line with the current revision process for CEN TS 16157-8. The 3.5 model matches the version undergoing formal vote through CEN. The changes support distributed traffic management collaboration and they address many issues of functionality and quality that had been raised against the previous drafts created by a CEN project team. The namespace is now considered stable in version 3.

The EnhancedRerouting namespace has also been significantly revised in line with the current revision process for CEN TS 16157-8, and matches the version undergoing formal vote through CEN. The changes address many issues of functionality and quality that had been raised against the previous drafts created by a CEN project team.

A few additional enumeration literals have been added in the UrbanExtensions namespace, for active travel, in line with the current revision process for CEN TS 16157-8. An extension namespace called OpenlrBinary has been added to allow a LocationReference to be supplied as OpenLR binary. It is expected that this extension will be promoted to the main LocationReferencing model in version 4.

The TrafficSignal namespace has been removed. This was a namespace created by a CEN project team and it was included in DATEX II releases 3.1 to 3.4, but contained critical bugs. This namespace may be improved and restored in a future release.

The FaultAndStatus namespace has not changed except for the addition of an informative diagram, but with the draft CEN TS 16157-13 having passed through a CEN review since release 3.4, this namespace is now considered stable in version 3.

Minor backwards-compatible changes

  • The Common extensions used by FaultAndStatus have moved from the Draft folder to the Final folder (this makes no difference in schemas).
  • Informative diagram added to FaultAndStatus namespace to show dependencies on other namespaces.
  • Clarified the definition of “bearing” types to specify the direction of increasing value.

Model Files

3.5 is expected to be the last release to use the old EAP format of Enterprise Architect – future releases are expected to use the current QEA format only, which we have also provided since release 3.4. This change only affects users of assembled model files.

JSON Schema mapping

The JSON schema mapping has been improved, to support a better range of code generation frameworks, and to remove limitations on validation.

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.5 both EAP and QEA formats are provided, to allow working with DATEX II models in various EA versions, though in future it is likely that only QEA files will be provided.

  • DatexIIEmptyPIM.eap - the shell of the DATEX II data model, as an Enterprise Architect .eap model. Use this as a base and then import modules or add your own extensions.
  • 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.

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

Warning! The following modules are made available as drafts but have not yet reached their final version 3 forms i.e. non-interoperable changes are expected in a future v3 release.

  • DatexIIControlledZone.xml- the DATEX II "ControlledZone" namespace, as an XMI file for import to an Enterprise Architect UML model.
  • DatexIIGnssExtension.xml - the DATEX II "GNSSExtension" 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.
  • DatexIIOpenlrBinary.xml - the DATEX II "OpenlrBinary" 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 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.5 both EAP and QEA formats are provided, to allow working with DATEX II models in various EA versions, though in future it is likely that only QEA files will be provided.

EAP Files

QEA Files

HTML Model of DATEX II v3.5

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