- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Thu, 2 Sep 2004 11:11:03 -0700
- To: "Bijan Parsia" <bparsia@isr.umd.edu>
- Cc: <public-ws-desc-comments@w3.org>
The Working Group resolved this issue (LC3 [1]) by accepting the
proposal at [2] (below). We will assume you accept this resolution if
we
don't receive an explicit acknowledgement by 1 October.
[1] http://www.w3.org/2002/ws/desc/4/lc-issues/#LC3
[2] http://lists.w3.org/Archives/Public/www-ws-desc/2004Aug/0016.html
> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]
On
> Behalf Of Bijan Parsia
> Sent: Tuesday, August 03, 2004 2:53 AM
> To: www-ws-desc@w3.org
> Subject: Editorial for Part 1 section 2.18
>
>
> "2.18 QName resolution
>
> In its serialized form WSDL makes significant use of references
between
> components. Such references are made using the Qualified Name, or
> QName, of the component being referred to. QNames are a tuple,
> consisting of two parts; a namespace name and a local name. For
> example, in the case of an Interface component, the namespace name is
> represented by the {namespace name} property and the local name is
> represented by the {name} property."
>
> I can't find any {namespace name} *property* (component). Perhaps it
is
> the {targetNamespace}?
>
> I see lots of references to [namespace name] Infoset properties.
>
> Ah, I see in 2.17:
>
> "Within a symbol space, all qualified names (that is, the combination
> of {name} and {target namespace} properties) are unique. Between
symbol
> spaces, the combination of these two properties need not be unique.
> Thus it is perfectly coherent to have, for example, a binding and an
> interface that have the same name."
>
> This suggests that it is {targetNamespace}.
>
> Cheers,
> Bijan Parsia.
Received on Thursday, 2 September 2004 18:11:10 UTC