Lists Home |
Date Index |
Amelia A Lewis <email@example.com> writes:
> I'm currently investigating what it would take to make a generic SAX filter
> that would effectively act as a macro processor (this only handles the
> processing instruction in instance document case, though; the use of entity
> definitions in schema documents isn't addressed).
SAX defines a skippedEntity(String name) callback, so the filter
itself would be quite simple: you write an implementation of that
method that swallows the original callback, looks the entity up by
name and reports its content downstream.
The question is what do the different parsers think of WF constraints
that have been brought up in this thread - you will never get a
skippedEntity if the parser decides that this entity reference
represents a fatal error.
Elections only count as free and trials as fair if you can lose money
betting on the outcome.