[Issue 6385] New - XML Namespace prefix missing in PGML

[email protected]
Newsgroups gmane.comp.lang.uml.argouml.issues
Message-ID <[email protected]>
http://argouml.tigris.org/issues/show_bug.cgi?id=6385
                 Issue #|6385
                 Summary|XML Namespace prefix missing in PGML
               Component|argouml
                 Version|0.34.beta1
                Platform|Macintosh
                     URL|
              OS/Version|Mac OS X
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|Other
             Assigned to|linus
             Reported by|simonjwright






------- Additional comments from [email protected] Tue Nov 29 10:11:40 -0800 2011 -------
The PGML output isn’t properly formed XML, because of the argouml prefix in argouml:pathitem’s. There 
should be an xmlns attribute: such as

<pgml xmlns:argouml=“org.argouml” description=“org.......

The reason I care is that I much prefer to keep my models as text rather than the compressed zargo form, 
so that the VCS (in my case Mercurial, but would apply to any VCS) handles changes better. This means I 
need to process the .uml output form, which contains the PGML as well as the XMI, and my XSLT 
processor (Saxon) rejects it:

Error on line 1450 column 34 of file:/Users/simon/coldframe/models/ColdFrame_Examples.uml:
  Error reported by XML parser: undeclared name prefix in: argouml:pathitem

If it’s not possible to amend the PGML format, could we put the attribute at the top level? like:

<uml xmlns:argouml="org.argouml" version="6">

------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=448&dsMessageId=2889098

To unsubscribe from this list, e-mail: [[email protected]].
Please do not reply to this mail. Instead, add your comments in the issue.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.