-
Key: UML14-101
-
Legacy Issue Number: 5525
-
Status: closed
-
Source: Adaptive ( Mr. Pete Rivett)
-
Summary:
The UML 1.3 DTD implies a reference ModelElement.taggedValue which does not
exist in the UML metamodel XMI file. This causes problems for my product
which is metamodel-driven so reports an error when an import attempts to
supply a value for the non-existent reference. This is strictly speaking a
bug in the DTD (since it's not generated according to the XMI rules):
however changing the DTD might cause inconvenience for vendors who are
making use of it, and because not having the reference would make processing
the tags much harder.At UML 1.4 the reference has been added to the metamodel, which suggests
that the metamodel rather than the DTD be fixed. However this could require
a restructuring to avoid circular package dependencies [see UML issue 3735].The same issue applies to the 'stereotype' reference on ModelElement - again
it should ideally be added to the metamodel.The reason I'm raising the issue on UML 1.3 is that this is the chosen
version for interoperability work. A decision is needed as to which way to
resolve the inconsistency within UML 1.3 without forcing an upgrade to UML
1.4. -
Reported: XMI 1.3 — Fri, 19 Jul 2002 04:00 GMT
-
Disposition: Resolved — UML 1.4.2
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT
UML14 — UML Issue - Inconsistency between UML 1.3 XMI and DTD
- Key: UML14-101
- OMG Task Force: UML 1.4 RTF