Scott --
We use Xalan in quite a few non-presentation oriented scenarios. The idea
that "XSLT is a tree transformation language" is not my idea, but it's the
truth -- XML (SAX or DOM) is really only an "interface" for accessing
hierarchical information, and XSLT is a way to interpolate between those
interfaces.
With that in mind, we are using XalanJ2 (coupled with a parser description
language that creates SAX event drivers for non-XML files and a serializer
description language, also SAX-based) to transform EDI->EDI (X.12, EDIFACT,
etc.), HL7->HL7 (v2.x to v2.x, v2 to v3, etc.), and we're starting to work
with SWIFT. For the EDI-EDI, applications, throughput is great: ~5M typical
messages per day on a desktop PC. To put that in perspective, a typical
large hospital will handle thousands of messages per day. A medium-sized
VAN will handle 1M message per day. Considering the variety of tools, IDEs,
mappers, etc. -- XSLT is more than adequate.
The only reason I can think of to use anything else is a bad case of "NIH".
Paul Brown
FiveSight Technologies, Inc.
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 05, 2001 4:09 PM
> To: [EMAIL PROTECTED]
> Subject: Need non-presentation-oriented usage scenarios
>
>
> I am looking for non-presentation oriented usage scenarios for XSLT and
> Xalan. If you have one, and would be willing to take the time to write it
> up, it would be much appreciated... send either privately to me or the
> list.
>
> Thanks!
>
> -scott
>
>
>
>
