Annex A.3 of prEn 16157-1 as submitted to CCMC for publication describes rules how UML qualifiers are mapped to XSD. The tool implements these rules and the mapping is consistent with the handling of qualiifers in earlier DATEX II versions. Qualifiers are actually used throughout the Level A model, as is the basis for EN 16157-2, 3 and 7 and will be the basis for further parts of the standard.
Nevertheless, there is no rule mentioning the use of UML qualifiers in the main section of the document.

Proposal:

Add the following section to clause 7.2:

At http://www.datex2.eu/datex-node/2012/04/02/329, the website link should be http://met.halogenonline.co.uk

Jon Harrod Booth pointed out that WeekOfMonthEnum is ambiguous, and not aligned with a relevant ISO standard.

(Unfortunately this observation came just after v3 was sent to CCMC.)

The UML Profile initially used the metaclass Composition as the basis for the D2Relation stereotype.
A sparx support engineer recommended to Ian Cornwell that we use Association instead, with an attribute set to indicate the composition, because the Composition metaclass was only kept for UML 1 compatibility.

We tried using the Association metaclass, and this appeared to work in the EA user interface, but this had unwanted impact in the XMI:
- we get extra elements with , implying that something is not recognising the stereotype as part of the profile.

the Class ReroutingManagement raise some doubts for management of this SituationRecord specialisation, it seems improvements are needed to achieve interoperable management.

in particular

For congested, blocked, closed roads or junctions there is a need to specify an advise on suggested / advisory  Exit or Entry
 
Entry or Exit are dependant of direction found on SituationRecord which causes the advice to divert from congested or blocked route
 
There is a need to delive information of which destionation is related the advice. DATEX II manages this adding Destination to Itinerary provided as Rerouting.

It would be very valuable to have a new String attribute "venueName" in PublicEvent.

That has been in place for years in the UK traffic management system specification UTMC, and has been heavily used. But it is surely valuable in all countries.

There are 2 different kinds of generalisation allowed in DATEX:
- Generalisation across the boundary between the core (“level A”) DATEX model and an extension model
- Other inheritance i.e. between 2 concepts within the core, or between 2 concepts within extensions

In the former case DATEX specifications insist that a DATEX “level B extension” mechanism is used (clause 8.2.6 in prEN 16157-1).
But only in the latter case does the specialised subclass inherit the attributes of the superclass.

I'm wondering, what the literal 'convoyService' in GeneralNetworkManagementTypeEnum means.
I expected a convoy of cars, i.e. a platoon.
But in the original name field it says "convoy service due to bad weather" - I'm quite astonished about this. Is it about a hotel, where you are guided by someone with an umbrella?

I suggest to clearify the meaning and to adjust defnition.