[
Lists Home |
Date Index |
Thread Index
]
At 5:48 PM -0500 11/1/02, Mike Champion wrote:
>It would seem to me that ALL the "syntax sugar preprocessing" --
>entity resolution and substitution, CDATA section processing, attribute
>default value insertion, maybe XInclude resolution -- belongs
>in some preprocessor step.
XInclude resolution is different because it's not syntax sugar. Most
importantly it's based on elements and the infoset rather than low
level syntax. You need to parse the document to produce the infoset
before you can resolve the XIncludes.
Beyond that the problem for a preprocessor step is that what's legal
to be preprocessed depends on where it shows up. For instance
<name>Randy;</name> is well-formed whereas
<name>Randy;</name> is not. I think you'd pretty much need
a full-fledged parser in the preprocessor.
--
+-----------------------+------------------------+-------------------+
| Elliotte Rusty Harold | elharo@metalab.unc.edu | Writer/Programmer |
+-----------------------+------------------------+-------------------+
| XML in a Nutshell, 2nd Edition (O'Reilly, 2002) |
| http://www.cafeconleche.org/books/xian2/ |
| http://www.amazon.com/exec/obidos/ISBN%3D0596002920/cafeaulaitA/ |
+----------------------------------+---------------------------------+
| Read Cafe au Lait for Java News: http://www.cafeaulait.org/ |
| Read Cafe con Leche for XML News: http://www.cafeconleche.org/ |
+----------------------------------+---------------------------------+
|