Re: Fw: [soapbuilders] NMTokens, NCNames, PortTypes, and Bindings.

Hi Sanjiva,

The schema at http://schemas.xmlsoap.org/wsdl/ seems to have rectified this
though...

Regards, Prasad

-------- Original Message --------
Subject: Re: [soapbuilders] NMTokens, NCNames, PortTypes, and Bindings.
Date: Tue, 11 Jun 2002 10:32:01 +0600
From: "Sanjiva Weerawarana" <sanjiva@watson.ibm.com>
Reply-To: soapbuilders@yahoogroups.com
To: <soapbuilders@yahoogroups.com>
References: <005b01c210b1$386f9dd0$6801a8c0@GAIA.THEMINDELECTRIC.NET>

This is definitely a bug in WSDL 1.1. We (now I'm speaking as
a member of the W3C WS-Desc WG) will fix it in WSDL 1.2.

Sanjiva.

----- Original Message -----
From: "Wes Moulder" <wes@themindelectric.com>
To: <soapbuilders@yahoogroups.com>
Sent: Tuesday, June 11, 2002 1:01 AM
Subject: [soapbuilders] NMTokens, NCNames, PortTypes, and Bindings.


> Oh my!
>
> >From the soapbuilders conference, one bug came up with the WebMethods
> guys, and I wanted some clarification of understanding.
> The WSDL spec says that a PortType's name attribute is an nmtoken, but
> the Binding refers to this via a QName, which we have always understood
> to be a combination of the targetNamespace of the WSDL, and the name of
> the PortType.  If the PortType's name attribute is an nmtoken, it's
> allowed to have characters (such as ":") which are illegal for an
> NCName.
>
> This same issue holds for binding and wsdl:port in the service
> description.
>
> The issue is, all over the place in the WSDL spec, it uses nmtokens for
> name attributes, which can result in invalid qnames for types that refer
> to them.  Is this an inconsistency in the WSDL spec, an inconsistency in
> my understanding of the issues, or a "feature"?
>
> Comments appreciated,
> --Wes
>

Received on Tuesday, 11 June 2002 04:40:01 UTC