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

I am incomfortable with this. As far as an intermediary is concerned, the
"main purpose" of the message is _not_ the body. If we are talking about
simple intermediaries, this may not matter much; but it does matter once we
start talking about more elaborate intermediaries, intermediaries which may
perform processing of equal importance to that of the final receiver.

Besides, why just restrict the Body element to at most one child, if we then
say that that one child may have multiple children? Are we not being
somewhat inconsistent with ourselves?


Henrik Frystyk Nielsen wrote:

> IMO, a simple way of putting it is to say that the <body> is defined as
> a well-known block. Just as any other block, it has an open content
> model and can contain as many immediate child elements as it wants.
> [...]
> As part of the guidelines for how to *use* the body we indicate that
> this is where the "main purpose" of the message goes.
> Henrik Frystyk Nielsen

Received on Thursday, 15 November 2001 04:59:23 UTC