|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: EDI <-> XML Translator
I have privately received few questions for clarification, here's the
response.
1. I assumed a packaged EDI<->XML translator product, since the question was
in reference to EDI/XML translator products
2. EDI->XML translation (commonly referred as "inbound" in the context of
XML being application-EDI interface file) involves, parsing (analyzing) an
EDI file, mapping it to the desired application file (just like it would be
done for more traditional application-EDI interface files) and generating
the application file (it's an XML file in the context). The "outbound"
process (XML->EDI translation) will be just the opposite.
3. To achieve EDI<->XML translation, "mapping" has to be done (just like you
would have done if you were using more traditional application flat-files).
Most translator products (I think) provide simple drag and drop mapping
capability (one time effort). For most cases you do not have to do any
programming for mapping. I by no means suggested that mapping is not
required or is bypassed. I assumed that my usage of term "application-EDI
interface" was self explanatory in this context.
4. I write:
"In context of EDI to XML translation, XML is used as part of
application-EDI interface, replacing fixed/variable length nested sequential
flat-files. A good reason to do this is because, you do not have to
write(code) a parser/writer."
When I say, you do not have to "write(code)" a parser/writer, I mean that
you can "use" OS or third-party provided XML Parser and writer from the
inside your business application.
For example, in our XML/EDI translator, we "used" MSXML SAX parser directly,
simply providing our own handlers for events like "startElement",
"endElement", "characters" etc. You will do it "similarly" in your business
application, depending on the SAX/DOM parser you wish to "use". You do not
have to write(code, program) your own parser or writer.
I hope this clarifies any ambiguity. Please feel free to ask more questions.
Thanks,
Ajay
-----Original Message-----
From: Ajay K sanghi [mailto:
Sent: Wednesday, October 03, 2001 12:10 AM
To:
Subject: RE: [EDI-L] EDI <-> XML Translator
Glenn,
In context of EDI to XML translation, XML is used as part of application-EDI
interface, replacing fixed/variable length nested sequential flat-files. A
good reason to do this is because, you do not have to write(code) a
parser/writer.
In the context of EDI to XML translation, you do NOT have to use any
XML-based initiatives like Rosettanet, ebXML etc. Why? Because, in the given
context, XML is your application data. It is your business application and
you decide it's layout.
Ajay
Ajay K Sanghi
Managing Director
ABO Software Private Limited
B102 Gulmohar Park, New Delhi 110049
Tel: +91 11 6968976, 6512822 Fax: 6518873
Website: http://www.abosoftware.com
email:
-----Original Message-----
From:
t.com
[mailto:sentto-2107676-343-1002052309-sanghi=giasdl01.vsnl.net.in@return
s.onelist.com]On Behalf Of J. Glenn Thompson
Sent: Wednesday, October 03, 2001 1:20 AM
To:
Subject: Re: [EDI-L] EDI <-> XML Translator
I am coming to the fountain of knowledge hoping to drink. I am seeing more
and more EDI to XML and vice versa translators. To what standard does the
XML
adhere to? What is the XML being used for other than displaying in a
browser?
I am just curious as to what extent and what purpose XML is being used.
Please use small words in your explanations :-)
--
Glenn Thompson
Senior Analyst
American Trouser, Inc.
To unsubscribe from this group, send an email to:
Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>,
<PRODUCT>
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
To unsubscribe from this group, send an email to:
Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>,
<PRODUCT>
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
