Jostein Frømyr jostein.fromyr@edisys.no Chief Technical Officer, EdiSys Past chair of eBES TCG

1. How does ebXML address semantic interoperability?Who is using ebXML today?Presentation at the CEN/ISSS ebXML Market Survey EventOslo, February 8, 2006 Jostein Frømyr jostein.fromyr@edisys.no Chief Technical Officer, EdiSys Past chair of eBES TCG Secretary of UN/CEFACT ATG2

2. Who is using ebXML today? A review of the global adoption of ebXML. How does ebXML address semantic interoperability? A more in-depth presentation of ebXML Core Components and the value it brings to the concept of semantic interoperability. The ebXML Awareness Team Use of e-busienss technologies The ebXML user community Technical infrastructure Semantic framework Core Components Actual projects Today’s presentation …

3. The OASIS ebXML Awareness Team • ebXML is unique in the breadth of its standards vision and arguably represents the culmination of all previous standards efforts toward a shared global Internet-based B2B framework. http://www.ebxml.org/ebxml_jmt

4. ebXML Adoption update, December 2003. Electronic Business Technologies • ebXML is complementary to many existing standards and technologies, such as legacy EDI, XML-based business document standards, and Web Services.

5. The ebXML user community • Over 2,000 people contributed to the original ebXML development efforts, made public in May 2001. • Since then, continuing standards development, pursued jointly by OASIS and UN/CEFEACT, has being augmented by creative real world projects applying ebXML with other technologies such as Web Services, XML as a whole, as well as legacy EDI.

6. The technical infrastructure • Major vendors have developed ebXML support into their flagship products and new ebXML vendors are emerging. Mercator Oracle Ponton Consulting POSDATA Samsung, SDS, Korea SeeBeyond Seeburger AG Smartdraw.com Sockeye Solutions Sterling Commerce Storefront.CO Sun Microsystems Sybase Inc TIBCO Software Inc XENI Adobe Zenaptix Vitria WebMethods Webswell Whitehill Technologies TIE ebXMLsoft Sonic Software Fujitsu Limited HanMaek IT InnoDigital Co., Ltd IONA Iopsis IPNet Solutions Inc. iWay Software Killdara Corp Kinzan KTNET Mega Software … and probably many more

7. The semantic framework • Industry groups and standards bodies are working to bring their vocabularies into alignment around ebXML, promising a new level of interoperability that industry has been seeking for more than a decade. • Industry independent standards groups • ISO TC154, the current group responsible for EDIFACT – complete alignment to Core Components • OAGi (Open Applications Group) – OAGIS Version 9.0 and later • OASIS UBL (Universal Business Language) • Industry dependent standards groups • ACORD for Insurance Data • AIA (Aerospace Industry Association) • AIAG, ODETTE and JAMA/JAPIA – for all current and future projects in the international automotive sector. • BoostAero for its Supply Chain Project in the Aerospace and Defense Industry • CIDX in the chemical industry for its Material Safety Project • CIDX (chemical), PIDX (oil) and RAPID (agriculture) – evaluating a move to core component compliance • EUDIN for European Waste Movement Project • Eurofer for Messages in European Steel Industry • HL7 for future Healthcare Data • IATA (International Air Transport Association) • GS.1 for Supply Chain Messages and Cataloging • OTA (Open Travel Alliance) - evaluating for Business Data in Travel-Industry • SWIFT for Messages in Financial Business Processes • SITPRO and EUROPRO for Sanitary & Phytosanitary Certificates • XBRL - evaluating for future Accounting & Audit data and collaboration with UN/CEFACT • Governments groups • Department of Navy – DONXML V2.0 • DCMA (Defense Contract Management Agency) • NDIA (National Defense Industrial Association) • US Federal CIO Council • International groups • eBes – (eBusiness Board for European Standardization) - for its Invoice Processing and Remittance Advice • GJXDM (Global Justice XML Data Model) • WCO (World Customs Organization) • National Governments • Australian Government • Canadian Government • Danish Government • German Government – formal announcement identifying CCTS as future data standard for domestic affairs • Hong Kong Government • Korean Government • Sweden and Norway are evaluating Core components • Software vendors • SAP • Oracle … and probably many more

