[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: AW: Summary of XML Datatypes as required for B2B applications
i do not believe anyway is seriously considering a 1:1 conversion of X12 and/or EDIFACT to XML. as you point out the syntax is not the important issue - it is the semantics. therefore, the point being made is that we must ensure the semantic knowledge of EDI experience is incorporated into any XML initiatives. Andreas Schultz wrote: > I agree with those of you, who think that a conversion of EDIFACT messages > into XML is not the right way. This will not solve the problems. We would > take the restrictions of EDIFACT into the restrictions of XML. This will > mean multiplying the restrictions. But on the other hand, we should not > ignore the business know how which is in the EDIFACT messages. We should > save the best of EDIFACT and combine it with the best of XML. Please allow > me to remind us all what are we really talking about: We want to exchange > informations between partners in a standardised way. The syntax to choose > for this is a second question. This should be dependent from the special > need of the business partners. > > Andreas Schultz -- regards tim mcgrath TEDIS fremantle western australia 6160 phone: +618 93352228 fax: +618 93352142
begin:vcard n:McGrath;Tim tel;pager:australia 016 631 632 tel;cell:041 381 6846 tel;fax:+61893352142 tel;work:+61893352228 x-mozilla-html:FALSE adr:;;;;;; version:2.1 email;internet:tmcgrath@tedis.com.au x-mozilla-cpt:;-4960 fn:tim mcgrath end:vcard
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC