Pavel Lepin wrote:
> The entire "one text node per element" idea just doesn't
> make much sense (in context of document markup, as opposed
> to data markup), unless for some inexplicable reason you
> want to stuff everything with default semantics into a
> span; and that doesn't even work, because of the way
> whitespace is handled in XHTML, and because of Gecko's
> peculiar idiosyncrasies where long text nodes in DOM are
> concerned. 

Agreed. Avoiding mixed content may make sense for specific applications, 
but (a) the proposed change doesn't do that, and (b) it really isn't 
either viable or necessary as a general rule of thumb.

XML tools handle text siblings with no trouble. If a specific 
application doesn't, then when you design the dedicated XML language 
which goes with that application you can consider whether the XML should 
reflect that limitation.

Note that the old argument for avoiding mixed content (that DTDs 
couldn't constrain the order of element children in mixed content) goes 
away when using schemas.

-- 
() ASCII Ribbon Campaign  | Joe Kesselman
/\ Stamp out HTML e-mail! | System architexture and kinetic poetry