OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wss] Critical ISSUE (RE: [wss-comment] Enumerations of QNamefault codes)


Rich Salz wrote:
> It helps human reader because they can see, in the schema, what some
> pre-defined QNAME's are.

Yes, but...

>>allows all other QNames, and still makes the wsse: prefix a unique
>>first-class citizen.
> 
> 
> Only if the receiver treats the incoming data as a string, and not as a
> qname.  Since the specs say it's a qname, I think the concern of making
> some strings "special" is more theoretical than practical, and more than
> outweighed by having a technique to (er) enumerate any architected QNAME
> values.

The specs say it's a QName, but the schema doesn't make it so.  Thus, 
this string couldn't be processed identically to other strings that are 
equivalent to it.  Sounds icky all around.

I would rather see the keywords enumerated in the specs than in the 
schema, since the unioning solution seems like a hack (though a cute 
one) that doesn't buy much.  SAML uses the spec-based solution, though 
we have a fixed top-level list of status codes and extensible 
lower-level lists, which is slightly different from WSS.  See Section 
3.4.3.1 in http://www.oasis-open.org/committees/download.php/3406 for 
details.  It explains:

"This attribute contains an XML Schema QName; a namespace prefix MUST
be provided. .... The top-level <StatusCode> values are QNames 
associated with the SAML protocol namespace. The local parts of these 
QNames are as follows: .... Additional second-level status codes MAY be 
defined in future versions of the SAML specification. .... SAML system 
entities are free to define more specific status codes in other 
namespaces, but MUST NOT define additional codes in the SAML assertion 
or protocol namespace."

> Personally, I consider it yet another arugment against qname's instead of
> uri's, but it's too late to fix soap.

+1!

	Eve
-- 
Eve Maler                                        +1 781 442 3190
Sun Microsystems                            cell +1 781 354 9441
Web Products, Technologies, and Standards    eve.maler @ sun.com



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]