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

RE: update part1 docs (editors' drafts) .. - issue with name scop e of top elements

From: Liu, Kevin <kevin.liu@sap.com>
Date: Fri, 17 May 2002 15:13:19 +0200
Message-ID: <99CA63DD941EDC4EBA897048D9B0061DA950FE@uspalx20a.pal.sap-ag.de>
To: "'Sanjiva Weerawarana'" <sanjiva@watson.ibm.com>, "WS-Desc WG (Public)" <www-ws-desc@w3.org>
Hi Sanjiva and all,  A few more issues:

Issue 1:

Section 2.3 states that "The message name attribute provides a unique name
among all messages defined within the enclosing WSDL document"

Issue: This does NOT address the situation when messages are defined in two
separate wsdl files which share the same namespace and then are combined
using the import mechanism. The same issue applies to other elements,
including portType, binding, and services.

Proposal: Change "within the enclosing WSDL document" to "within the same
namespace" for all the top elements

Issue 2:

Section 2.1.1 states that "WSDL documents can be assigned an optional name
attribute of type NCNAME that serves as a lightweight form of documentation.
Optionally, a targetNamespace attribute of type URI may be specified."

Issue: the uniqueness of the wsdl name is not defined. Should it be globally
unique? If two wsdl are define a same target namespaces, can they have the
same name? 

Related issue with import: it's not clear if it's legal with WSDL to import
a wsdl with the same namespaces? in XSD, it's treated as include, but wsdl
doesn't have include machenism.

Regards,
Kevin
Technology Architecture Group, 
SAP Labs, Palo Alto
650-849-5167


-----Original Message-----
From: Sanjiva Weerawarana [mailto:sanjiva@watson.ibm.com]
Sent: Thursday, May 16, 2002 11:40 PM
To: WS-Desc WG (Public)
Subject: update part1 docs (editors' drafts) .. 


.. are attached.

Sanjiva.
Received on Friday, 17 May 2002 09:13:53 GMT

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