W3C home > Mailing lists > Public > public-ws-desc-comments@w3.org > May 2005

Re: Comments

From: Arthur Ryman <ryman@ca.ibm.com>
Date: Fri, 27 May 2005 14:34:59 -0400
To: Rich Salz <rsalz@datapower.com>
Cc: Jonathan Marsh <jmarsh@microsoft.com>, public-ws-desc-comments@w3.org, public-ws-desc-comments-request@w3.org
Message-ID: <OF589B8DC5.130094F1-ON8525700E.00642BED-8525700E.00661356@ca.ibm.com>
Rich,

The answer is "no", we mean more. The problem is that we are assigning 
QNames to "nested" components. In the case you cite, the Interface Fault 
component is nested in an Interface component. While the QName of the 
Interface component is enough to uniquely identlfy it, the Interface Fault 
QName is "local" to the parent Interface.

Put another way, each Interface component defines a new symbol space for 
Interface Fault component names.

We do have a way to globally identify an Interface Fault, and in fact any 
component. This identifier is defined in the media type Appendix A [1] 
where we define Fragment Ids for every WSDL 2.0 component. This is like 
the XML Schema Component Desiginators scheme since WSDL and XSD have 
similar structure and use of QNames.

It is convenient to associate a QName with an Interface Fault since we 
allow inheritance. The namespace of the InterfaceFault QName gives us an 
extra level of qualification and avoids name collisions when we combine 
Interfaces. However, we still can encounter collisions within a target 
namespace so it is a best practice to use unique QNames if you plan to use 
Interface extension.

[1] http://www.w3.org/TR/2005/WD-wsdl20-20050510/#wsdl.interfaceFault

Arthur Ryman,
Rational Desktop Tools Development

phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
intranet: http://labweb.torolab.ibm.com/DRY6/



Rich Salz <rsalz@datapower.com> 
Sent by: public-ws-desc-comments-request@w3.org
05/27/2005 01:54 PM

To
Jonathan Marsh <jmarsh@microsoft.com>
cc
public-ws-desc-comments@w3.org
Subject
Re: Comments







>>[15] http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC89j
> 
> 
> After discussing this for some time, it became apparent there are
> multiple ways to interpret this comment.  For instance, we don't see any
> improper use of namespaces.  Can you elaborate a bit more, and point out
> what you think the worst example is so we can focus on this issue more
> directly?

I will try.  It's been awhile and I've forgotten many details.

Consider the last few paragraphs of section 2.3.1.

I don't understand the "Note" paragraphs.  Are they simply saying to 
compare two QName's, you ahve to compare (namespace-uri,local-name) and 
tha you can't just compare "foo:bar" and "foo:bar" since foo might have 
different bindings?

If the answer is yes, then my response is "well, duh" and you don't have 
to say this every single time.

If the answer is no, and that more is meant, then either I don't 
understand you, which is most likely, or you're using QName's "wrong."

Hope this helps.

                 /r$

-- 
Rich Salz, Chief Security Architect
DataPower Technology                           http://www.datapower.com
XS40 XML Security Gateway   http://www.datapower.com/products/xs40.html
Received on Friday, 27 May 2005 18:35:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:31 GMT