At 00/07/03 00:52 -0400, David RR Webber wrote:
>Message text written by Richard Hayes
> >
>Modern computers systems need to parser information between ERP / CRM /
>MRP II / etc and it is far easier using a common language XSL. What
>will happen there will be a device probability software agent (bot) that
>learns any data format and automatically translates it into a usable
>formats.
><<<<<<<<<<<<
>
>Richard - there is only one major flaw in this concept!
>
>XSL is not the right tool!!
Wait a minute here ... XSLT (XSL Transformations) is used for translation,
XSL for style semantics. I'll assume Richard meant to reference XSLT and
not XSL since I think he is talking about vocabulary transformation. I
won't comment on the automation scenario he has described, I only want to
comment on the use of XSLT: I don't see why XSLT is not (necessarily) the
right tool to parse and translate XML derived from different systems.
XSLT is not useful (and shouldn't be promoted as being so) for conversion
from non-XML to XML (as would, say, Omnimark) ... but if Richard is talking
about translation between instances of XML vocabularies, then XSLT can be
very useful.
>XSL is a style language, it is being
>pressed into service as a business information transformation
>toolset. It is poorly suited for the role.
I unreservedly disagree that XSLT is categorically inappropriate for XML
instance vocabulary transformation ... it is very appropriate in many areas
and I anticipate its wide acceptance in EDI-related applications utilizing XML.
For example: an XSLT processor can even play a role as the front-end to an
application adapting to XML inputs with far greater flexibility than using
just an XML processor as a front-end.
>Fortunately people (including the W3C!) are working on
>successor and better equipped tools.
>
>Message: don't bet the farm on XSL, even for forms,( see xhtml, XForm
>are showing better ways).
Now are you talking XSL formatting or XSL transformation? Why are you
bringing forms into this discussion? I thought Richard was talking about
information transformation.
>Your example above also pre-supposes that all XSL processors
>give you consistent results. This is simply not the case, only
>talked about right now.
Again I disagree! Many processors available *today* are
interchangable. Vendors are working towards compliance. I chair the OASIS
XSLT Conformance Technical Committee and there is demand in the industry
for a conformance test suite from our efforts.
>XSL is a complex tool, and from complexity
>comes several side-effects that limit its usefulness.
Complexity is in the eye of the beholder. Such a blanket statement is
unfair and judgmental.
>However, used sparingly, as it was designed to be, XSL can deliver
>good results, albeit at a cost in programming time.
XSLT's "transformation by example" paradigm does not require programming
knowledge to be used successfully. It was designed to be usable by
non-programmers.
To learn more about XSL, XSLT and XPath, you can participate in:
http://www.mulberrytech.com/xsl/xsl-list
There is also an *excellent* FAQ at:
http://www.dpawson.co.uk
I find unqualified and unsubstantiated claims of inappropriateness are
difficult to defend, so I hope the reader will make their own decision
about how easy or difficult XSLT is to use. There are a number of free
resources noted in the FAQ where one can learn more. I've released on our
web site a free download excerpt (covering the context and introduction to
XSLT) of my own book.
I hope this helps.
.................. Ken
--
G. Ken Holman mailto:[EMAIL PROTECTED]
Crane Softwrights Ltd. http://www.CraneSoftwrights.com/e/
Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (Fax:-0995)
Web site: XSL/XML/DSSSL/SGML services, training, libraries, products.
Book: Practical Transformation Using XSLT and XPath ISBN1-894049-04-7
Next instructor-led training: 2000-09-19/20,2000-10-03,2000-10-04,
- 2000-10-05,2000-11-13,2001-01-27
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
