Issue 15138: New SMSC Issue on non-resolving hrefs in fUML XMI files (smsc)
Source: Fujitsu (Mr. Tom Rutt, tom(at)coastin.com)
Nature: Uncategorized Issue
Severity: 
Summary: This is an Issue for the SMSC to resolve


Before final publication of fUML the following issue needs to be resolved
in some manner.


In the fUML FTF report there are normative xmi files,
( ptc/10-03-08.zip ), which include hrefs to primitive UML types.


However, these hrefs to not resolve to an actual file on the OMG server.


For example


           <ownedAttribute xmi:type="uml:Property"
             xmi:id="Syntax-CommonBehaviors-BasicBehaviors-OpaqueBehavior-body"
name="body"
             visibility="public" isOrdered="true" isUnique="false">
             <type xmi:type="uml:PrimitiveType"
               href="http://www.omg.org/spec/UML/20090901/uml.xml#String"/>
             <upperValue xmi:type="uml:LiteralUnlimitedNatural"
               xmi:id="Syntax-CommonBehaviors-BasicBehaviors-OpaqueBehavior-body-_upperValue"
               value="*"/>
             <lowerValue xmi:type="uml:LiteralInteger"
               xmi:id="Syntax-CommonBehaviors-BasicBehaviors-OpaqueBehavior-body-_lowerValue"/>
           </ownedAttribute>



where is the  link destination 
http://www.omg.org/spec/UML/20090901/uml.xml  ?    It does not resolve. 
Is this an OMG problem?


Partial explanation from Ed Seideitz



The URI http://www.omg.org/spec/UML/20090901 is the normative URI for
the UML 2.3 namespace (per the policy for URIs that you wrote, I think!
   ). Unfortunately, there does not really seem to be any complete
normative specification of the form of hrefs to standard elements like
http://www.omg.org/spec/UML/20090901/uml.xml#String. We are trying to
fix this in UML 2.4. However, hrefs using the file "uml.xml" have been
pretty common so far.



Resolution: 
Revised Text: 
Actions taken:
March 22, 2010: received issue
Discussion: 

End of Annotations:=====
te: Mon, 22 Mar 2010 14:21:56 -0500 (CDT)
Subject: New SMSC Issue on non resolving hrefs in fuml XMI files
From: "Tom Rutt" <tom@coastin.com>
To: issues@omg.org
Cc: smsc@omg.org
Reply-To: tom@coastin.com
User-Agent: SquirrelMail/1.4.3a
X-Mailer: SquirrelMail/1.4.3a




Source: Tom Rutt (Fujitsu)


Title: New SMSC Issue on non-resolving hrefs in fUML XMI files.


This is an Issue for the SMSC to resolve


Before final publication of fUML the following issue needs to be resolved
in some manner.


In the fUML FTF report there are normative xmi files,
( ptc/10-03-08.zip ), which include hrefs to primitive UML types.


However, these hrefs to not resolve to an actual file on the OMG server.


For example


           <ownedAttribute xmi:type="uml:Property"
             xmi:id="Syntax-CommonBehaviors-BasicBehaviors-OpaqueBehavior-body"
name="body"
             visibility="public" isOrdered="true" isUnique="false">
             <type xmi:type="uml:PrimitiveType"
               href="http://www.omg.org/spec/UML/20090901/uml.xml#String"/>
             <upperValue xmi:type="uml:LiteralUnlimitedNatural"
               xmi:id="Syntax-CommonBehaviors-BasicBehaviors-OpaqueBehavior-body-_upperValue"
               value="*"/>
             <lowerValue xmi:type="uml:LiteralInteger"
               xmi:id="Syntax-CommonBehaviors-BasicBehaviors-OpaqueBehavior-body-_lowerValue"/>
           </ownedAttribute>



where is the  link destination 
http://www.omg.org/spec/UML/20090901/uml.xml  ?    It does not resolve. 
Is this an OMG problem?


Partial explanation from Ed Seideitz



The URI http://www.omg.org/spec/UML/20090901 is the normative URI for
the UML 2.3 namespace (per the policy for URIs that you wrote, I think!
   ). Unfortunately, there does not really seem to be any complete
normative specification of the form of hrefs to standard elements like
http://www.omg.org/spec/UML/20090901/uml.xml#String. We are trying to
fix this in UML 2.4. However, hrefs using the file "uml.xml" have been
pretty common so far.




-- 
Tom Rutt
Tel: +1 732 801 5744
Fax: +1 732 774 5133
email: tom@coastin.com; trutt@us.fujitsu.com