[EDI-L Mailing List Archive Home] [Message List] [Reply To This Message]

RE: Re: TDCC and EDI X12

From: "Peter Olivola" <polivola@...>
Date: Mon Nov 17, 2003  5:52 pm
Subject: RE: [EDI-L] Re: TDCC and EDI X12
Data formatting is not now and never has been the primary issue with
document exchange/application interoperation. ebXML will only be as
successful as the companies involved in implementing it can agree to accept
the definitions employed. Is business willing to forego its own
definitions? There isn't a lot of evidence that this will happen quickly or
involve large numbers of trading partners.

Even if ebXML is viewed as a layer in the data exchange/application
interoperation whole, implementing it without all layers employing the same
definitions will not reduce the need to code and maintain the differences.
That extends the problem beyond trading partners and includes application
software.

Peter Olivola
708 445 0023


-----Original Message-----
From: georgeopenx1 [mailto: Sent: Monday, November 17, 2003 10:49 AM
To: Subject: [EDI-L] Re: TDCC and EDI X12


Bob and any eBiz experts,
Let us discuss ebXML framework stuff first. I agree with you about
that ebXML is a framework for the future electronic trading market.
ebXML is broader than current EDI standards because it includes all
the business activities but X12 or others only format the EDI data.
Concerning about message format, the specific part of ebXML, to my
understanding, it should be XML format which means all the EDI data
will be written as XML tags then will be transmitted in XML format
(SOAP). If it was true, the current X12 or EDIFACT standards will be
out of date, am I right?
I noticed there was no description about EDI data format in ebXML
technical documents. OF course, the biz data is not that much more
important than other parts on the architect level, but I just want to
make it clear that whethere we have to describe biz data in XML or
other available ways. People always compare ebXML with Web Services
which is composed of SOAP, UDDI, WSDL based on XML. In term of Web
Service, there is no concerns about the data itself wrapped.




 
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools Simplify EDI Data Integration with Stylus Studio XML Enterprise Suite - Free Download!
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2007 All Rights Reserved.