From: Anthony M. <to...@am...> - 2003-02-24 12:17:56
|
I am cross posting this email to the MDR mailing list in case someone = there has a comment. Or some suggestions. It would be nice if all the = CASE tool vendors verified their XMI output using some XMI Reader = standard. Of course I'd like them to use the MDR one :-) The Together XMI output type 'XMI 1.1 for UML 1.4 (OMG)' appears to have = a few errors in it. =20 I detected what I believe to be at least 3 errors in the output. Two of = the errors appear to be serious XML errors that prevent the file from = being correctly processed by an XSL transformer. The errors even = prevented my XML browser from displaying the file. =20 The third error is easily corrected using XSL, but the XSL = transformation cannot be done until the first two errors have been = corrected. I have attached the XSL file which will make a Together XMI readable by = the NetBeans MDR. But, remember this XSL file cannot be used until the = first 2 XML errors have been corrected. 1) First line of file reads: <?xml version =3D '1.0' encoding =3D 'UTF8' ?> The above line prevents an XSL processor from reading the file. It = should read: <?xml version =3D '1.0' encoding =3D 'UTF-8' ?> 2) Second line of file reads: <XMI xmi.version =3D '1.1' xmlns:UML =3D '//org.omg/UML/1.3'> I believe that this is not valid namespace syntax given that it causes = the XSL processor to complain. The above line should read: <XMI xmi.version =3D '1.1' xmlns:UML =3D 'org.omg/UML/1.3'> *NOTE: I actually believe they are outputting UML 1.4 not UML 1.3. 3) All instances of: <UML:StructuralFeature.type> <UML:Classifier> <UML:Namespace.ownedElement> <UML:DataType xmi.idref =3D 'G.4'/> </UML:Namespace.ownedElement> </UML:Classifier> </UML:StructuralFeature.type> should be converted to: <UML:StructuralFeature.type> <UML:DataType xmi.idref =3D 'G.4'/> </UML:StructuralFeature.type> |