xml-dev - Re: SAX2 Lexical Handler Suggestions

[Chris Pratt <chris@planetpratt.com>]

How does XSL deal with these problems?  There's no control over entity
references in XSL?  I am basically doing what XSL enables except that I'm
caching it in between.  I don't understand how XSL is able to do this using
a SAX parser if the rest of us mortals aren't?
  (*Chris*)

----- Original Message -----
From: "David Megginson" <david@megginson.com>
To: "XML-DEV" <xml-dev@lists.xml.org>
Sent: Wednesday, July 12, 2000 11:37 AM
Subject: Re: SAX2 Lexical Handler Suggestions


> Chris Pratt wrote:
>
> > Our system is a web based authoring system
> > that allows the XHTML/AML (our own markup extensions) to be parsed once
and
> > held in memory in an executable tree so that when each request comes in
for
> > that page a completely new HTML document can be created from the
executable
> > XHTML template by simply running the chain.  If all the attributes
(which we
> > use as Dynamic macros) are silently replaced by the parser, we have no
way
> > of Dynamically inserting the proper macro value into the generated HTML.
>
> If I'm reading correctly (assuming 'entities' for 'attributes'), I don't
> think that this is a very good approach.  Instead of
>
>   <p>xxxx &myDynamicMacro; xxx</p>
>
> I'd recommend something like
>
>   <p>xxxx <aml:dynamicMacro a="bbbb"/> xxx</p>
>
> or even
>
>   <p>xxxx <?aml macro a="bbb"?> xxx</p>
>
> They do the same thing, but play nicely with existing tools (i.e.
> someone could easily do the substitution with XSL if they wanted to) and
> don't complicate your data model as badly.
>
>
> All the best,
>
>
> David
>
> --
> David Megginson                 david@megginson.com
>            http://www.megginson.com/
>