Lists Home |
Date Index |
- From: "Simon St.Laurent" <email@example.com>
- To: "XML Developers' List" <firstname.lastname@example.org>
- Date: Fri, 12 Mar 1999 10:37:55 -0500
After a few months of intense busy-ness (and business), plus a trip to
XTech that I'm still recovering from, I'm finally catching up to ModSAX.
Printed it all out, looked it all over, and mostly I'm very pleased. I
think it'll make implementing my Layered Model proposal as a a Layered
Parser much easier overall.
One key thing is missing at this stage, and that's a feature.
At 08:16 PM 3/9/99 -0500, David Megginson wrote:
>Here's my revised version of the core feature list, based on recent
>ModSAX Core Features
> Validate (true) or don't validate (false).
> Expand external general entities (true) or don't expand (false).
> Expand external parameter entities (true) or don't expand (false).
> Preprocess namespaces (true) or don't preprocess (false). See also
> the http://xml.org/sax/properties/namespace-sep property.
> Ensure that all consecutive text is returned in a single callback to
> DocumentHandler.characters or DocumentHandler.ignorableWhitespace
> (true) or explicitly do not require it (false).
Requires the parser to load the external subset of the DTD and process
it. (External parameter entities remain a separate issue referenced by a
This is critically important for attribute defaulting, which makes things
like XLink much much simpler. At one point I switched parsers, only to
find that my attribute values in the external subset had all disappeared.
I promptly jumped back. The spec (5.1) allows non-validating parsers to
skip the external subset; I'd very much like to have a way to tell the
parser not to skip it, or at least know that they are in fact being skipped.
XML: A Primer / Building XML Applications (April)
Sharing Bandwidth / Cookies
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)