Skip to content

DATEX II v3.7 Downloads

Release notes

Changes from v3.6

Platform Independent Model

New namespaces AfirEnergyInfrastructure and AfirFacilities - The existing namespaces EnergyInfrastructure and Facilities, standardised in CEN TS 16157-10:2022 and CEN TS 16157-12:2022 respectively, do not cover the most recently amended AFIR regulations. We have published these namespaces as stable, with backwards compatibility guarantees, so rather than change them, release 3.7 introduces 2 new namespaces with upgraded versions to cover current AFIR regulations. These new namespaces align with revisions of CEN TS 16157-10 and CEN TS 16157-12 currently submitted for CEN formal vote.

The contents of AfirEnergyInfrastructure are based on the 2022 EnergyInfrastructure version, with changes including:

  • EnergyInfrastructureSite now has optional associated ServiceTypes, and EnergyInfrastructureStation may have multiple associated ServiceTypes, while RefillPoint no longer has a directly associated ServiceType.
  • ServiceType has an optional associated OverallPeriod
  • ServiceType has a new literal physicalAttendance.
  • EnergyInfrastructureStation has new optional attributes totalMaximumPower and renewableSources.
  • Hydrogen-specific information may now be specified at the EnergyInfrastructureStation level.
  • EnergyInfrastructureStation has a further optional Organisation, for mobility service provider(s).
  • ElectricEnergyMix has been refactored to produce EnergyProduct and its subclass ElectricEnergy.
  • Energy rates are now expressed with a specific EnergyRate class with complex properties, instead of the general Facilities::Rates model.
  • A ConnectorType of “mcs” can be specified.
  • ElectricChargingPoint has new properties: current type (AC or DC), explicit number of connectors, charging mode (which has moved from Connector), and others.
  • VehicleSpace is replaced by DedicatedParkingSpaces.
  • External identifiers for Connectors can be specified.
  • HydrogenRefillPoint and OrganicGasRefillPoint have been merged into AlternativeFuelsRefillPoint, and OrganicGasTypeEnum is replaced by an expanded enumeration GasConnectorTypeEnum.
  • Three new unit-specific datatypes have been added: Bar, GramsPerKilowattHour, and KilogramPerDay.

The contents of AfirFacilities are based on the 2022 Facilities version, with changes including: - Further kinds of means of payment can be specified. - It can be specified whether a SupplementalFacility is nearby but distinct from the parent facility. - External identifiers for FacilityObjects can be specified. These use an extensible system where national kinds of identifiers can be added through extended enumerations. The OrganisationSpecification property externalCode is removed as it is replaced by this more general mechanism. - An organisation providing a helpdesk for a FacilityObject can be specified. - The class OrganisationSpecification is renamed to AnOrganisation to emphasise that it should represent one concrete organisation (in contrast to the abstract base class Organisation which may also represent the concept of an unknown or undefined organisation).

Minor backwards-compatible (for XML validation) changes

  • Unused orphaned enumerations RouteProcessingInstructionEnum and IncentiveLevelEnum removed from the extension namespace ReroutingManagementEnhanced.
  • Unused orphaned class OpenlrPointAttributes removed.
  • The “definition” property of class Comment in Situation namespace refined to clarify that this should be used only for information that cannot otherwise be coded.
  • The “definition” property of VersionedReference has been made consistent with its mapping to schemas where any string is allowed.
  • Existing UML comments guiding the usage of multiple instances of location reference elements within a single Location object have been changed from recommendations saying “should” to requirements saying “shall”.
  • The “definition” property of TimePeriodOfDay now explicitly confirms that an endTime before startTime should be interpreted as being in the following day.
  • The “definition” property of laneNumber has added words to clarify the concept of the centreline (which laneNumber increases towards): “including the lane on the centreline in the case of an odd number of lanes for a single carriageway road.” A note is added on this definition to say that 0 may be used to identify the outer hard shoulder.
  • The “definition” property of PercentageDistanceAlongLinearElement::percentageDistanceAlong adds the illustration that 0 represents the starting point and 100 represents the end point.
  • A few definitions have the word “may” changed to “can” to match the precise meanings of these terms that are required by CEN.
  • There are very minor editorial changes to “definition” properties in the TrafficRegulations namespace to align with changes made by CEN editors when preparing CEN TS 16157-11:2025 for publication – no changes of semantics.
  • Typo fix in a definition in CommonExtension.

JSON Schema mapping

One minor change to the mapping has been required during the review process of CEN TS 16157-15: - The “definitions” keyword is now “$defs”. The former was used in older JSON Schema drafts, but our current base 2020-12 uses the latter. Tool support varies, but the latter is now the more reliable choice for tool support.

DATEX II individual modules

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

  • 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.
  • DatexIIAfirEnergy.xml - the DATEX II "AfirEnergyInfrastructure" namespace, as an XMI file for import to an Enterprise Architect UML model.
  • DatexIIAfirFacilities.xml - the DATEX II "AfirFacilities" 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.
  • DatexIIEnergyInfrastructure.xml - the DATEX II "EnergyInfrastructure" 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.
  • DatexIIParking.xml - the DATEX II "Parking" 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.
  • DatexIISituation.xml - the DATEX II "Situation" 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.
  • DatexIITrafficManagementPlan.xml - the DATEX II "TrafficManagementPlan" 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.
  • DatexIIVms.xml - the DATEX II "VMS" namespace, as an XMI file for import to an Enterprise Architect UML model.

Extensions

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.

QEA Files

HTML Model of DATEX II v3.7

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