One of the problems facing B2B developers with XSLT is that the XML instance
needs to run 'in-memory' real or virtual memory because XSLT doesn't have
scope control as a tool based on input source - making translation of some
B2B type messages difficult (slow) if not impossible.
- Bruce
Ken,
Question on XSLT, I want to know if I have children, if I do I want to start
an HTML table structure, and if I don't have children, I simply want to
display some attribute information. How one know at the parent node this
information, or is this handled with flag variables on the first occurance
of the child? Hope this question makes sense.
----- Original Message -----
From: "David RR Webber" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, July 03, 2000 6:01 PM
Subject: Re: Are there really any benefits?.
Message text written by "G. Ken Holman"
>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
<<<<<<<<<<<<<<<<<<<<
Ken,
I know you a big advocate of XSLT and you have authored much
on training and learning XSLT. Good to see the other side of the
coin expoused.
Anyway - part of this is as you say a 'gut thing', and just like
BetaMax and VHS, the market will ultimately decide.
I would stand by my assertion that XSLT is a programmer toolset,
and this is based on extensive XML/XSLT teaching, where
non-technical audiences used to using EDI translation mapper
technologies ask the question 'and we are supposed to do what with
this now?'.
There are already many good alternatives in the area of
B2B information exchanges, and I firmly see that people will
vote based on business applicability and need.
This is not a bad thing! Also I would expect solutions based on
ebXML compliant technologies to more nearly match B2B
information needs, than something like XSLT - which just
because you add 'T' to the name, does not fundamentally
alter that fact that the heritage is from markup stylesheet land
which is a whole different mindset to EDI, code and element,
and business information interchanges.
DW.
------ 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
