RE: service and binding name shown as QNames in example - should be NCNames

Thanks for your comment.  The WS Description Working Group tracked this
issue as a CR061 [1].

The Working Group removed the extraneous prefixes, and shown in the latest
editor's draft [2].

Unless you let us know otherwise by the end of October, we will assume you
agree with the resolution of this issue.

[1] http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR061
[2]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?content-
type=text/html;%20charset=utf-8#Feature_composition_model_example

Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com
 

> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
> Behalf Of Jeremy Hughes
> Sent: Monday, June 05, 2006 2:52 AM
> To: www-ws-desc@w3.org
> Subject: service and binding name shown as QNames in example - should be
> NCNames
> 
> 
> The XML representation of the service component in part 1 [1]
> describes the service name attribute as being of type xs:NCName.
> However, example WSDL elsewhere in part 1 [2] has a service element
> as:
> 
>   <service name="ns1:BankService"
>            interface="tns:Bank">
> 
> i.e. with name attribute as a QName. I believe the service name should
> be simply "BankService" without qualification.
> 
> The binding name in the same example suffers a similar problem.
> 
> [1]
> http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?conten
> t-type=text/html;%20charset=utf-8#Service_XMLRep
> [2]
> http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?conten
> t-type=text/html;%20charset=utf-8#Feature_composition_model_example
> 
> Many thanks,
> Jeremy
>

Received on Monday, 16 October 2006 17:42:06 UTC