We have created an extension to VmsMessage::VmsPictrogram named VmsPictogramImageExtension. This extension adds the possibility to transfer a raw bitmap representing the message on the VMS board.

This is to accommodate messages from VMS boards that are utilise a fully graphic LED board. This signs represent a vast number of purposes and hence messages, and at the same time reduce the need for a high number of special purpose signs.

Can this be considered part of version 3.0?

The extension can be found here:
http://www.vianova-eureka.no/datex/2.3/index.htm?goto=5:6:724

Other than expected, roadworksScale does not target the size of the roadworks, but the traffic disruption caused by the roadworks. But I think that this issue is already covered by the attribute severity.

I suggest to change definition of roadworksScale and the corresponding enumeration to target some combination of size, complexity and duration of the roadworks (for example, green cutting for few hours would be minor, whereas a a bridge construction for one year would be major).

The literals for the duration of roadworks are currently defined like this:

Short Term < 1 month
Medium Term 1 month up to 6 month
Long term > 6 months

Are these definitions still useful like this? Expecially for short term roadworks, our expectation is something like <= 24 hours (think about C-ITS solutions), mid term for example 24 hours up to 3 calendar days.

Proposal is to change the limits or to introduce more stages.
I would prefer to get this clarified for the 3.0 version.

The 2016 edition of the DATEX User Forum will been held in Dublin on 13th-14th Sep 2016: check  DUF  Information Page.

In element of the Schema DATEXIISchema_2_2_3 with definitions the word "junction" is written as "junctionon".

In the definition of class KilogramsConcentrationValue it says "grams" instead of "kilograms".

I propose to correct this for version 3.0!

Current tool allows only use via GUI, no command line interface (CLI) is provided.

The tool currently allows to:

- import/validation of (possibly extended) model in form of XMI file
- make selection of features to include in the profile to be created
- save the selection into "selection file" (which can be later reloaded)
- create the XML schema

Currently, all this has to be done via GUI and no CLI is available.

In case, one has automated pipeline for creating documentation of UML profile, lack of CLI is
limiting as it requires someone to do part of the processing manually.

 If you deselect all at root and then eg. select SituationPublication the exchange package is not selected.
First time you deselects all elements the whole model is not delesected. Some elements like trafficStatusValue is not deselected.

I found a bug that caused this..

Will be fixed in both 2.3 och 3.0

I am facing an error when using the schema generation tool on my laptop.
It uses Windows 10 Pro 64 bits (French version).
Description of error:

Normal
0

21

false
false
false

In Enterprise Architect, the PayloadPublication class has got an attribute "defaultLanguage". The Tool produces an inline attribute with name "lang", i.e. there is a discrepance between the names in the EA 'pictures' and in the resulting XSD or XML files.

(This might be a model issue and/or as a Tool issue)..
To be considered whether this is still a problem in Version 3.0.