Short form:
Messages with a Level-B extension will not validate against the original 2.3 model, if they extend an object that is already extended in 2.3 (for example Linaer, GenericPublication).

Not sure if this is also a methodology issue.

Description:
In DATEX II version 2.3, the A-Model is extended by default (for example with OpenLR).
All instances created by extended clients should be able to be validated against the A model.

We should create PIM's per publicatoins. Users who want to work with the model and are only interested in VMS or parking are bothered with loads and loads of modelparts they are not interested in. (this is a request from the SG Porto 2013)

Comment raised by UK during TC approval of CEN/TS 16157-2
Point class – Software libraries frequently have classes named Point, but the DATEX II Point is much more than those classes which typically have only coordinates.

The proposition is to call this PointLocation to suggest that there is more to this class than coordinates - it is a fully described NetworkLocation and a peer of Linear, which we would call LinearLocation.

Comment raised by UK during TC approval of CEN/TS 16157-2
There are various uses of "directionBound" – this term implies a boundary or even a binding, not a heading.

A better term should be used e.g. "flowDirection".

Comment raised by UK during TC approval of CEN/TS 16157-2

In the class "AffectedCarriagewayAndLanes" the word “Affected” may not be valid in all cases. There may be a use for some of the attributes of this class even when the location is not naturally considered as “affected”, for example when specifying the location of a device.

Change the class name to avoid the word "Affected".

Comment raised by UK during the TC approval of CEN/TS 16157-2.

"PredefinedLocationContainer" has used a different solution to the substitutable composite problem mentioned above in relation to GroupOfLocations. It has managed to avoid the term "GroupOfPredefinedLocations", but instead has introduced the term "Container", which is a pollution of the traffic-domain model with an information system concept.
It is suggested a conventional Composite design pattern.

Issue raised by UK in TC approval of CEN/TS 16157-2.
For the package name, “Location” seems preferable to “GroupOfLocations”. One could re-use a class that expressed a single location i.e. "Location".

Comment raised by UK during he TC Approval of CEN/TS 16157-2.
Comment:

Issue raised by UK during the stage "TC comment" of CEN TS 16157-2:
Comment: "Clarifying meaning of "without being exclusive". What is the interpretation if two methods are used to generate an irresolvable location?"

Proposal: woud it be better to make this an excusive choice?

14.00

Normal
0

TMC Event code 897 says "People throwing objects onto the road. Danger". In DATEX II, the best match is "attackOnVehicle" (a DisturbanceActivity), which is semantically not the same (you can think of throwing stones without attacking a vehicle as well as an attack on a vehicle without throwing stones).

Proposal is to add a literal like "throwingObjects" to DisturbanceActivity.