1 / 29

ebXML Semantic Content Management

ebXML Semantic Content Management. Mark Crawford Logistics Management Institute mcrawford@lmi.org. Agenda. ebXML Overview The ebXML Registry Concept ebXML Core Components Summary. The ebXML Initiative. A joint UN/CEFACT and OASIS 18-month effort, concluding in May 2001

talasi
Download Presentation

ebXML Semantic Content Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ebXML Semantic Content Management Mark CrawfordLogistics Management Institutemcrawford@lmi.org

  2. Agenda • ebXML Overview • The ebXML Registry Concept • ebXML Core Components • Summary

  3. 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. The ebXML Concept Source: ebXML Architecture TS, V1.04, Feb 2003

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

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

  7. Agenda • ebXML Overview • The ebXML Registry Concept • ebXML Core Components • Summary

  8. 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. RIM – Public View • RIM Provides information on: • The types of metadata stored in the Registry • The relationships among the various metadata classes. Source: ebXML RIM Specification, V 2.5, June 2003

  10. RIM – Detailed Inheritance View Source: ebXML Registry Information Model Specification, V 2.5, June 2003

  11. Agenda • ebXML Overview • The ebXML Registry Concept • ebXML Core Components • Summary

  12. 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. 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. Core Components Are Based On ISO 11179 Data Constructs Each aspect of 11179 relates to a CC construct

  15. An Example • This is basic object-oriented “good stuff”

  16. Core Component Overview

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

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

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

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

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

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

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

  24. 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. Agenda • ebXML Overview • The ebXML Registry Concept • ebXML Core Components • Summary

  26. 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. 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. A Final Thought Voluntary Consensus Standards are Hard Especially those that cross functional boundaries Its easy to justify not using them for mission requirements But in the long run the mission suffers because data is not interoperable and mission resources are diverted to data transformations

  29. For More Information • For ebXML: http://www.ebxml.org • For ebXML Registry: http://www.oasis-open.org • For ebXML Core Components: • <chair: Alan.Stitzer@marsh.com> • <editor: mcrawford@lmi.org> • 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

More Related