On jeu, 2005-07-14 at 11:54 -0400, Elliotte Harold wrote:

> regardless, mixed content is not as uncommon or unexpected as many 
> people think. It is not an accident. It is not bad form. It is not 
> something to be avoided. It is the very natural way to express many 
> extremely common constructs when modeling information, including 
> so-called data-oriented applications (as if any information content were 
> not data). 

Well said! 

Unfortunately, most people tend to exclude any mixed content from
data-oriented applications and the grammar based schema languages
(including RELAX NG) include restrictions that makes it impossible to
restrict the values of the text nodes in mixed content (that's what I
have tried to explain in my RNG book:
http://books.xmlschemata.org/relaxng/relax-CHP-7-SECT-10.html).

It's a chicken/eggs problem: because data heads don't like mixed
content, their toolbox doesn't support it properly and because their
toolbox doesn't support it properly, they don't like mixed content...

Eric  

-- 
Carnet web :
           http://eric.van-der-vlist.com/blog?t=category&a=Fran%C3%A7ais
------------------------------------------------------------------------
Eric van der Vlist       http://xmlfr.org            http://dyomedea.com
(ISO) RELAX NG   ISBN:0-596-00421-4 http://oreilly.com/catalog/relax
(W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema
------------------------------------------------------------------------