MeasuredDataPublication cannot be used for more than one MeasurementSiteTable

Submitted by Joerg Freudenstein on Thursday, 5 May, 2011 - 13:44
Issue ID
44
Component
UML Elaborated Data Pub
Category
Bug report
Priority
Normal
Assigned
Status
Fixed
Source
Website
Description

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.

{"changeLogs":[{"date":1528366266098,"componentOLD":"- Select a value -","component":"UML Elaborated Data Pub","categoryOLD":"- Select a value -","category":"Bug report","priorityOLD":"- None -","priority":"Normal","assignedOLD":"","assigned":"Josef Kaltwasser (18)","statusOLD":"- None -","status":"Fixed"},{"date":1537270154143}]}

Posted by Joerg Freudenstein on February 17, 2024 Permalink

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.

Posted by iancornwell on May 17, 2020 Permalink

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."