Skip to Content.
Sympa Menu

xom-interest - Re: [XOM-interest] CDATA handling

xom-interest AT lists.ibiblio.org

Subject: XOM API for Processing XML with Java

List archive

Chronological Thread  
  • From: John Cowan <jcowan AT reutershealth.com>
  • To: elharo AT metalab.unc.edu (Elliotte Rusty Harold)
  • Cc: laurent.bihanic AT atosorigin.com (Laurent Bihanic), XOM-interest AT lists.ibiblio.org (XOM-interest)
  • Subject: Re: [XOM-interest] CDATA handling
  • Date: Thu, 19 Sep 2002 11:34:46 -0400 (EDT)

Elliotte Rusty Harold scripsit:

> The application of the first principle is obvious. The application of
> the second is based on my observation that lots of client code out
> there in the world today treats CDATA sections as some kind of
> special purpose container with structural significance rather than as
> just syntax sugar. I deliberately chose not to make this possible in
> XOM. I want to cause cognitive dissonance for developers using CDATA
> sections in this fashion so that they will reevaluate their approach
> and come to a better understanding of how they should and should not
> use CDATA.

Fair enough. For documents that are meant to be readable, though, it might
make sense for at least some whole elements (ones with embedded languages
like "script" or "style") to be output as CDATA sections. How about
methods Serializer.writeAsCDATA(Text|Element), which would not affect the core
model?

--
John Cowan jcowan AT reutershealth.com www.reutershealth.com
www.ccil.org/~cowan
Promises become binding when there is a meeting of the minds and consideration
is exchanged. So it was at King's Bench in common law England; so it was
under the common law in the American colonies; so it was through more than
two centuries of jurisprudence in this country; and so it is today.
--_Specht v. Netscape_




Archive powered by MHonArc 2.6.24.

Top of Page