SOAP and HTTP bindings: Editorial reorganization for defaults

Defaults in the bindings are inconsistently defined.

The bindings have:
- a default binding rules section:
  5. WSDL SOAP Binding Extension
     5.3 Default Binding Rules
  6. WSDL HTTP Binding Extension
     6.3 Default Binding Rules
- sections for other defaults:
     5.6 Specifying the Default SOAP MEP
     6.5 Specifying the Default HTTP Method
- other sections defining their own defaults:
     6.6 Binding Operations
       (defines queryParameterSeparatorDefault)
     6.10 Specifying the Transfer Coding
       (defines transferCodingDefault)

I would like to propose to have each @foobarDefault consistently
defined in its own subsection under 5.3 Default Binding Rules and 6.3
Default Binding Rules, or have them consistently defined in the
section where they're used for determining the value of a property
(like sections 6.6 or 6.10).

I prefer those two proposed solutions to having them as subsections of
the the binding definition (like 5.6 and 6.5) as I believe that it
gives as much important to setting a default, which does not directly
impact the component, as to say binding an operation, which is much
more substantial.

-- 
Hugo Haas - W3C
mailto:hugo@w3.org - http://www.w3.org/People/Hugo/