Re: Editorial for Part 1 section 2.18

Martin Gudgin wrote:

>I believe the property used to be called {namespace name} and was
>populated with the value of wsdl:definitions/@targetNamespace.
>Personally, I think {namespace name} is the better name, as the property
>is NOT a *target* namespace when it appears on an interface component (
>or any other component for that matter ). To my mine, the notion of
>target namespace is purely a serialization detail.
>
 +1

>
>Gudge
>  
>
--umit

>  
>
>>-----Original Message-----
>>From: www-ws-desc-request@w3.org 
>>[mailto:www-ws-desc-request@w3.org] On Behalf Of Bijan Parsia
>>Sent: 03 August 2004 10:53
>>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.
>>
>>
>>    
>>
>
>
>  
>

-- 
Umit Yalcinalp                                  
Consulting Member of Technical Staff
ORACLE
Phone: +1 650 607 6154                          
Email: umit.yalcinalp@oracle.com