- From: Marc Hadley <marc.hadley@sun.com>
- Date: Thu, 14 Nov 2002 08:28:09 -0500
- To: "Jean-Jacques Moreau" <moreau@crf.canon.fr>
- Cc: XMLP Public <xml-dist-app@w3.org>, WSD Public <www-ws-desc@w3.org>
Interesting question. I think its probably clear that there's nothing we can do to prevent a SOAP node from receiving a message containing an unknown header block (irrespective of whether a module specification for the header block exists or not). Marc. On Thursday, Nov 14, 2002, at 03:46 US/Eastern, Jean-Jacques Moreau wrote: > > Dear all, > > An interesting question/issue has come up during yesterday's WSD > face-to-face: can SOAP 1.2 header blocks exist independently from SOAP > 1.2 modules? I.e. can you define a new header block without writing > down on paper the corresponding module specification *and* without > assigning a new module URI? > > I think the spec is at best unclear on this topic. Beyond > clarification, the real question is: as a WG, how do we feel about > this issue? Since we have taken all the trouble of describing modules > in a normative fashion, probably for a good reason, do we still want > allow "independent" header blocks, or do we think they should be > discouraged? > > I am cc'eing ws-desc since the WSD WG is interested in this topic, as > part of its work of describing SOAP features in WSDL 1.2. However, I > am not raising this issue on behalf of the WSD WG (although the WSD > might raise this issue itself in the future). > > Please remove xmlp-comments from any further discussion. > > Cheers, > > Jean-Jacques. > > > -- Marc Hadley <marc.hadley@sun.com> Web Technologies and Standards, Sun Microsystems.
Received on Thursday, 14 November 2002 08:28:02 UTC