Re: Content-free Header and Body elements

On Friday, May 16, 2003, at 11:10 US/Eastern, 
noah_mendelsohn@us.ibm.com wrote:
> Bottom line, this is not worth a delay of weeks
> or months.  It is worth fixing ASAP.  Agreed?
>
Very much so. Fix it if we can do so without going back to WD, leave as 
is if not.

Marc.

>
>
> Rich Salz <rsalz@datapower.com>
> Sent by: xml-dist-app-request@w3.org
> 05/16/2003 11:02 AM
>
>
>         To:     Martin Gudgin <mgudgin@microsoft.com>
>         cc:     "Marc.Hadley@Sun.COM" <Marc.Hadley@Sun.COM>, 
> Christopher B Ferris
> <chrisfer@us.ibm.com>, "xml-dist-app@w3.org" <xml-dist-app@w3.org>, 
> (bcc:
> Noah Mendelsohn/Cambridge/IBM)
>         Subject:        RE: Content-free Header and Body elements
>
>
>
>> I think this text nails it.
>
> Not quite.
>
>>> 3. Element information items for additional header blocks MAY
>>> be added to the [children] property of the SOAP Header
>>> element information item as detailed in 2.7.2 SOAP Forwarding
>>> Intermediaries. In this case, a SOAP Header element
>>> information item MAY be added if not already present.
>
> [children] is an ordered list, right?  So the Header EII "may be 
> inserted
> before the Body EII" is probably what it should say.
>
>         /r$
> --
> Rich Salz                     Chief Security Architect
> DataPower Technology          http://www.datapower.com
> XS40 XML Security Gateway     
> http://www.datapower.com/products/xs40.html
>
>
>
>
>
--
Marc Hadley <marc.hadley@sun.com>
Web Technologies and Standards, Sun Microsystems.

Received on Friday, 16 May 2003 13:25:57 UTC