TMC Event codes distinguish between "danger of aquaplaning" (1002) and "surface water hazard" (1041), DATEX II does not. Proposal is to add "aquaplaning" to  WeatherRelatedRoadConditionTypeEnum.

For some TrafficElements, it is not possible to define specific VehicleCharacteristics.

Concrete example is the safety related message "Strong winds affecting high-sided vehicles". "StrongWinds" is a PoorEnvironmentCondition (thus a TrafficElement), where you cannot attach the vehicleType "highSidedVehicle".
(Note: For Accidents and VehicleObstructions, such a link exists).

 A lot of the causes in "normal" traffic infomration are based on what is in the class Activity. These are incidents not managed and not well known by the road operator. In general is not very usefull for the roadoperator to have a situation for these kind of events, as he does not have the detailed information required to fill a situation(record) for this (especially the location is often not available in TMC locationtables).

 the attribute situationRecordCreationReference opens the possibility to refer to a situation record from a different supplier. It would be usefull to have the opportunity to provide more details about the first supplier feed. We have feeds providing subsets of other feeds and we need a reference to which feed is included.

 Extend RoadSurfaceConditionMeasurements so it includes a aggregation to a new FrictionValue class with the attribute coeffientOfFriction. Datatype is a float. 
Norway and Sweden has an extension for this.

 In AffectedCarriagwayAndLanes the attribute carriagway is mandatory, We would it to be optional. Normally we don't have the information about the carriagway.

 In the new 3.0 version the OpenLR extension should be included in the level A model. At the same time we should asses if we should keep TPEG Loc or not? My understanding is that TPEG loc is more or less decrepted and would be replaced by URL in future.

 There is a need to send a Liner defined by a list of coordinates. Today two extensions for this is in the extension directory. The Linear by coordinates extension and LineString extension. In Sweden and Norway we use the LineString extension. In version 3 we would like at least one of this extensions to be included.

Single DATEX elementary  Information may be related to some organization which is responsible of the data which is delivered among centres

i.e. the Road Owner which directly manages Traffic Management Centres, or Police Centres which manage information for public national or regional road 

the organization which is responsible of this information should be clearly identified in DATEX, which thing is not explicitly and completely covered in the current model as we have

These are bug fixes, improvements and proposals for changes on the Parking model for DATEX II version 3.0.
A technical note for migration of the ParkingPublications to Level A is also included.

Bug fixes
- ParkingTypeOfGroup must end with ‘Enum’
- parkingOccupanyDetectionType: Typo in attribute name (missing ‘c’) (two times, in ParkingSpaceBasics and in ParkingRecord!)

Improvements