The DATEX Tool is not Windows 10 complaint.
In my setup, it ends up reading an XMI file with an unspecific error message. Tagged values are not imported into the Tool. You still can hanlde the Tool, but successor errors will follow.

As there is the possibility to run the program in Windows 7 complaint mode, which works fine, the problem is not too hard right now.

(In case the critical setup is needed for testing, please contact me).

These are a few requirements for the datex2.eu website.
I will also report them to the webmaster.

• When calling datex2.eu without being logged in, the header in the browsers tab titles "access denied". This is unlikely and should be changed (e.g. to 'DATEX II official homepage' or something similar).

this is a test issue to be used only for issue tracker test purposes

CEN ISO/TS 14823 "Graphic data dictionary (GDD)" is a technical specification that provides a very flexible mean to exchange complex road signs. In the perspective to extend VMS information towards vehicles (through cooperative ITS services), it seems relevant to harmonise practices between standards covering simlar topics.
The inclusion of dedicated enumeration lists for VMS pictograms (VmsDatexPictogramEnum) and additional pictograms (VmsDatexSupplementalPictogramEnum) is something rigid, not easily extendable.

There exists an EA-XMI export including this line:

Normal
0

false
false
false

EN-GB
X-NONE
X-NONE

There is the need, to mark attributes (as well as classes, enumerations, literals) as being core components for a specific type of profile in the UML model. Note that I do not use the word "mandatory" here, because optional elements can be covered as well.

In the DATEX tool, it should be possible to select a set of core components (severals sets should be available).
Those elements must stay selected then.

Example:

The difference between aggregations and compositions in the DATEX model seems obscure. There is no ecognisable benefit of using these two different UML constructs. As the model is not an object or computational model, but a model of tarnsfer syntax for data exchange, substructures are always fully contained and under control of the super structure. Hence I propose to use composition only and turn all aggregations in th emodel to compositions.

In the VMS context, there are two enumerations for pictorgrams:
VmsDatexPictogramEnum and VmsDatexSupplementalPictogramEnum.

They are used in two different classes. Newertheless, there are cases, where you need a pcitogram in the supplementary panel which is located only the 'main' enumeration (and maybe vice versa).

Couldn't it be useful to combine them into just one enumeration and use it in both classes?

(By the way: Do we need the 'Datex' in the names of the enumerations?).

These are some VMS feature requests, mostly resulting from German TLS specification (but is not a complete cross check).

• As far as I can see, pictograms cannot be associated with a specific lane (e.g. different speed limits for each lane). The lane attribute should be introduced in VmsPictogramDisplayCharacteristics.

• Proposals for VmsDatexPictogramEnum:
  • snow maybe complemented by fallingSnow and snowOrIceSleekness
  • endOfAllRestrictions
  • blinkingAmber

This document is submitted to CEN to be standardised as Part 6 of CEN Technical Standard 16157. The document itself can only be available on this website as long as the formal CEN standardisation process runs.

The document containing the standard is very extensive and detailed. Therefore more accessible documentation will be created and published on this website later on.

The PIM part is included in version 2.3 that can be found in the Reference Set

In ANNEX A the profile for Truck parking can be found.