RE: [DM] BEA_006

> Data Model: request for simplification
> 
> What is the rationale for supporting functionality beyond
> the Infoset: e.g. documents with empty content, with multiple 
> element children, etc ?
> 
> Is this rationale serious enough to overcome all the 
> serialization and application communication difficulties that 
> derive from there ?
> 

Many of these considerations apply because the Data Model has more than
one customer: it is also used by XSLT.

Historically, I think the main reason XSLT 1.0 did it like this was a
philosophy of avoiding dynamic errors wherever possible. We can argue
about the merits of this philosophy (there are arguments on both sides)
but there is little point, because we can't change these decisions
retrospectively.

Michael Kay