2.1

XML Schema that has been automatically generated by the XML Schema generation tool from the DATEX II UML model. The XML schema is used by PSM’s.
The Zip archive includes two schemas, one with definitions and one without definitions.

This is a spreadsheet version of the Data Dictionary for the DATEX II PIM v2.1.

This guide contains documentation for the mapping tool between UML and XML Schema. It is targeted towards users of the DATEX II Schema generation tool.

These are some example XML messages that validate against the DATEX II XML Schema.

This is the top level entry document into the DATEX II specification set. The document describes the way that modelling is handled in DATEX II, especially focusing on the data model aspects. Data modelling in DATEX II takes a formal, metamodel-based approach that allows the process of generating the transfer syntax to be implemented in software. A tool that creates an XML schema from the DATEX II data model based on this methodology is available from this website.

by definition feedType is related to filter facilities used in some implementation where different URLs deliver different types of content based on filters

these attributes should be better related to Exchange package

Today the tool take the version from the assembly (2.0.XX) and uses the major and minor version as part of the namespace and schema name.
Now, we change to version 2.1 and we don't want to change the namespace but the tool should have version 2.1.
In future, the tool version could be removed from the namespce.

Possiby the simpliest solution now is to introduce a configuration parameter in the config file,

The definition of 'Destination' is wrong (or at least ambiguous):

"The specification of the destination of a defined route or itinerary. This may be either a location on a network or an area location."

The aggregation between NetworkLocation and Destination is not in the direction as descibed. What is the use of this aggregation?

Suggestion: Writing a definition for Destination with general terms and putting two explicit definitions on the two aggregations from Itenerary and from NetworkLocation.

All components for data types are derived from the superclass "DataValue". But the component "DataValue" can't be found in the tree (of the DATEX-Tool), as there's nowhere a direct access to this class.
Newertheless it's generated properly in the .xsd; but the idea is to deselect some of the optional attributes in it, which is not possible in my opinion (there might be even some more situations like this).

When a class had a rootElement and was used at other places in the model the selection feature crashed, This only happend on a levelC extension.