The concept of "profiles" (i.e. selecting the optional elements of the level A model actually used in a service when creating a service specific sub-schema, plus optional level B extension elements) is widely used for DATEX services. The methodology supports this, but the term "DATEX profile" isn't even mentioned in the Methodology document. This is confusing, some basic explanation should be included.

As  some measurement devices are able to have information of plate or country   the information relevant to one specific vehicle could be added to IndividualVehicleDataValues by adding an aggregation from IndividualVehicleData to the Reusable Vehicle Class.. ( see attached pic )

In the Class BasicData the attributes 

measurementOrCalculatedTimePrecision
measurementOrCalculationPeriod
measurementOrCalculationTime

could be also associated to the class SiteMeasurement

For some devices infact these attributes are the same for all MeasuredValues associated to the same site

Normal
0
21

The current DATEX II data model allows having several LRS simultaneously to describe a linear, area or point location. It may imply difficult interpretation if two methods are used that generate an irresolvable location.

The definition of 'Destination' is wrong (or at least ambiguous):

"The specification of the destination of a defined route or itinerary. This may be either a location on a network or an area location."

The aggregation between NetworkLocation and Destination is not in the direction as descibed. What is the use of this aggregation?

Suggestion: Writing a definition for Destination with general terms and putting two explicit definitions on the two aggregations from Itenerary and from NetworkLocation.

In calss AffectedCarriagewayAndLanes the attribute carriageway is requiered. I wonder if this is a bug so it should have been optional. lane is optional and often you don't have the information requiered for carriageway. In our case we sometimes know the lane and often have the lengthAffected but never the cariageway. 

On enum litteral RodMaintenanceTypeEnum.maintenanceWork the originalCode is RWK, that is wrong. It should have been

The VehicleTypeEnum enumeration contains 'caravan', and that's it.
First of all it is not clear to me, whether this includes only the trailer species or also the things that have an engine themself (I call it a 'motorhome' but as I am a non-native speaker this might be AE ir inadequate, or both).
Whatever the language clarification reveals, the current enumeration does not allow a distinction between trailers and vehicles, which I was told is required for proper modelling of parking facilities.

The default extension attribute for a component looks like this (here an example for the component 'Period'):

<xs:element name="periodExtension" type="D2LogicalModel:_ExtensionType" minOccurs="0" />

If there is a Level-B-Extension for the component Period, it will look like this (no error so far):

<xs:element name="periodExtension" type="D2LogicalModel:_PeriodExtensionType" minOccurs="0" />

Of course there will be a complex type "_PeriodExtensionType" defined.

For every component, the DATEX-Tool generates extension points like in the following example:

<xs:element name="windExtension" type="D2LogicalModel:_ExtensionType" minOccurs="0"/>

This means, that the phrase “windExtension” (without underscore!!) is created by the DATEX-Tool, not by the user.
Ergo, the user is not allowed to name a class “WindExtension” (for instance as a level b Extension), because it will also produce the phrase 'name="windExtension"'.