Fw: attributeFormDefault="unqualified"

["Anne Thomas Manes" <anne@manes.net>]

Questions from the JAXR cmmunity...

----- Original Message -----
From: "Farrukh Najmi" <farrukh.najmi@SUN.COM>
To: <JAXR-INTEREST@JAVA.SUN.COM>
Sent: Saturday, August 09, 2003 1:28 PM
Subject: Re: [JAXR-INTEREST] RI authentication issue


> Jon Maron wrote:
>
> >A search of various sources and querying the W3C schema development group
> >indicates that setting the value to "unqualified" indicates that
attributes
> >must not specify a namespace.
> >
> >-- Jon
> >
> >
> Jon,
>
> Thanks for reporting this issue and for providing some background
> related to it. Based upon your research on the semantics of:
>
> attributeFormDefault="unqualified"
>
> I agree that the current JAXR RI behavior would be technically incorrect.
>
> Here is what we have found after investigating the issue.
>
> The JAXR RI has always provided namespace qualified attribute names on
> the setCredentials (and other) requests. Nothing has changed in the JAXR
> RI in this regard.
>
> Could Sam or someone else from UDDI TC comment on:
>
> -Is it possible that the UDDI V2 schema changed as part of an errata fix
> and changed:
>
> attributeFormDefault="qualified" to attributeFormDefault="unqualified"?
>
> -Why the attributeFormDefault is set to "unqualified"? Just curious.
>
> We will fix this bug in for our next release. Thanks.
>
> --
> Farrukh
>