2.1

The attribute 'country' is defined as follows:
"ISO 3166-1 two character country code."

The corresponding enumeration contains codes in lowercase, whereas ISO defines uppercase codes.

Suggestion: Change enumeration codes into uppercase (which produces incompatiblities, of course), or change definition.

The attributes "passageDurationTime" and "presenceDurationTime" both include the phrase "DurationTime" which does not make sense.

The attribute name floatingPointMetreDistance is verbose considering that the floating point nature is clear from the class context (and in our experience this is also the more far more common than integer distance in systems). Elsewhere in DATEX II types and units are often not included in attribute names.

Can the attribute be renamed to metreDistance, or simply distance?

The term "Generic data" in the definition of Basic Data is not appropriate. The class could be called generic but the data in the objects should not.

Suggest that the word "Generic" is removed from the definition.

The attribute name measurementOrCalculatedTimePrecision implies in the case of calculation that it is the time precision that is calculated, whereas from the description the corresponding name should be "measurementOrCalculationTimePrecision".
However, the "measurementOrCalculation" part adds length without adding much value.

Suggest a rename to timePrecision (or measurementOrCalculationTimePrecision).

There is currently no clear way to state the meaning of a travel time – particularly for elaborated data publication of route travel times there are various possibilities: a measured time of a journey just completed, a crude prediction for a journey just starting by summing current link travel times on the route, or a more sophisticated prediction e.g. using a statistical blend of profiles and current conditions, or a traffic flow model.
One would expect travel time in a measured data publication to be for a journey just completed.

There is a need to be able to generate DD based on a selection so that only those selected elements will be generated in the DD. The DD format is excel. For word we have the profiles.

I solution has been created and committed to the 2.0 branch. Will be released in the next version of the tool.

Currente Implementation of the model give a chance to define a situaton record that remain valid for some time using the Overall Period adding information for Valid Period and Invalid Period in which the situation record is not currently valid. 

Once having specified the Overall Period ( in which the situation record is supposed to be valid implicitely ) the  usage of Valid Period could lead to some misunderstandig: in case for the same days or period of time both an invalidPeriod and also a validPeriod is defined.

The modelling of a mobile VMS (component name: VMS) could benefit from the following new attributes:

• remainingAccuCapacity (Minutes)
• qualityOfGpsSignal (Percent)

As there is no datatype for minutes right now, this is also a proposal to add a datatype 'Minutes'.