• To: reinhard gantar <gantar@u...>, xml-dev@l...
• Subject: Re: Escaping XML? Flattening the parse tree?
• From: Elliotte Rusty Harold <elharo@m...>
• Date: Wed, 13 Aug 2003 16:43:04 -0400
• In-reply-to: <3F3A9498.4050405@u...>
• References: <3F3A9498.4050405@u...>

At 9:42 PM +0200 8/13/03, reinhard gantar wrote:
>Dear XMLers,
>
>XML might contain .HTML that is not supposed to be processed
>as XML. It should be treated "as is", i.e. a string of
>characters. Real-World content management systems based
>on XML (import/export, like OpenCMS) store items like title,
>introduction, bodytext, etc. and mark such tidbits up in XML.
>

No, what you ask for is completely contrary to the design and nature 
of XML. It's all parsed. If you really can't live with that, (and not 
everyone can though many more people can than think they can) then 
XML is not a suitable envelope for your data. You should investigate 
other, non-XML solutions.  Some interesting work is being done with 
multipart MIME messages that might fit your needs better.
-- 

   Elliotte Rusty Harold
   elharo@m...
   Processing XML with Java (Addison-Wesley, 2002)
   http://www.cafeconleche.org/books/xmljava
   http://www.amazon.com/exec/obidos/ISBN%3D0201771861/cafeaulaitA

• References:
  • Escaping XML? Flattening the parse tree?
    • From: reinhard gantar <gantar@u...>

• Prev by Date: RE: Symbol Grounding and Running Code: Is XML Really E xtensible?
• Next by Date: Re: Data vs. Document-Oriented XML - Better Terms? (Was Re: XML database enviroment using PostgreSQL)
• Previous by thread: Escaping XML? Flattening the parse tree?
• Next by thread: Re: Escaping XML? Flattening the parse tree?
• Index(es):
  • Date
  • Thread