Re: First Class Header Proposals

Hi Asir.

* Asir Vedamuthu <asirv@webmethods.com> [2005-02-07 05:01-0800]
> Attached docs are two variations of the First Class Header Proposal - A and
> B. There is one principal difference between these two proposals: A uses a
> set of element declarations and B uses a complex type definition to describe
> headers.
> 
> Hope, these docs, SOAP Header Blocks in WSDL [1] proposal, Headers Proposal
> V1.2 [2], and other AD feature issues [3][4] provide sufficient info to act
> on LC76d [5].

A couple of questions about the requiredness of the headers:

- why do we need a mechanism to disable header generation? It seems to
  me that either the binding supports headers, and then you should use
  them if you need to, or it doesn't, and then that's it. Why would
  one want to disable header generation for a particular binding?

- I don't understand the purpose of @required either; with your
  element/type declaration, couldn't you express this with minOccurs?

Cheers,

Hugo

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