>I spoke to Henrik today, and he thinks it is better to
>overload the block tag. Some blocks would be purely
>declarative -- this is a vcard, for example. Other
>(actionable) blocks would have more processing-oriented tags
>that the processor would bind to a handler. These tags would
>either surround a declarative block, or possibly point to a
>declarative block, particularly if the block needed to be
>processed in multiple ways.
The role of a block can even change depending on the semantics of other
blocks pointing to it. This is a different way of saying that how one
uses some data (a block) often is a function of the user rather than of
the data.
Looking at the example in the SOAP DSig W3C Note [1], it shows an
example of one block signing another block. The block being signed has
processing associated with it - it is requesting a stock price. To the
signing block, however, it is just a bag of angle brackets.
Figuring out how modules relate processing wise of course gets us into
the other discussion that we have had on ordering but even though these
discussions are related I think it would be nice to keep them separate.
Henrik
[1] http://www.w3.org/TR/SOAP-dsig/#ex