Hans,
Ah, well, my simple example is a stylesheet process I've been working on
that must, after transformation, create SGML output....
To do this, not only do I have to do some of the usual tricks (force empty
elements into start-tag and end-tag notation, etc.), but also pay special
attention to the serializing. Since the downstream processes aren't
guaranteed to hack UTF-8, there's a character mapping stage including a
resort to disable-output-escaping to force the correct representations of
characters (the SGML wants named entities).
Stage two could be rolled into stage one, but it doesn't have to be.
Essentially their tasks are very different: the first is a true transform,
the second just a post-process that happens to be implemented using an XSLT
engine. They involve different dependencies: the first is Pure XSLT, the
second relies on a backend serializer supporting certain features like
plain ASCII output (and d-o-e). They also involve separate maintenance
issues (e.g. the character mapping in the second phase has to be extensible).
If at some point the need to create SGML goes away, the second process can
simply be abandoned. Since in this case there's no benefit to rolling the
two processes together (performance or other constraints not being an issue
in this case), we're leaving them separate.
At 07:03 AM 11/22/2002, you wrote:
Thank you all for your input making this forum possible.
Sure! but all I do is hang around giving my opinions: it's Tommie who does
the real work at mulberrytech. :->
Cheers,
Wendell
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list