|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
Re: EDI and XML Processing
Thanks to all that responded on this issue. Although I architected,
designed and implemented an EDI-XML Transformer for the former Netfish
Technologies, I no longer believe that a corporation would have a need for
this type of translator/transformer. I may be working in a tunnel, however,
so please forgive any naive comments. It does not make any sense to take
an X12 document and convert it to a RosettaNet document type or any other
XML flavored document.
Our data originates and terminates in Oracle Applications and databases. We
have a mix of trading partners who can span a number of data formats
including EDI X12, EDIFACT, and XML standards as well. Those partners in
the trading network to whom we trade EDI documents over traditional VAN's
will stay that way. The issue really boils down to transport mechanisms and
data security as it usually does in our EDI world. For these cases, we will
use EDI-INT AS2 to communicate secure EDI documents via email. Using our
XML based server, we have decided to XML enable those TP's that can
communicate in this manner and keep the EDI partners on the EDI Server. We
have an excellent XML server product that can handle the migration when it's
time for those TP's to do so when they are in a ready position to migrate.
Thanks again to all who responded. It helped us immensely.
Regards-
Gerard
----- Original Message -----
From: "Bill Chessman" <
To: <
Sent: Tuesday, September 25, 2001 12:59 PM
Subject: RE: [EDI-L] EDI and XML Processing
> The RosettaNet documents thus far are designed to XML enable the
electronics
> industry (computers, devices, etc.). I have heard some small amount of
talk
> about it being adopted by other industries, however I understand that the
> overall adoption rate is rather lower than was hoped for. In any case,
I'm
> not quite sure what you mean, but RosettaNet doesn't have anything to do
> with EDI<-->XML (at least not that I'm aware of...I'm sure there are
others
> who can say better than I).
>
> I do understand the idea of retaining your workhorse, but I'm concerned
that
> the more stuff that's plugged and bolted and nailed together, the more
> likely that the processes involved will look like a Rube Goldberg cartoon.
> If you're system is not home-grown, hopefully, the vendor of your EDI
> solution software would be able to provide (or be working on providing) an
> upgrade path that would more seemlessly support EDI and XML translation
> needs without the extra steps. (Not trying for a shameless plug, but I
know
> we've been moving that way on some of our products.)
>
> Best regards,
> Bill Chessman
> Peregrine Systems, Inc., E-markets Group
>
> P.S. I'm a programmer, not a marketeer. 8-)
>
> -----Original Message-----
> From: Cancilla, Chris [mailto:
> Sent: Tuesday, September 25, 2001 12:15 PM
> To:
> Subject: RE: [EDI-L] EDI and XML Processing
>
>
> Is that not what one aspect the RosettaNet initiative is supposed to do?
> Standardize the XML transactions world-wide. At least on e-paper.
>
> Running an NT server to perform EDI-->XML / XML-->EDI translations allows
> you to retain your workhorse (Mainframe/AS400/UNIX) while still having the
> capability, separate as it is, to perform the "high-tech" XML to EDI
> translations on incoming XML documents.
>
> <snip/>
>
>
> 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
