W3C home > Mailing lists > Public > xml-dist-app@w3.org > November 2001

Re: Proposed resolution of issue 101: relationship between header and body blocks

From: Jean-Jacques Moreau <moreau@crf.canon.fr>
Date: Thu, 22 Nov 2001 16:52:44 +0100
Message-ID: <3BFD1F4C.4B972157@crf.canon.fr>
To: Noah_Mendelsohn@lotus.com, dug@us.ibm.com, frystyk@microsoft.com, xml-dist-app@w3.org, ruellan@crf.canon.fr
[Ok, no reaction, so let's try this again with a concrete
example.]

In the following example, the "next" SOAP node will fault if it
does not understand "xx:user":
  <envelope>
    <header>
      <xx:user
          mU="true"
          href="#example.org"
          actor="next"><name>fred</name></xx:user>
      <yy:company
          id="example.org"
          actor="none"><name>Example Org</name></yy:company>
    </header>
    <body>...</>
  </envelope>

In this other example, should the "next" SOAP node fault if it
does not understand "yy:company"?
  <envelope>
    <header>
      <xx:user
          href="#example.org"
          actor="next"><name>fred</name></xx:user>
      <yy:company
          mU="true"
          id="example.org"
          actor="none"><name>Example Org</name></yy:company>
    </header>
    <body>...</>
  </envelope>

... probably... after all, the second block is implicitely
targetted at the next SOAP node, and is not understood by that
node. But is this not currently disallowed by the processing
model (section 2.3 targetting + section 2.5 processing model,
although a reading of section 2.5 alone my lead to a different
conclusion)?

Jean-Jacques.
Received on Thursday, 22 November 2001 10:53:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:05 GMT