RE: Identification of an interface operation

Thanks for your comment.  The WS Description Working Group tracked this
as a Last Call comment LC308 [1].  The Working Group agreed to fix the
problem as you suggest, both here and in similar places in the document
if they exist.

If we don't hear otherwise within two weeks, we will assume this
satisfies your concern.

[1] http://www.w3.org/2002/ws/desc/5/lc-issues/issues.html#LC308

> -----Original Message-----
> From: public-ws-desc-comments-request@w3.org [mailto:public-ws-desc-
> comments-request@w3.org] On Behalf Of Hugo Haas
> Sent: Tuesday, August 23, 2005 4:27 AM
> To: public-ws-desc-comments@w3.org
> Subject: Identification of an interface operation
> 
> This is an editorial comment about Part 1.
> 
> Section 2.4.1 The Interface Operation Component states:
> 
>    Note:
> 
>    Despite having a {name} property, Interface Operation components
> cannot
>    be identified solely by their QName. Indeed, two Interface
> components
>    whose {name} property value has the same namespace name, but
> different
>    local names, can contain Interface Operation components with the
> same
>    {name} property value. Thus, the {name} property of Interface
> Operation
>    components is not sufficient to form the unique identity of an
> Interface
>    Operation component.
> 
> Since we're going through the effort of saying that you can't use
> QNames to identify operations, we should add a reference to our
> definition of fragment identifiers for WSDL documents, and more
> specifically to appendix A.2.6 The Interface Operation Component.
> 
> --
> Hugo Haas - W3C
> mailto:hugo@w3.org - http://www.w3.org/People/Hugo/

Received on Thursday, 15 September 2005 19:04:01 UTC