overrestrictive constrainsts for "SOAP header block" and "SOAP Body child Element"?

• From: adam souzis <adam@kinecta.com>
• Date: Fri, 19 Jul 2002 12:14:54 -0700
• To: xmlp-comments@w3.org
• Message-Id: <4.2.0.58.20020719115131.03a36090@mail.kinecta.com>

Unless I'm missing something, the spec appears to disallow children 
elements for the child element information items of both the SOAP Header 
and the SOAP Body.

See:
5.2.1 SOAP header block

5.3.1 SOAP Body child Element

Both sections only state that they "MAY have any number of character 
information item children" but there is no mention allowing element 
information item children.

Perhaps you intended to define the "SOAP header block" and "SOAP Body child 
Element" as descendents of the SOAP Header and the SOAP Body element 
information items respectively and not as just the children?

As it stands now most of examples given in the spec are invalid, for 
example, Example 1 in Part 1, because n:priority is a child element of the 
"SOAP header block" n:alertcontrol and because m:msg is a child element of 
the "SOAP Body child Element" m:alert.

If the authors did indeed intend this restriction and these are indeed 
invalid examples, then I'm sure I would not be alone in protesting this as 
overly restrictive constraints.

regards,
adam

Received on Friday, 19 July 2002 15:15:01 UTC