RE: URI comparison

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

The Working Group agreed that the slash is needed on SOAP 1.2 binding URIs,
and to add one to the SOAP 1.1 binding URI to keep them similar.  This has
been incorporated into the SOAP 1.1 binding, the Primer, and the Test Suite.

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/#CR077

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 Youenn Fablet
> Sent: Monday, July 24, 2006 1:25 AM
> To: www-ws-desc@w3.org
> Cc: Arthur Ryman
> Subject: URI comparison
> 
> 
> Hi all,
> 
> I dug into some of the WSDL documents for which our wsdl parser does not
> match with the baseline.
> Some differences are due to the use in some documents (Echo-1G for
> instance) of the following binding URI:
>        wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"
> Our parser recognizes the use of the SOAP1.2 HTTP binding with the
> following URI:
>        wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP/"
> The sole difference is the last character '/'.
> We currently use a simple character-by-character comparison to match the
> URI against the SOAP1.2 binding URI, as defined IIRC somewhere in part 1.
> Arthur, do you know how Woden is handling URI processing and comparison ?
> Regards,
>     Youenn
>

Received on Tuesday, 31 October 2006 01:00:17 UTC