W3C home > Mailing lists > Public > www-ws-desc@w3.org > June 2002

Re: Ports, Names, Symbol Spaces and targetNamespace

From: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
Date: Tue, 25 Jun 2002 21:11:56 +0600
Message-ID: <043201c21c5a$a8ab2ce0$02aa7cca@lankabook2>
To: "Martin Gudgin" <mgudgin@microsoft.com>, <www-ws-desc@w3.org>

I had always thought that portNames were only unique within a
<service> .. so I'm definitely +1 with this change.

Sanjiva.

----- Original Message ----- 
From: "Martin Gudgin" <mgudgin@microsoft.com>
To: <www-ws-desc@w3.org>
Sent: Tuesday, June 25, 2002 2:19 PM
Subject: Ports, Names, Symbol Spaces and targetNamespace


> 
> According to WSDL 1.1 the value of the name attribute of all port
> elements in a WSDL document must be unique. Effectively, ports have
> their own symbol space, along with messages, portTypes, bindings and
> services. However, ports do NOT take on the target namespace of the WSDL
> document, so it is impossible to refer to them from elsewhere ( e.g.
> from another WSDL document ). For consistency, it would make sense to
> say that the names of ports need only be unique within the service they
> are contained by.
> 
> Changes to spec:
> 
> In section 3.8 change:
> 
> The name attribute provides a unique name among all ports defined within
> in the enclosing WSDL document
> 
> To 
> 
> The name attribute provides a unique name among all ports defined within
> a given service element
> 
> 
> 
> Changes to schema:
> 
> remove uniqueness constraint on wsdl:service/wsdl:port from definitions
> global element declaration
> Add uniqueness constraint for wsdl:port to service local element
> declaration
> 
> 
> Gudge
Received on Tuesday, 25 June 2002 11:12:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:20 GMT