History

1. History Strategies What ebXML is Scope, Relationships Why ebXML ebXML Requirements Mission, Values Deliverables & Core Components

2. History • Nov 9, 10 1999 • NATO meeting, The Hague • State-of-the-market presentation by OASIS "NATO and its member nations recognize the need to encode agreements on information exchange in XML before a plethora of uncoordinated, non-interoperable encodings get developed in defense systems projects." Dr. Klaus G. Muller of the NC3A

3. Accelerating the adoption of industry standards 100+ member companies including IBM, Sun, Microsoft, Corel, Software AG, and Oracle. The XML Industry Portal Sponsored by IBM, Sun, Oracle, SAP, ... A vendor-neutral XML schema clearinghouse. Info on how to apply XML in industrial and commercial settings. United Nations Centre for the Facilitation of Procedures and Practices for Administration, Commerce and Transport A global XML & EDI initiative

4. OASIS Non-profit international consortium Advance the open interchange of documents and structured information objects SGML, XML, xml.org UN/CEFACT United Nations body under Trade Facilitation Global policy and technical development in the area of trade facilitation and electronic business UN/EDIFACT Put its own XML program on hold until completion of ebXML work History A joint effort . . .

5. History • Nov 17-19, 1999 • Inaugural meeting, San Jose, CA • 140 participants from major companies, countries and organizations • Jan 31-Feb 4, 2000 • Project Team meetings, Orlando, FL

6. Why ebXML • Traditional EDI adoption growing • Rate of adoption decreasing • XML/Internet e-commerce applications increasing • Many vendor schemes for near-verbatim EDI-to-XML message translation emerging

7. Why ebXML • Traditional EDI vendors want to grow EDI market share while transitioning customers to interface with new XML representations of business objects • Need for a common message structure and syntax so that industry-specific XML vocabularies will interoperate • No business communicates solely in its supply chain • Must be able to exchange messages with those outside their industry boundaries

8. Mission • Provide an open XML-based infrastructure enabling the global use of electronic business information in an interoperable, secure and consistent manner by all parties.

9. Value • Provides the only globally developed open XML-based Standard built on a rich heritage of electronic business experience • Creates a Single Global Electronic Market • Enables all parties irrespective of size to engage in Internet-based electronic business

10. Value • Provides for plug and play shrink-wrapped solutions • Enables parties to • complement and extend current EC/EDI investment • expand electronic business to new and existing trading partners • Facilitates convergence of current and emerging XML efforts

11. Strategies • Use the strengths of OASIS and UN/CEFACT to ensure a global open process • Develop technical specifications for the open ebXML infrastructure • Create the technical specifications with the world’s best experts • Collaborate with other initiatives and standards development organizations

12. Strategies • Build on the experience and strengths of existing EDI knowledge • Enlist industry leaders to participate and adopt ebXML infrastructure • Realize the commitment by ebXML participants to implement the ebXML technical specifications

13. ebXML Scope* • Develop relevant and open technical specifications to support • Domestic and international electronic business exchanges • Make publicly available • Complete effort within 15-18 months *ebXML Terms of Reference http://www.ebxml.org

14. Relationship between ebXML and other XML initiatives • Few other XML initiatives are trying to do what ebXML has set out to do • Most such efforts address single industries or specific business functions • Most of these other initiatives support ebXML and participate in its development

15. What is the relationship between ebXML and W3C? • W3C defines the basic XML standards • ebXML aims to establish common conventions for the use of XML in business data exchange • Both groups complement each other

16. Does ebXML address the needs of the SMEs? • Yes • ebXML expects that shrink-wrapped, plug-and-play software will support its messages • Economies of scale presented by the Web will keep the ebXML design and technical architecture within the reach of smaller businesses

17. Is ebXML re-creating the wheel? • No • Not "starting from scratch“ • Building on experience of • EDI standards • Current XML e-business vendors • XML industry standards organizations • to build a framework to maximize interoperability

18. Organization • 8 Project Teams • Architecture • Business Process • Core Components • Marketing, Awareness & Education • Requirements • Registry & Repository • Transport, Routing & Packaging • Technical Coordination & Support • Executive Committee

19. Major requirements • General Business Requirements which relate to the need for a single consistent approach to use XML • The need to support for both vertical and horizontal solutions regardless of the user’s level of sophistication • The need to support for a range of basic, low cost solutions for Small or Medium Enterprises (SME’s) as well as complex solutions appropriate to large enterprises • A general specification for developing XML-based Schematas

20. Major requirements • The need for globalized solutions which will accommodate national and international process requirements • Completely open accessibility, enabled by a registry and repository • The need for an architecture that will ensure and maximize interoperability by supporting common business process, common semantics, a common vocabulary, and common character encoding • Consistent transport, routing and packaging methodologies to ensure secure sending and receiving of messages over the Internet • Digital signature and other security related capabilities

21. ebXML general deliverables • Technical Architecture Specification • Repository & Registry Functionality Specification • Transport, Routing & Packaging Specification • ebXML Glossary of Terms

22. ebXML Core Components • Reusable components that can be applied in a standard way • Accompanied by methodology for extensibility • Enable users to define meaningful business and process data • Ensure maximum interoperability

23. ebXML Core Components • Common semantic units at any level consistent across contexts • Reusable within and between business exchange messages • Business process models • To define common items • Provide context • Independent of implementation syntax • Apply equally to XML and/or EDI

24. ebXML Specification Deliverables • May 8-12, Brussels meeting • ebXML Requirements • ebXML Conceptual Architecture • ebXML Message Structure and Headers • ebXML Core Components Specification

25. How to participate • Sign up at www.ebXML.org • Select a project team • Project Teams • Listserv • Teleconference • Scheduled meetings • Web site

26. Meeting Schedules • 8-12 May 2000 • Brussels, Belgium • 7-11 August • United States • 6-11 November • Tokyo, Japan

27. ebXML . . . The first . . . The only global . . . The last opportunity this decade . . . To fashion a global specification for the conduct of electronic business