Difference between aggregations and compositions oscure

Submitted by Josef Kaltwasser on Tuesday, 2 June, 2015 - 10:03
Issue ID
193
Component
Methodology
Category
Feature request
Priority
Normal
Assigned
Status
Fixed
Source
ES5
Description

The difference between aggregations and compositions in the DATEX model seems obscure. There is no ecognisable benefit of using these two different UML constructs. As the model is not an object or computational model, but a model of tarnsfer syntax for data exchange, substructures are always fully contained and under control of the super structure. Hence I propose to use composition only and turn all aggregations in th emodel to compositions.

{"changeLogs":[{"date":1528109460573,"componentOLD":"- Select a value -","component":"Methodology","categoryOLD":"- Select a value -","category":"Feature request","priorityOLD":"- None -","priority":"Normal","statusOLD":"- None -","status":"Fixed"},{"date":1528109542437,"assignedOLD":"","assigned":"Josef Kaltwasser (18)"},{"date":1537268148956}]}

Posted by Josef Kaltwasser on January 25, 2023 Permalink

DATEX II v3.0 will no longer use aggregations, only compositions.