The current mapping of DATEX II to XML schema definitions (XSD) does not support importing other namespaces, since the schemaTypeInclude tagged value does allow providing a bespoke schema definition for a datatype (as used for example for the MultiLingualString class) but this definition is just put as some kind of text macro at the place where the tool would introduce its own type definition if a standard mapping mechanism had been sued instead.

The pictogram definition actually comes from a fixed list of road signs and other pictograms.

TextDisplayAreaSettings" and " PictogramDisplayAreaSettings" Classes

To save a selection with the DATEX Tool (file ending .sel) does not work properly. There are often (always?) more elements included in the resulting sel file (which is a readable xml-structure) than selected in the tree.

Best example is an unselected (empty) tree from the D2 model (XMI export from D2 website model, deselecting the trunk element D2LogicalModel in the tool - which takes some while, by the way). The resulting .sel file ist not empty, as to be expected, but more than 32.000 lines long.

The definition of accuracy is the following:
"The extent to which the value may be subject to error, measured as a percentage of the data value."

This is not along with the default interpretation of accuracy. Usually, the 100% means free of error whereas 0% means never working correct.
The definition seems to imply the contrary, i.e. the percentage value is used in a reversed order.

Suggestion is to adapt the definition to the default meaning.

By using facets, you can narrow the data types to some restricted set or combination of numbers or letters. For example, a string is defined to have a maximum of 1024 characters in the Level-A model.

Up to now, it is not possible to change facets when creating a profile.

Example:
To define a string with 20 characters max., you have the following options right now:

• Changing Level A model - this is not intended
• Adding a custom data type, for example String20

I suggest to add the literals refrigeratedGoods and comestibleGoods to the list of loadTypes.

The existing literal perishableProducts is quite similar, but not the same. Refrigerated goods require some special cooling system and a power connection on parking sites, for example.

Poor environment conditions characterised by the PoorEnvironmentTypeEnum type.This allows you to indicate things like snow, heavy winds.dail, etc. Some of these conditions come along with reduced visibility. If you have an exact numerical value for visibility, you can code his using the minimumVisibilityDistance component. But very often you do not have such a numerical value, you just want to indicate that the conditions come alonf with reduced visibility.

In the XML example files, the schema reference does not point to the current version of the schema (2.1) but to the version 2.0.

I suggest fixing the scham location link in the example messages.

The DATEX Namespace http://datex2.eu/schema/2/2_0 is by definition an URI, not an valid URL. Newertheless it is good pratice to guide users to the schema, if they try to resolve the namespace in a webbrowser.
In DATEX, this doesn't work and produces a 403 error (which is actually no bug, see above).

I suggest to implement some forwarding to the current DATEX schema.