[
Lists Home |
Date Index |
Thread Index
]
I like this proposal to the extent that I can ignore it. It does not
break existing parsers or tools. I'm not at all convinced that it's
necessary, but if someone else has a need and wants to use it in
their documents, it doesn't bother me.
I would be opposed to wiring this into any other specs though. For
instance, I don't think XSLT 2.0, Schemas 2.,0, or any other
recommendation should treat xml:orphanedChar any differently than
they treat any other element. In particular, they should not define
their behavior in terms of the strings that are left after the
xml:orphanedChar elements are replaced with the actual characters.
Schemas should not ignore this element. All processing of it should
be left to those who want to use this. It should be recognized for
what it is: an occasionally useful hack, but not a core part of XML.
That said, I suspect it needs a different prefix and a different
namespace. The xml prefix is inappropriate.
--
+-----------------------+------------------------+-------------------+
| Elliotte Rusty Harold | elharo@metalab.unc.edu | Writer/Programmer |
+-----------------------+------------------------+-------------------+
| The XML Bible, 2nd Edition (Hungry Minds, 2001) |
| http://www.cafeconleche.org/books/bible2/ |
| http://www.amazon.com/exec/obidos/ISBN=0764547607/cafeaulaitA/ |
+----------------------------------+---------------------------------+
| Read Cafe au Lait for Java News: http://www.cafeaulait.org/ |
| Read Cafe con Leche for XML News: http://www.cafeconleche.org/ |
+----------------------------------+---------------------------------+
|
