Lets imagine the following scenario: There is an electronic commerce system with an integrated shopping system and you want to generate electronic orders in XML format in order to forward them to your suppliers business system over the internet. I don't want to create an own notation I want to use an existing standard. Reading a lot I am aware of the ongoing XML/EDI initiatives. XML is pushed as the future solution of the EDI dilemma. But EDIFACT will not be replaced by XML. There will be both worlds. I need something that seamlessly migrates to both sides. Sounds like a typical requirement in the recent electronic commerce development environment, isn't it? There is one big question in the air which i am certain I am not the only one to be faced with: "Which xml dtd / format / structure / initiative should be chosen that will do the best job?" - I see CBL 2.0, a framework of message building blocks designed to construct an order message. 2.0 sounds good and mature. How should the order message look like? How must the underlying application look like? Are there any experiences with CBL? CBL and EDIFACT??? - I see cXML with its predefined message structures. Looks like a traditional EDI approach with a fixed and inflexible message structure. Does it meet all demands a business system can have? How will it be extended in the future? Who is using the cXML? - I see the biztalk framework, which follows another way. There will be XML schemata published within this framework. I can submit my own and build translators to other message types. Very interesting. How should my message type look like? What about translators to EDIFACT or ANSI X.12 based messages? Doesn't that mean that I have to understand every message type I want to communicate with? Sounds quite work intensive from my perspective ... - What about the ebXML initiative? CEFACT developed the EDIFACT standard, how will an XML based work look like? Is there already some concrete work? - What about these numerous converter tools that claim to be xml enabled? I had a notion that they mainly contruct a xml structure out of the EDIFACT structure by using the EDIFACT qualifiers or codes as tag names. - What about the XML/EDI repository? Is there any work that can be used already? Are there any experiences? How should it be used? Is the any migration path to traditonal EDIFACT solutions? - What else is available? What should be considered and evaluated? Is there any impartial evaluation of existing xml/edi initiatives already available? - Where is the main difference between XML.org and Biztalk and why are there again different approaches, different work, different standards. Are these initiatives disjunct or are there any intersections? How should I value these initiatives??? Aren't they both aiming the same objective??? And if yes, do they cooperate? Or is it again a case of pure competition? - Is it too early for an XML based solutions and should we go back to the roots and implement an EDIFACT based solution? Any help, contributions, answers and suggestions will by highly appreciated! regards Bernd Buchegger Product Development Manager - intos GmbH Primoschgasse 3 - 9020 Klagenfurt tel: ++43 463 / 3875 - 250 fax:++43 463 / 3875 - 255 ========================================== XML/EDI Group members-only discussion list Homepage = http://www.xmledi.com Brought to you by: Online Technologies Corporation Home of BizServe - www.bizserve.com TO UNSUBSCRIBE: Send email to <[EMAIL PROTECTED]> Leave the subject blank, and In the body of the message, enter ONLY: unsubscribe Questions/requests should be sent to: [EMAIL PROTECTED] To join the XML/EDI Group complete the form located at: http://www.geocities.com/WallStreet/Floor/5815/mail1.htm
