-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing properties for di:DiagramElement in the XMI file #9
Comments
😴 💤 |
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 But that is wrong because all these are inherited from For comparison: Here is the UML model from the DD specification: Proposal: Move |
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: omg-bpm-taskforces/omg-bpm-specs#4 |
The intention seems to have been to specialize |
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.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.
The text was updated successfully, but these errors were encountered: