Issue 4810: Invalid XMI.link.atts in UML 1.4 DTD (uml2-superstructure-ftf) Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com) Nature: Uncategorized Issue Severity: Summary: The DTD for UML 1.4 (ad/01-02-16)(which claims to be XMI 1.1) has a XMI.link.att declaration as follows: <!-- _______________________________________________________________ --> <!-- --> <!-- XMI.link.att defines the attributes that each XML element that --> <!-- corresponds to a metamodel class must have to enable it to --> <!-- function as a simple XLink as well as refer to model --> <!-- constructs within the same XMI file. --> <!-- _______________________________________________________________ --> <!ENTITY % XMI.link.att 'href CDATA #IMPLIED xmi.idref IDREF #IMPLIED xml:link CDATA #IMPLIED xlink:inline (true|false) #IMPLIED xlink:actuate (show|user) #IMPLIED xlink:content-role CDATA #IMPLIED xlink:title CDATA #IMPLIED xlink:show (embed|replace|new) #IMPLIED xlink:behavior CDATA #IMPLIED'> The XMI 1.1 (and XMI 1.2) standard specifies only href and xmi.idref out of these (p4-81 of formal/00-11-02). The others seem to be copied from the "UML 1.1" DTD in the XMI 1.1 appendix (this appendix was removed at XMI 1.2 since it was wrong and misleading). Many of the above link attributes seem actually to be invalid: - xml:link is invalid since this is not part of the xml namespace - xlink:inline, xlink:behavior and xlink:content-role are not part of xlink namespace - xlink:actuate has invalid values - the standard values are (onLoad|onRequest|other|none) - xlink:show is missing values - the full set is (new|replace|embed|other|none) [I guess it is not so much of a problem to exclude certain values] Resolution: Revised Text: Actions taken: January 21, 2002: received issue March 9, 2005: closed issue Discussion: MOF 2.0 XMI does not have linkatts so the issue does not apply. Disposition: Closed, no change End of Annotations:===== From: "Pete Rivett" To: Cc: , Subject: Invalid XMI.link.atts in UML 1.4 DTD Date: Sun, 20 Jan 2002 23:28:20 -0000 Message-ID: <000401c1a20a$26be4160$0100007f@CHIMAY> MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 In-Reply-To: Content-Type: text/plain; charset="us-ascii" X-UIDL: OaF!!]:kd99k'!!+Uc!! The DTD for UML 1.4 (ad/01-02-16)(which claims to be XMI 1.1) has a XMI.link.att declaration as follows: The XMI 1.1 (and XMI 1.2) standard specifies only href and xmi.idref out of these (p4-81 of formal/00-11-02). The others seem to be copied from the "UML 1.1" DTD in the XMI 1.1 appendix (this appendix was removed at XMI 1.2 since it was wrong and misleading). Many of the above link attributes seem actually to be invalid: - xml:link is invalid since this is not part of the xml namespace - xlink:inline, xlink:behavior and xlink:content-role are not part of xlink namespace - xlink:actuate has invalid values - the standard values are (onLoad|onRequest|other|none) - xlink:show is missing values - the full set is (new|replace|embed|other|none) [I guess it is not so much of a problem to exclude certain values] 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. From: "Mutschler, Gene O" To: xmi-rtf@omg.org Subject: FW: issue 4810 -- UML RTF (for now) Date: Mon, 21 Jan 2002 12:04:28 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-UIDL: E=;!!~~@e90fEe9M7Rd9 I believe we can address this by removing all of the xlink-related attributes from XMI.link.att and creating a new entity for the proposed xmi.href, the reference for which we can put into XMI.link.att. Dr. Gene Mutschler Unisys Corp. Mission Viejo, CA + 1 949 380 6617 -----Original Message----- From: Juergen Boldt [mailto:juergen@omg.org] Sent: Monday, January 21, 2002 9:12 AM To: issues@emerald.omg.org; uml-rtf@emerald.omg.org; xmi-rtf@emerald.omg.org Subject: issue 4810 -- UML RTF (for now) This is issue # 4810 Pete Rivett" The XMI 1.1 (and XMI 1.2) standard specifies only href and xmi.idref out of these (p4-81 of formal/00-11-02). The others seem to be copied from the "UML 1.1" DTD in the XMI 1.1 appendix (this appendix was removed at XMI 1.2 since it was wrong and misleading). Many of the above link attributes seem actually to be invalid: - xml:link is invalid since this is not part of the xml namespace - xlink:inline, xlink:behavior and xlink:content-role are not part of xlink namespace - xlink:actuate has invalid values - the standard values are (onLoad|onRequest|other|none) - xlink:show is missing values - the full set is (new|replace|embed|other|none) [I guess it is not so much of a problem to exclude certain values] ================================================================ Juergen Boldt Senior Member of Technical Staff Object Management Group Tel. +1-781 444 0404 ext. 132 250 First Avenue, Suite 201 Fax: +1-781 444 0320 Needham, MA 02494, USA Email: juergen@omg.org URL: www.omg.org ================================================================