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:;%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"

However, Indicating an HTTP Binding shows:

  <binding >
    <http:binding methodDefault="xs:string"?
                  defaultTransferCoding="xs:string"? >

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.

Hugo Haas - W3C -

Received on Wednesday, 21 July 2004 07:14:00 UTC