FYI [Fwd: [Bug 169] New: unable to select prefix to use when writing startTag,endTag, and attribute]

hi,

i have created XmlPull.org entry in bugzilla to keep list of issues 
related ot XmlPull API.

currently automatic email notificaiton does not work so i will keep 
forwarding them to xmlpull-dev (until it starts to work)

to see current list of issues please visit:
http://www.extreme.indiana.edu/bugzilla/buglist.cgi?product=XmlPull.org

thanks,

alek

-------- Original Message --------
Subject: 	[Bug 169] New: unable to select prefix to use when writing 
startTag,endTag, and attribute
Date: 	Mon, 5 Jan 2004 08:22:18 -0500 (EST)
From: 	[email protected]
To: 	[email protected]



http://www.extreme.indiana.edu/bugzilla/show_bug.cgi?id=169

           Summary: unable to select prefix to use when writing
                    startTag,endTag, and attribute
           Product: XmlPull.org
           Version: 1.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: critical
          Priority: P1
         Component: Design
        AssignedTo: [email protected]
        ReportedBy: [email protected]
                CC: [email protected],[email protected]


it seems that to be consistent with XML Infoset it is necessary
to allow optional prefix to be passed to XmlSerializer
in case when namespace is bound ot more than one prefix.
http://www.w3.org/TR/xml-infoset/#infoitem.element 

Liang Fang wrote:
> and I have a question for you about XML prefix.
>
> Originally, when XML Signature signs the following chunk of XML, it is
> like this:
> <Assertion xmlns="urn:oasis:names:tc:SAML:1.0:assertion"
> xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion"
> xmlns:samlp="urn:oasis:names:tc:SAML:1.0:protocol"
> AssertionID="c08274b5e85877cbda6cc293ca0deba6"
> IssueInstant="2004-01-03T05:49:16.840Z">
> </Assertion>
>
> Now after I pass the above xml chunk along with the SOAP messages over to
> the other side, and restore the DOM object to a string, it looks like
> this:
> <saml:Assertion xmlns="urn:oasis:names:tc:SAML:1.0:assertion"
> xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion"
> xmlns:samlp="urn:oasis:names:tc:SAML:1.0:protocol"
> AssertionID="c08274b5e85877cbda6cc293ca0deba6"
> IssueInstant="2004-01-03T05:49:16.840Z">
> </saml:Assertion>
>
> Apparently, they are actually still the same thing, except that the latter
> has "saml" as its prefix. However, XML Signature cannot verify this. It
> thinks the corresponding signature is invalid.
>
> I am wondering: isn't the canonicalization procedure solves the problem?
> -- apparently it doesn't. So how to solve this problem? I think the
> problem here is that it gives two prefix definitions for SAML:
> xmlns="urn:oasis:names:tc:SAML:1.0:assertion" and
> xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion", and the
> parser/serializer has no way to know about the original xml is with which
> one.
>



------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.


-- 
The best way to predict the future is to invent it - Alan Kay


 

Yahoo! Groups Links

To visit your group on the web, go to:
 http://groups.yahoo.com/group/xmlpull-dev/

To unsubscribe from this group, send an email to:
 [email protected]

Your use of Yahoo! Groups is subject to:
 http://docs.yahoo.com/info/terms/