8. Transport Retail Telecom Energy Social Security Consignment  Product      Organisation      Address      Core Components … • … are reusable components that can be applied in a standard way within a business context. • … represents the business objects of e-busniness • … are defined using items that are common across businesses • … enables users to define information that is meaningful to their business while also continuing to maintain interoperability with other business applications Healthcare Entertainment

9. Core Component Technical Specification • A methodology for • developing a common set of semantic building blocks • to identify, capture and maximize the re-use of business information to support and enhance information interoperability across multiple business situations • Follows the principles of ISO 11179 • Enables • interoperability among different industry domains • common semantic units at any level consistent across context • multilingual support • Is gaining support from a number of XML initiatives and user groups • Rosetanet, OAG, SWIFT, EAN, UBL, .... • The first library of harmonized core components are now available from UN/CEFACT

10. The UN/CEFACT Core Component library • UN/CEFACT TBG is proud to announce the release of its version 1.0 Core Components Library. This library - containing 49 ACC´s and 478 objects in total - has been developed in strict conformance to the UN/CEFACT developed ISO 15000-5 ebXML Core Components Technical Specification (CCTS) and replaces the pre-version 1.0 library released in January of this year. • The UN/CEFACT Core Component library is intended as the basis for all future business vocabulary work by UN/CEFACT. It is also available without restriction to other implementers of ISO 15000-5 who share a common goal of building reusable, interoperable business libraries. All users are encouraged to develop context specific CCTS conformant Business Information Entities from this library. Where necessary, users should also identify additional candidate Core Components following CCTS methodology and rules. All new Business Information Entities and Core Components should be submitted to UN/CEFACT TBG17 for inclusion in the UN/CEFACT Library.

11. BIE = CC in Context • Core Component (CC) • generic building block • unique semantic definition and content • Business Information Entity (BIE) • specific building block for use within a given business context • sub-set (based on) a Core Component • Business Context defined through a set of context drivers • Business process • Product classification • Geopolitical region • Official constraint • Business process role • Supporting role • System capabilities

12. Semantically defined data types Semantically defined data types are used to allow for business specific validation of the data. • CCT = Core Component Type • A generic data type as defined in CCTS • Used as reference for definition of UDTs • UDT = Unqualified Data Type • UN/CEFACTs application and use of CCTs • Defined based on a CCT • QDT = Qualified Data Type • Date types defined for use within a given business context • Defined as a restrictions of a UDT • Field size • Choice of code list • Choice of code values • Combination of code values

13. Semanticallydefineddata types

14. The message model • Messages definitions are assembled from the defined Business Information Entities. • A message model is an hierarchical structure describing the data contained in a message during exchange from one party to another.

15. Core Components is a key part of the ebXML semantic framework • Facilitates a clear distinction between the logical view (the model ) and the technical solution (e.g. XML or EDI) • Enables harmonization and common understanding of business semantics across domains Collaboration model Processes – activities – Interactions Business information UMM UN/CEFACT Modelling Methodology Harmonized components Message model CCTS UN/CEFACT Core Components Technical Specification NDR UN/CEFACT XML Naming and Design Rules MDR UN/EDIFACT Message Design Rules Technicalsolution

16. Global adoption • Key industry sectors and government entities are deploying new eBusiness applications that are serving as benchmarks in the adoption of ebXML globally.

17. European ebXML projects - Commercial … and probably many more

18. European ebXML projects - Government/EU

19. European ebXML projects - Government/EU … and probably many more

20. The IDA program about ebXML … • "The study has shown that ebXML is the only framework that is at the same time generic and flexible, and can be used for inter-administrations relations. Moreover, ebXML is clearly the only trend for organised business communities. The general recommendation is to follow ebXML standards as much as possible. This is coherent with the fact that many exchanges between European administrations reflect the interactions between those administrations and the national business world.“ • Conclusion by IDA in their study on Business-to-Business frameworks (http://europa.eu.int/ISPO/ida/jsps/doc.jsp?1564)

21. Special report one-Business Interoperabiliyt and StandardsSeptember 2005 • "Systems such as ebXML have reached a point where they are now ready for full deployment". • "If, as some contend, the market for Web Services has peaked, and Grid Services are already the next big venture ... it is advisable for SME managers to be very cautious before risking their business ... ebXML represents a far safer and more viable option at this time". • “… the investment in ebXML will continue to pay dividends for the foreseeable future"

22. Thank you for your attention … and welcome as a user of ebXML!