1. ebXML Semantic Content Management Mark Crawford Logistics Management Institute mcrawford@lmi.org

2. Mark Crawford, LMI, 11 February 2004 LMI Agenda ebXML Overview The ebXML Registry Concept ebXML Core Components Summary

3. Mark Crawford, LMI, 11 February 2004 LMI The ebXML Initiative A joint UN/CEFACT and OASIS 18-month effort, concluding in May 2001 Over 1000 international participants from both XML and Business Communities The vision: a global electronic marketplace where enterprises of any size, anywhere, can: –Find each other electronically –Conduct business by exchanging XML messages Initial product is a technical framework that enables XML and other payloads to be utilized in a consistent manner for the exchange of all electronic business data ebXML work continues in OASIS and UN/CEFACT

4. Mark Crawford, LMI, 11 February 2004 LMI The ebXML Concept Source: ebXML Architecture TS, V1.04, Feb 2003

5. Mark Crawford, LMI, 11 February 2004 LMI The ebXML Construct Mark Crawford, LMI, 11 February 2004

6. LMI ebXML Design Time and Runtime Reference Model 8 8 ebXML CCBP Analysis Transport Package Business Service Interface Business Services/App’s Run Time Business Service Interface Business Services/App’s Registry/ Repository Core/Domain Components Business Documents CP Agreement Design Time Business Process Collaboration Protocol Profile Collaboration Protocol Profile Register & Discover Business Library Source: ebXML Business Process and Business Information Analysis Overview v1.0

7. Mark Crawford, LMI, 11 February 2004 LMI Agenda ebXML Overview The ebXML Registry ConceptThe ebXML Registry Concept ebXML Core Components Summary

8. Mark Crawford, LMI, 11 February 2004 LMI ebXML Registry Purpose: –Provide a set of services that enable sharing of information between interested parties –Enable business process integration between parties based on the ebXML specifications –Manage repository objects Latest specifications: –ebXML Registry Information Model, Version 2.5, June 2003 –ebXML Registry Services Specification, Version 2.5, June 2003 What it does: –Identifies shared objects maintained in a repository –Provides a set of services to manage and share these objects

9. Mark Crawford, LMI, 11 February 2004 LMI RIM – Public View RIM Provides information on: 1. The types of metadata stored in the Registry 2. The relationships among the various metadata classes. Source: ebXML RIM Specification, V 2.5, June 2003

10. Mark Crawford, LMI, 11 February 2004 LMI RIM – Detailed Inheritance View Source: ebXML Registry Information Model Specification, V 2.5, June 2003

11. Mark Crawford, LMI, 11 February 2004 LMI Agenda ebXML Overview The ebXML Registry Concept ebXML Core ComponentsebXML Core Components Summary

12. Mark Crawford, LMI, 11 February 2004 LMI ebXML Core Components A set of the lowest common denominators that capture information about real world (business) concepts Core Components are neutral –in the notation for every kind of industry –in the syntax for every kind of business document standard or implementation

13. Mark Crawford, LMI, 11 February 2004 LMI ebXML Core Components Reusable pieces (objects) of contents that can be atomic or aggregate –Enables interoperability among different industry domains and areas –Uses common semantic units at any level consistent across context –Holds any related information together and avoids fragmented semantic dispersal –Facilitates multilingual support Accompanied by methodologies for context and extensibility –Enables users to define meaningful business and process data –Ensures maximum interoperability

14. Mark Crawford, LMI, 11 February 2004 LMI Core Components Are Based On ISO 11179 Data Constructs Each aspect of 11179 relates to a CC construct

15. Mark Crawford, LMI, 11 February 2004 LMI An Example This is basic object-oriented “good stuff”

16. Mark Crawford, LMI, 11 February 2004 LMI Core Component Overview

17. Instantiating CC’s as BIEs  Mark Crawford, LMI, 11 February 2004 LMI

18. Technical Details CC and Data Types Metamodel  Mark Crawford, LMI, 11 February 2004 LMI

19. Technical Details – BIE Metamodel  Mark Crawford, LMI, 11 February 2004 LMI

20. The Storage Metamodel – Core Components  Mark Crawford, LMI, 11 February 2004 LMI

21. The Storage Metamodel – Business Information Entities  Mark Crawford, LMI, 11 February 2004 LMI

22. The Storage Metamodel - Context Definition  Mark Crawford, LMI, 11 February 2004 LMI

23. The Storage Metamodel – CCTS Metadata  Mark Crawford, LMI, 11 February 2004 LMI

24. Mark Crawford, LMI, 11 February 2004 LMI Where 11179/Core Components Methodology is Being Used Basis for Emerging Business Standards –United Nations CEFACT XML, EDI, OO –ANSI ASC X12 XML –OAG OO –OASIS UBL Basis for various Federal XML Efforts –NARA Transfer Schema With XSLT to METS Schema –SBA Schema Initiatives –FEA Schema –T-REX Schema –Various EPA Schema –Federal & Agency XML Naming and Design Rules –Federal Schema Best Practices –DON XML Basis for Data Reference Model piece of FEA Basis for ebXML Registries Basis for EPA EDR & DON XML Registry Requirements

25. Mark Crawford, LMI, 11 February 2004 LMI Agenda ebXML Overview The ebXML Registry Concept ebXML Core Components SummarySummary

26. Mark Crawford, LMI, 11 February 2004 LMI Summary ebXML provides a flexible framework for eBusiness information storage, management, and exchange ebXML semantic content metadata consists of that required by the RIM and CCTS The ebXML registry is at the heart of the architecture The ebXML registry provides the mechanism for capturing and managing the content

27. Mark Crawford, LMI, 11 February 2004 LMI Summary ISO 11179 provides a mechanism for expressing data and metadata consistently across communities The ebXML Core Components methodology provides the mechanism for ensuring the semantic content is consistent across users ebXML semantic content management provides VCS based approach to consistent registration and metadata standardization for all types of artifacts – to include data and document centric A number of key federal and VCS initiatives are basing their work on ebXML/ISO 11179

28. Mark Crawford, LMI, 11 February 2004 LMI A Final Thought Voluntary Consensus Standards are Hard But in the long run the mission suffers because data is not interoperable and mission resources are diverted to data transformations Its easy to justify not using them for mission requirements Especially those that cross functional boundaries

29. Mark Crawford, LMI, 11 February 2004 LMI For More Information For ebXML: http://www.ebxml.org For ebXML Registry: http://www.oasis-open.org For ebXML Core Components: – For ISO 11179 & Metadata Registries –Bruce Bargmeyer - BEBargmeyer@lbl.gov For other referenced standards work: mcrawford@lmi.org For referenced Federal Initiatives using 11179/ebXML: –marion.royal@gsa.gov –vineski.steve@epa.gov –robert.a.green2@navy.mil –mcrawford@lmi.org For OASIS UBL TC –http://www.oasis-open.org