Re: Issue 25 Proposal

I'm curious as to what manner of discomfort? Header blocks
could be considered "pre-processing" for the Body and Trailer
blocks "post-processing" of the Body. 

For instance, if I wanted to have the message signed
after processing of the Body, a Trailer might be much
more appropriate than a Header block which needed to
be deferred until after the Body (and/or other Headers)
were processed.

I think that we should strive for simplification. Adding
in (or simply clarifying in) the ability to stick
"stuff" in the Envelope after the Body element without
providing any processing guidance as has been provided
for Headers seems to me to be arbitrary and would lead to
confusion not increased clarity.

Cheers,

Chris
Jean-Jacques Moreau wrote:
> 
> christopher ferris wrote:
> 
> > I am curious as to why the trailers aren't
> > XMLP Blocks?
> 
> Making trailers ordinary blocks (and hence having a unified processing
> model) would indeed simplify the spec, remove a number of ambiguities, and
> enable us to build simpler (and more maintainable) implementations. However,
> this option does seem to cause some incomfort...
> 
> Jean-Jacques.