This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: xslt and edi question


about 1 yr ago, i implemented a system that does edi transforms both ways

some things u will find

a) look at eagle http://www.mendelson-e-c.com/eagle/doc/Install.html
though this is woefully out of date, the java transforms work well though,
and some of the work of defining an edi.xml format has been done and takes
care of the extraction of edi messages into xml ( though i must say its not
so easy to setup )

b) if u are transforming edi format messages, these are flat text files, its
much easier in xslt to transform from xml to edi, bear this in mind when
designing the architecture of your system ( i tend to fling everything
around in xml, then generate edi if and when as final transport format)

c) break down your generation or extraction of edi messages into 2 stages, u
will find this much easier, then trying to do everything in 1 stage ( not
necc for processing speeds but for gaining the benefits of human readability
in your final xml format, which of course is the main problem with EDI
messages )

d) once u have your home grown format xml ( purchase order, etc ), and your
edi.xml its simple to use any of the number of mapping tools out there that
auto generate xslt ( look at www.capeclear.com, or of course M$ has
something or other... ) which takes care of your xml->edi.xml concerns.

good luck

feel free to post to me personally if things get silly.

cheers, jim fuller

----- Original Message -----
From: "Kuhn, Allen" <Akuhn@enporion.com>
To: <xsl-list@lists.mulberrytech.com>
Sent: Wednesday, August 01, 2001 5:29 PM
Subject: [xsl] xslt and edi question


> I am a software developer working for a business to business exchange.
> We are working on integrating our trading partners to the exchange using
> Commerce One's xCBL XML. To do this we also need to convert data from
> the format used by our trading partners (OAG, EDI, flat files, etc).
>
> XSLT appears to be a good solution for this challenge. A good portion of
> my work will include converting EDI documents to xCBL. I have also seen
> mappings of EDI formats to xCBL and OAG. I also currently have to
> translate a flat file (with delimiters) to xCBL. I realize I have more
> work going from non-XML data fields, however I'm assuming this can be
> done.
>
> Is my assumption correct, that non-XML "data" documents can be converted
> using XSLT. Any clarification, or additional advice would be greatly
> appreciated.
>
> Thanks for your time and consideration. I am also subscribing to
> Mulberry's user group, to post this there. Thanks again.
>
> Sincerely,
>
> Allen Kuhn
> akuhn@enporion.com <mailto:akuhn@enporion.com>
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]