- From: Jacek Kopecky <jacek@systinet.com>
- Date: 19 Nov 2002 19:51:41 +0100
- To: Marc Hadley <marc.hadley@sun.com>
- Cc: XMLP Dist App <xml-dist-app@w3.org>
Marc,
how about our headers? Can they have encodingStyle, even though they are
defined without one? If we want to prohibit encodingStyle on them, the
list might grow too much. Unfortunately, I can't think of any other
viable way to say what we seem to mean. 8-|
Best regards,
Jacek Kopecky
Senior Architect, Systinet Corporation
http://www.systinet.com/
On Tue, 2002-11-19 at 16:30, Marc Hadley wrote:
>
> I think there's a minor problem with the current text that specifies
> where the encodingStyle attribute can go. The current text says:
>
> <current>
> The encodingStyle attribute information item MAY only appear on:
>
> 1. A SOAP header block (see 5.2.1 SOAP header block).
>
> 2. A child element information item of the SOAP Body element
> information item (see 5.3.1 SOAP Body child Element).
>
> 3. A child element information item of the SOAP Detail element
> information item (see 5.4.5.1 SOAP detail entry).
>
> 4. Any descendent of 1, 2, and 3 above.
> </current>
>
> A SOAP Fault can be a child of the SOAP Body, but I don't think we
> really intend to permit that. I propose we modify the text to read:
>
> <proposed>
> The encodingStyle attribute information item MAY only appear on:
>
> 1. A SOAP header block (see 5.2.1 SOAP header block).
>
> 2. A child element information item of the SOAP Body element
> information item (see 5.3.1 SOAP Body child Element) if that child is
> not a SOAP Fault element information item (see ref to Fault EII).
>
> 3. A child element information item of the SOAP Detail element
> information item (see 5.4.5.1 SOAP detail entry).
>
> 4. Any descendent of 1, 2, and 3 above.
> </proposed>
>
> Comments ?
>
> Marc.
>
> --
> Marc Hadley <marc.hadley@sun.com>
> Web Technologies and Standards, Sun Microsystems.
Received on Tuesday, 19 November 2002 13:51:43 UTC