1 / 18

Collaborating to Develop an Ontological Basis for E-Business Standards

Collaborating to Develop an Ontological Basis for E-Business Standards. by Peter P. Yim < peter.yim@cim3.com > July 6, 2004 - Workshop on: “ Extending Enterprise Ontologies: Levels, Limits, and Tensions ”. at the 7th Protégé International Conference Date: July 6~9, 2004

aaron-barton
Download Presentation

Collaborating to Develop an Ontological Basis for E-Business Standards

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. Collaborating to Develop an Ontological Basis for E-Business Standards by Peter P. Yim <peter.yim@cim3.com> July 6, 2004 - Workshop on: “Extending Enterprise Ontologies: Levels, Limits, and Tensions” at the 7th Protégé International Conference Date: July 6~9, 2004 Venue: NIH – Bethesda, MD ( v 1.10 )

  2. Outline • Background • Purpose of this presentation • What do Standards, Ontologies & Collaboration have in Common? • Getting back to basics • The “CCT-Representation” project • [CCT-Rep] project mission • What is a CC (“Core Component”) ? • Our approach • a Status Report • An unprecedented opportunity and challenge • a solicitation

  3. Purpose of this presentation • Introducing [CCT-Representation] -- one of the projects being undertaken by the [ontolog] community • Through it, reflect upon how we are dealing with “Extending Enterprise Ontologies: Levels, Limits, and Tensions” in the flesh • Share the vision and mission of one very meaningful, yet challenging opportunity in front of the ontological engineering community • Solicit participation and contribution to this very meaningful project

  4. What do Standards, Ontologies & Collaboration have in Common? • Common goals • Interoperability (working together) • Better efficiency (time & cost) • Adopting best practices • Eliminating duplicated efforts • Optimal Effectiveness (getting things done; responsive) • Common approach • Eliminate/Reduce Ambiguity • Develop Shared Understanding “ … on tackling 'wicked problems': it's about having a shared commitment, developing a shared understanding, augmented by a shared display and a facilitator.” -- citing the work by the IBIS people (Horst Rittle/Jeff Conklin)

  5. Back to basics: • Ontolog is an open forum to: • Discuss practical issues and strategies associated with the development of both formal and informal ontologies used in business • Identify ontological engineering approaches that might be applied to the UBL effort (and by extension, to the broader domain of eBusiness standardization efforts) • What holds us together: Our Core Value • Developing Shared Understanding • Openness • Advancing the practice of semantic engineering • Doing meaningful work and making a difference with it

  6. [CCT-Rep] project mission • Goal: To influence the adoption of ontologies and ontological engineering methodologies in eBusiness standards.    [0141] • Mission: To establish an Ontological Basis for ebXML Core Component Types ("CCT") using the methodologies the [ontolog-forum] has established for the UblOntology project; engage representation and participation from the ontological engineering and standards community (particularly from the standards community that developed and implemented the core component types); and, to produce a reference CCT ontology and a report on findings and recommendations for submission to UN/CEFACT CCTS (and possibly the Harmonization) working group(s). • Deliverables: • a reference ontology of approved ebXML Core Component Types ("CCTONT") • a report on findings and recommendations regarding the current CCT specifications

  7. What is a CCT ? • … this story goes back to the 1970’s and 80’s … to EDI:Electronic Data Interchange • CC:BCC, CCT, BIE, ABIE, … • CC = Core Component • BCC = Basic Core Component (e.g. “Person. Name. Text”) • ASCC = Association Core Component (e.g. “Person. Residence. Address”) • CCT = Core Component Type = A Core Component, which consists of one and only one Content Component, that carries the actual content plus one or more Supplementary Components giving an essential extra definition to the Content Component. Core Component Types do not have Business Semantics. (e.g. “Text. Type”) • ACC = Aggregate Core Component (e.g. “Address. Details”) • CCTS:Core Component Technical Specification - Part 8 of the ebXML Framework • ebXML:Joint UN/CEFACT-OASIS initiative; began Fall 1999; 18 months • UN/CEFACT = United Nations Center for Trade Facilitation and Electronic Business • OASIS = Organization for the Advancement of Structured Information Standards • CCTS Implementers:UN/CEFACT-TBG’s; Joint UN/CEFACT-ISO efforts (e.g. ISO-TC154; WCO/UNTDED; UNeDocs); EAN.UCC; OAGI, SWIFT; OASIS-UBL; … • UN/CEFACT – TBG17:Core Component Harmonization working group

  8. [CCT-Rep] Project WIP(1) – CCTS excerpt

  9. The Ontolog [cctont] & [ublont] Approach • Have the expressivity worthy of a basic industry reference standard • To develop unambiguous, consistent, computable standards that are defined in logic; intended to support future machine-to-machine interaction (when current standards are generally defined in human languages and require human beings to interpret them.) • Normative Ontology to be defined in First Order Logic and axioms -- implemented in KIF (SUO-KIF to be exact) • Extending our Business Domain Ontology from the SUMO Upper Ontology (and MILO) • Expressing the Normative Ontology in multiple other, more pervasive representations (either in “lossless” or “lossy” mappings, as long as we are fully aware).

  10. [CCT-Rep] Project Status • Focusing work on the CCTS approved CCT’s: 10 Core Component Types, and their 44 Supplementary Components • 8 step project plan [017] • 15 members (active and observing) so far; broad representation: • from multiple standards working groups; government and citizen efforts; ontologists and domain experts; … • 2nd iteration of the mapping to SUMO in progress

  11. [CCT-Rep] Project WIP(2) – SUMO / SIGMA-kee

  12. [CCT-Rep] Project WIP(3) – Worksheet & CCTrep.kif

  13. [CCT-Rep] Project WIP(4) – example: defining URI

  14. [CCT-Rep] Project WIP(5) – CCT-to-SUMO Mapping

  15. CCT-Representation Project (summary-1) • Develop a ebXML CCT ontology in KIF (extending from SUMO) • Gain the opportunity to work with people from UBL; OAG; NIST; UN/CEFACT-CCTS, TBG-17; …etc. • From lessons learned in the exercise, provide meaningful and actionable input into the eBusiness standards community

  16. CCT-Representation Project (summary-2) • Take the normative KIF-based CCT-ontology, and expressed them in (either in “lossless” or “lossy” mappings, as long as we are fully aware): • Protégé • OWL • UML Class Diagram • UML 2 / OCL • XML / XSD • RDF/S • SQL • … etc. • Capitalize on the KIF-Protégé project and the power and capabilities of Protégé to provide some of the mapping

  17. An opportunity and challenge • This is a hard problem, but we believe it is solvable • We are making an attempt to introducing the ontological engineering approach to the eBusiness standards community • A chance to influence the future of eBusiness standards • This is one unique opportunity to really make a difference • Experience and provide an example of doing good work in a virtual Community of Practice setting • Solicitation: be a part of this very meaningful and challenging project, especially if you are master of any one or a combination of the skill sets that we are after (see: slide#16).

  18. Resources & Links • The [ontolog-forum] • To join us, see: ontolog membership • The [CCT-Representation] Project HomePage • CCTS – Core Component Technical Specification, v2.01 dated 2003-11-15 (UN/CEFAT) • UBL – Universal Business Language, v1.0 Committee Draft dated 2004-05-01 (OASIS) • SUMO, SIGMA-kee, … see: [OntologyPortal] • the Collaborative Work Environment (the cim3.net ‘CWE’) we are doing our work on, see: [a recent presentation]

More Related