|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: <Sales> XML/EDI Products
Michael,
You don't have to buy an expensive translator to do the things you are
talking about. At the low end are the XML Spy products and for a little
more you have a product like Edifix that can do data modeling as well as
create schemas and EDI implementation guides.
The big issue to be careful with is creating meaningful XML tags. Using
EDI field names to make XML tags makes for a fairly meaningless schema.
Look at the work of OAGI or UBL to see how much effort goes into tag
names.
Regards,
David Frenkel
Business Development
GEFEG USA
Global Leader in Ecommerce Tools
www.gefeg.com
612-237-1966
-----Original Message-----
From: Michael Mattias [mailto:
Sent: Wednesday, February 12, 2003 12:53 PM
To: EDI-L (E-mail)
Subject: Re: [EDI-L] <Misc>Flat File Creation - clarification.
2/11/03
<SHAMELESS COMMERCIALISM>
A couple of months ago I had an idea for a low-cost "generic" tool which
would convert ANSI ASC X12 EDI into XML and vice versa; the
idea being to take advantage of all the relatively low cost XML software
out there to obviate the need for an expensive translator
for those who only need to handle a couple of transaction sets.
This would take an input file containing ANSI EDI and create an output
file kind of like..
<?xml version="1.0" encoding='UTF-8'?>
<File>
<Interchange>
<ISASegment>
<Elements>
<E01>00</E01>
<E02></E02>
...
</Elements>
</ISASegment>
<Functionalgroup>
<GSSegment>
...
<TransactionSet>
<Segment>
<SegId>ST</SegId>
<E01>850</E01>
<E02>12345</E02>
</segment>
<Segment>
<SegId>BPR</SegId>
<E01>01</E01>
<E02>021103</E02>
</segment>
.....
<Segment>
<SegIdSE</SegId>
<E01>12</E01>
<E02>12345</E02>
</segment>
</TransactionSet>
</FunctionalGroup>
</Interchange>
</File>
I was thinking some kind of command-line utility and/or API call like,
"EDItoXML InputEDIFileName OutputXMLFileName" usable on
Windows(r) systems.
I'd also have the companion function, "XMLtoEDI InputXMLFile
OutputEDIFile" which would just collect up the XML nodes and wrap it.
(OK, so maybe I'd add some other goodies on the outbound side).
I kind of set this project aside to work on some other things, but this
discussion of "generic mapping" has kind of roused the black
bear from hibernation. I already have EDI and XML parsing engines: put
'em together, figure out an XML tag name scheme ("DTD"), I
got this. For those tag names, not sure exactly how I'd do it, but I'd
probably have descriptive names for the envelope segments
(ISA, IEA, GS, GE, ST, SE) and just "segment names" and
"element/subelement numbers" for all other segments and elements.
If I could put something like this together and offer a copy with both
command-line utility and "API" capability for say, $100-$200
per copy, might that be of interest to anyone?
Any ideas/comments appreciated (if you want to get 'techie' feel free to
send off-list).
(Yes, I know some vendors already offer something similar. But not in
the price range I am talking about; not with an "API"
interface; and certainly not where "install=copy less than one floppy
disk").
Michael Mattias
Tal Systems, Inc.
Racine WI
To unsubscribe from this group, send an email to:
Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>,
<OFF-TOPIC>
Access the list online at: http://groups.yahoo.com/group/EDI-L
Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
|
|
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
