Message text written by "G. Ken Holman"
>if the
information encoded is richer than the markup used to capture the encoding,
then XSLT could be very difficult to use and one falls back on more
difficult imperative techniques (which would have been required anyway if
the markup were not sufficiently rich). When the document models are
designed to capture the information required for successful EDI
interchange, I would hope translation and mapping requirements would be
considered in deciding the analysis and modeling granularity of the
information.
<<<<<<<<<<<<<<<<
Ken,
Herein lies the rub. Over in markup land everything is a tree and
related to its DOM representation.
Over in EDI land everything is business functional based. As you
correctly noted - this audience is not very HTML literate. Actually
HTML is a very bad model - as it is much about presentation.
EDI - like XML - is generic markup. Unlike XML the DTD is not
sent with the information content, and unlike XML there are
right wicked (X12 - not EDIFACT) and ugly loop constructs.
Further more - as Rachel Foerster noted - the context of the
information is vital in determining use. XSL and XML are
weak in these areas and RDF right now just adds to the
confusion (although the recent Harvard work in this area
has some promise).
Help is just around the corner however in the ebXML spec's
on Repositories and Core components, and also concepts
I have been championing such as bizcodes.
Will be interesting to see the synergy unfold here in due
course over the next few months.
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
