Open barmac opened 4 years ago
😴 💤
extensions are always done differently in UML and XML. But the rest should indeed be in the metamodel. Looking at the DMN 1.4 class diagram also shows a localStyle
and sharedStyle
:
But that is wrong because all these are inherited from DI::DiagramElement
.
For comparison: Here is the UML model from the DD specification:
Proposal: Move localStyle
and sharedStyle
from DMN:DiagramElement
to DI::DiagramElement
and add id
to DI::DiagramElement
. Maybe also add the UML extension mechanism.
This is too big to fix together with the other typos in #8. So I'd suggest we open a separate OMG issue and PR.
It's good input for SCE DI though.
In today's meeting we decided to defer this issue to DMN 1.6 and wait how SCE is solving this. See also: https://github.com/omg-bpm-taskforces/omg-bpm-specs/pull/4
The intention seems to have been to specialize sharedStyle
and localStyle
for DMNDiagramElement
to only permit DMNStyle
The XMI is kind of more correct because it only contains the intended connections between DMN:DiagramElement and DMN:Style.
@barmac since SCE is finished now, we could revisit this issue. I'm afraid though that it is a little too late for DMN 1.6, which has its Content Freeze tomorrow.
Let's keep this in mind for the next edition. It's not a big deal to be honest.
DMN 1.5
DMN 1.6 right?
Currently, the
DMNDI13.xmi
file does not specify any properties of theDI::DiagramElement
:On the other hand, the
DI.xsd
file contains multiple properties of that type:This causes a problem when we try to parse DMN files based on the XMI schema.