Re: HTTP binding mismatch and identification missing

+1 .. glad that you'll bring the http binding up-to-date.

Sanjiva.

----- Original Message ----- 
From: "Asir Vedamuthu" <asirv@webmethods.com>
To: "'Hugo Haas'" <hugo@w3.org>; <www-ws-desc@w3.org>; "David Orchard"
<dorchard@bea.com>
Sent: Wednesday, July 21, 2004 6:23 PM
Subject: RE: HTTP binding mismatch and identification missing


>
> Hugo,
>
> > Does everybody agree before I start making
> > lots of changes in the Part 3?
>
> +1 to these changes. I have the same set of issues in my notes. I did not
> post them because I wasn't sure if part 3 was ready for WG review. BTW,
when
> will part 3 be ready for WG review?
>
> One additional item is,
> Component property names: I prefer
> {http location} instead of {location}
> {http cookies} instead of {cookies}
> ...
>
> Asir
>
> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
> Behalf Of Hugo Haas
> Sent: Wednesday, July 21, 2004 7:14 AM
> To: www-ws-desc@w3.org; David Orchard
> Subject: HTTP binding mismatch and identification missing
>
>
> All, and Dave in particular,
>
> I have found two important issues with regards to the HTTP binding,
> but which can both be fixed easily.
>
> First, the HTTP binding doesn't set the {type} property of binding. I
> have fixed this already:
>
>
>
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20-bindings.html
> ?rev=1.44&content-type=text/html;%20charset=utf-8#http-binding-id
>
> Second, I have discovered a fairly big mismatch in the HTTP Binding.
> Fortunately, I think it's just an editorial mistake that should be
> fixable easily, but involves quite a lot of editing.
>
> The HTTP Syntax Summary shows, among other things:
>
>   <binding name="xs:NCName" interface="xs:QName"? type="xs:anyURI"
>            http:methodDefault="xs:string"?
>            http:cookies="xs:boolean"?
>            http:version="xs:string"?
>            http:defaultTransferCoding="xs:string"?
>
> However, Indicating an HTTP Binding shows:
>
>   <binding >
>     <http:binding methodDefault="xs:string"?
>                   cookies="xs:boolean"?
>                   version="xs:string"?
>                   defaultTransferCoding="xs:string"? >
>   </binding>
>
> which is obviously different.
>
> There is such a mismatch for all the components.
>
> I do believe that the first way (http:PROPERTY attributes) is the way
> to go and not the second one (http:COMPONENT elements). It actually
> matches what the SOAP binding does:
>
>   <binding  name="xs:NCName" interface="xs:QName"? type="xs:anyURI"
>             wsoap:protocol="xs:anyURI" >
>
> Does everybody agree before I start making lots of changes in the
> Part 3?
>
> Also, as a final comment, http:authenticationType and
> http:authenticationRealm go an endpoint and not service per our May
> F2F[1]. I will fix this.
>
>   1. http://lists.w3.org/Archives/Public/www-ws-desc/2004May/0074.html
> -- 
> Hugo Haas - W3C
> mailto:hugo@w3.org - http://www.w3.org/People/Hugo/

Received on Wednesday, 21 July 2004 11:52:01 UTC