The static and the dynamic part for measured data do not match exactly to each other. Up to now, the MeasurementSiteTable is referenced from the MeasuredDataPublication. When using more than one MeasurementSiteTables, you habe to use one MeasuredDataPublication per table. This seems to be inconvenient. I suggest a 1:1 mapping between the two messages, so to introduce a new class between MeasuredDataPublication and SiteMeasurements.
Meanwhile I do not longer suggest to add a new class.
The Parking Model uses the same structure, but the parkingTableReference has a multiplicity of [0..*] instead of [1:1] like the measurementSiteTableReference. Maybe this could be a solution.
In any case, Measurement and Parking should be handled analogous when finding a solution for further DATEX versions.
Alternative solution agreed along with Part 5 systematic review comments and
committed in revision 805.
"Change multiplicity of MeasurementSiteTableReference to [1..*]. Do not add any new classes."