Re: issue: optional "name" attribute of <definition>

Hi Sanjiva,

+1 to removing as many unnecessary things as we can catch.

Only place I have seen this attribute set consistently is with SOAP
Builders' WSDLs. I am not sure however if they are really using it for any
real purpose or just specifying a value as a convention and don't really
use it otherwise. Perhaps Glen someone more intimately associated with that
effort could comment.

Regards, Prasad

-------- Original Message --------
Subject: issue: optional "name" attribute of <definition>
Resent-Date: Tue, 25 Jun 2002 11:31:00 -0400 (EDT)
Resent-From: www-ws-desc@w3.org
Date: Tue, 25 Jun 2002 21:30:09 +0600
From: "Sanjiva Weerawarana" <sanjiva@watson.ibm.com>
To: "WS-Desc WG \(Public\)" <www-ws-desc@w3.org>


This is somewhat related to the "targetNamespace" issue that Gudge
posted about.

<issue id="issue-remove-optional-name-of-definition">
  <head>Should we remove the optional name attribute of
  &lt;definitions&gt;?</head>

  WSDL 1.1 has an optional attribute on definitions which is defined
  as being used to provide a lightweight form of documentation. I would
  like to remove that as its not clear that that has been useful or
  used.
  <source>Sanjiva Weerwarana</source>
</issue>

Can we get consensus on removing this? I haven't seen any real use
of this attribute so far.

Sanjiva.

Received on Wednesday, 26 June 2002 16:00:47 UTC