Yes.  You are right.  I had forgotten that clause.  Section 4.2.1 does
indeed say:

"A SOAP application generating a SOAP message SHOULD only use the SOAP
Header attributes on immediate child elements of the SOAP Header element.
The recipient of a SOAP message MUST ignore all SOAP Header attributes that
are not applied to an immediate child element of the SOAP Header element."

Thanks for catching this.

----- Original Message -----
From: <gdaniels@[...]..> 
To: <soapbuilders@[...].com> 
Sent: Sunday, April 01, 2001 10:27 PM
Subject: [soapbuilders] Re: The ebXML use of SOAP-ENV:mustUnderstand


--- In soapbuilders@[...]., "Andrew Layman" <yahoo@[...]..>  wrote:
>  The SOAP 1.1 specification defines the meaning and correct
processing of
>  SOAP-ENV:mustUnderstand when it appears on immediate child elements
of the
>  SOAP-ENV:Header element.  However, it says nothing one way or the
other
>  about the use of this attribute on more deeply nested elements.
This was
>  intentional: it leaves it up to the definer of the header elements
to choose
>  whether SOAP-ENV:mustUnderstand is allowed or not for them.  (One
expects
>  that, if it is allowed, it has the same meaning.)

Andrew, doesn't this interpretation conflict with the following
sentence from section 4.2.1:

"The recipient of a SOAP message MUST ignore all SOAP Header
attributes that are not applied to an immediate child element of the
SOAP Header element."

This seems to say that even though it isn't prohibited to put the
header attributes (actor, mustUnderstand) elsewhere, receiving SOAP
nodes should ignore them if they appear anywhere other than as an
immediate child of the Header element....

?

--Glen

P.S.  Rest of thread elided for brevity.