Issue 5525: UML Issue - Inconsistency between UML 1.3 XMI and DTD (uml2-superstructure-ftf) Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com) Nature: Clarification Severity: Minor 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. Resolution: Revised Text: Actions taken: July 19, 2002: received issue March 9, 2005: closed issue Discussion: The metamodel and XMI for UML 2.0 are different so this issue is no longer applicable. Disposition: Closed, no change End of Annotations:===== From: "Pete Rivett" To: , , Cc: Subject: UML Issue - Inconsistency between UML 1.3 XMI and DTD Date: Fri, 19 Jul 2002 03:46:12 +0100 X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal 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. Pete Pete Rivett (pete.rivett@adaptive.com) Chief Technology Officer, Adaptive Ltd Dean Park House, 8-10 Dean Park Crescent, Bournemouth, BH1 1HL, UK Tel: +44 (0)1202 449419 Fax: +44 (0)1202 449448 http://www.adaptive.com The information contained in this email and any attached files are confidential and intended solely for the addressee(s). The e-mail may be legally privileged or prohibited from disclosure and unauthorised use. If you are not the named addressee you may not use, copy or disclose this information to any other person. If you received this message in error please notify the sender immediately. Any views or opinions presented here may be solely those of the originator and do not necessarily reflect those of the Company.