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

RE: spelling error

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Thu, 27 May 2004 07:56:16 -0700
Message-ID: <DF1BAFBC28DF694A823C9A8400E71EA203BBDB4B@RED-MSG-30.redmond.corp.microsoft.com>
To: "Sharon Hu" <shu@OfficialPayments.com>, <www-ws-desc@w3.org>

You are right, but we are not processing errata against WSDL 1.1.

> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]
On
> Behalf Of Sharon Hu
> Sent: Wednesday, May 26, 2004 3:35 PM
> To: Jonathan Marsh; www-ws-desc@w3.org
> Subject: RE: spelling error
> 
> 
> 
> 
> 
> Also I am reading Web Services Description Language (WSDL) 1.1
> http://www.w3.org/TR/wsdl#_wsdl
> 
> 2.1.4 Documentation
> WSDL uses the optional wsdl:document element as a container for human
> readable documentation. The content of the element is arbitrary text
and
> elements ("mixed" in XSD). The documentation element is allowed inside
any
> WSDL language element.
> 
> Should it be "wsdl:documentation element"
> 
> Thanks
> 
> 
> -----Original Message-----
> From: Jonathan Marsh [mailto:jmarsh@microsoft.com]
> Sent: Wednesday, May 26, 2004 2:35 PM
> To: Sharon Hu; www-ws-desc@w3.org
> Subject: RE: spelling error
> 
> 
> This has been fixed in the latest draft, see
> http://www.w3.org/TR/wsdl20/.
> 
> > -----Original Message-----
> > From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]
> On
> > Behalf Of Sharon Hu
> > Sent: Wednesday, May 19, 2004 11:56 AM
> > To: www-ws-desc@w3.org
> > Subject: spelling error
> >
> >
> >
> >
> >
> > Hi,
> > I am reading Web Services Description Language (WSDL) Version 2.0
Part
> 1:
> > Core Language http://www.w3.org/TR/2003/WD-wsdl20-20031110/ and
found
> a
> > spelling error.
> > In 2.1.1 The Definitions Component
> > "Each WSDL or type/element component MUST be uniquely identified by
> its
> > qualified name. That is, if two distinct components of the same kind
> > (Interface, Binding etc.) are in the same target namespace, then
their
> > QNames MUST be unique. However, different kids of components (e.g.,
an
> > Interface component and a Binding component) MAY have the same
QName.
> > Thus, QNames of components must be unique within the space of those
> > components in a given target namespace."
> > should it be "kinds"?
> > Thanks
> >
Received on Thursday, 27 May 2004 10:56:51 GMT

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