|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
Re: Re: TDCC and EDI X12
At 04:49 PM 11/17/2003 +0000, georgeopenx1 wrote:
>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.
George,
ebXML is a bit of an old topic on this and the ebxml-dev list, so I'm not
too inclined to beat dead horses any more than absolutely needed. However,
you do seem to have a few misconceptions which I would be glad to
straighten out.
ebXML was/is *not* about converting EDI into XML. There are really two
parts - a technical infrastructure which is similar in many ways to Web
services, and a standards development approach which describes a way to do
business process analysis and modeling, and data analysis and modeling
(core components). Given how ebXML was developed and what it actually is,
there's no reason why EDI syntax messages (X12 or EDIFACT) couldn't be
developed using the ebXML BP and core component approaches, then exchanged
using an ebXML compliant technical infrastructure. So, ebXML is not
necessarily strictly XML.
UN/CEFACT is continuing the work of ebXML by developing business process
descriptions and XML messages based on the ebXML approach. To date none
have been produced. Several organizations such as UCC/EAN, RosettaNet, and
OAG, claim some degree of support for ebXML BP and core component work in
the standards that they have developed.
If and when XML-based messages (ebXML or otherwise) are developed that fill
the same needs as EDI messages, the EDI may be out of date. But, that's
kind of a moot point. Legacy technology usually has a way of living on
long past its expected lifetime.
Hope this helps,
Mike
(project leader, ebXML Requirements Team)
---------------------------------------------------------------
Michael C. Rawlins, Rawlins EC Consulting
www.rawlinsecconsulting.com
Using XML with Legacy Business Applications (Addison-Wesley, 2003)
www.awprofessional.com/titles/0321154940
|
|
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
