1 Collaborating to Develop an Ontological Basis for E-Business Standards at the OASIS UBL TC Face-to-face Meeting Date: Nov. 1~5, 2004 Santa Clara, CA (Sun Microsystems Campus) by Peter P. Yim Peter P. Yim Nov. 04, 2004 ( v 1.00 )

ppy/Protege-Ontolog_presentation--PeterYim_ ppt/Jul of 18 Outline BackgroundBackground  Purpose of this presentation  What do Standards, Ontologies & Collaboration have in Common?  Getting back to basics The “CCT-Representation” projectThe “CCT-Representation” project  [CCT-Rep] project mission  What is a CC (“Core Component”) ?  Our approach  a Status Report An unprecedented opportunity and challengeAn unprecedented opportunity and challenge  a solicitation

ppy/Protege-Ontolog_presentation--PeterYim_ ppt/Jul of 18 Purpose of this presentation Introducing [CCT-Representation] -- one of the projects being undertaken by the [ontolog] communityIntroducing [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 fleshThrough 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 communityShare 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 projectSolicit participation and contribution to this very meaningful project

ppy/Protege-Ontolog_presentation--PeterYim_ ppt/Jul of 18 What do Standards, Ontologies & Collaboration have in Common? Common goalsCommon goals  Interoperability (working together)  Better efficiency (time & cost) Adopting best practicesAdopting best practices Eliminating duplicated effortsEliminating duplicated efforts  Optimal Effectiveness (getting things done; responsive) Common approachCommon 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)

ppy/Protege-Ontolog_presentation--PeterYim_ ppt/Jul of 18 Back to basics: Ontolog is an open forum to: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  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 ValueWhat 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

ppy/Protege-Ontolog_presentation--PeterYim_ ppt/Jul of 18 [CCT-Rep] project mission Goal: To influence the adoption of ontologies and ontological engineering methodologies in eBusiness standards. [0141]Goal: To influence the adoption of ontologies and ontological engineering methodologies in eBusiness standards. [0141]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).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).UblOntology  Deliverables: a reference ontology of approved ebXML Core Component Types ("CCTONT")a reference ontology of approved ebXML Core Component Types ("CCTONT") a report on findings and recommendations regarding the current CCT specificationsa report on findings and recommendations regarding the current CCT specifications

ppy/Protege-Ontolog_presentation--PeterYim_ ppt/Jul of 18 What is a CCT ? … this story goes back to the 1970’s and 80’s … to EDI: Electronic Data Interchange… this story goes back to the 1970’s and 80’s … to EDI: Electronic Data Interchange CC: BCC, CCT, BIE, ABIE, …CC: BCC, CCT, BIE, ABIE, … CC = Core ComponentCC = 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 FrameworkCCTS: Core Component Technical Specification - Part 8 of the ebXML Framework ebXML: Joint UN/CEFACT-OASIS initiative; began Fall 1999; 18 monthsebXML: Joint UN/CEFACT-OASIS initiative; began Fall 1999; 18 months UN/CEFACT = United Nations Center for Trade Facilitation and Electronic BusinessUN/CEFACT = United Nations Center for Trade Facilitation and Electronic Business OASIS = Organization for the Advancement of Structured Information StandardsOASIS = 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; …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 groupUN/CEFACT – TBG17: Core Component Harmonization working group

ppy/Protege-Ontolog_presentation--PeterYim_ ppt/Jul of 18 [CCT-Rep] Project WIP (1) – CCTS excerpt

ppy/Protege-Ontolog_presentation--PeterYim_ ppt/Jul of 18 The Ontolog [cctont] & [ublont] Approach To develop unambiguous, robust, 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.)To develop unambiguous, robust, 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)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)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).Expressing the Normative Ontology in multiple other, more pervasive representations (either in “lossless” or “lossy” mappings, as long as we are fully aware).

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

ppy/Protege-Ontolog_presentation--PeterYim_ ppt/Jul of 18 [CCT-Rep] Project WIP (2) – SUMO / SIGMA-kee

ppy/Protege-Ontolog_presentation--PeterYim_ ppt/Jul of 18 [CCT-Rep] Project WIP (3) – Worksheet & CCTrep.kif

ppy/Protege-Ontolog_presentation--PeterYim_ ppt/Jul of 18 [CCT-Rep] Project WIP (4) – example: defining URI

ppy/Protege-Ontolog_presentation--PeterYim_ ppt/Jul of 18 [CCT-Rep] Project WIP (5) – CCT-to-SUMO Mapping

ppy/Protege-Ontolog_presentation--PeterYim_ ppt/Jul of 18 CCT-Representation Project (summary-1) Develop a ebXML CCT ontology in KIF (extending from SUMO)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.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 communityFrom lessons learned in the exercise, provide meaningful and actionable input into the eBusiness standards community

ppy/Protege-Ontolog_presentation--PeterYim_ ppt/Jul of 18 Take the normative KIF-based CCT-ontology, and expressed them in (either in “lossless” or “lossy” mappings, as long as we are fully aware):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éProtégé OWLOWL UML Class DiagramUML Class Diagram UML 2 / OCLUML 2 / OCL XML / XSDXML / XSD RDF/SRDF/S SQLSQL … etc.… etc. Capitalize on the KIF-Protégé project and the power and capabilities of Protégé to provide some of the mappingCapitalize on the KIF-Protégé project and the power and capabilities of Protégé to provide some of the mapping CCT-Representation Project (summary-2)

ppy/Protege-Ontolog_presentation--PeterYim_ ppt/Jul of 18 An opportunity and challenge This is a hard problem, but we believe it is solvableThis 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 communityWe are making an attempt to introducing the ontological engineering approach to the eBusiness standards community A chance to influence the future of eBusiness standardsA chance to influence the future of eBusiness standards This is one unique opportunity to really make a differenceThis is one unique opportunity to really make a difference Experience and provide an example of doing good work in a virtual Community of Practice settingExperience 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).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).

ppy/Protege-Ontolog_presentation--PeterYim_ ppt/Jul of 18 Resources & Links The [ontolog-forum]The [ontolog-forum]ontolog-forum To join us, see: ontolog membershipTo join us, see: ontolog membershipontolog membershipontolog membership The [CCT-Representation] Project HomePageThe [CCT-Representation] Project HomePageCCT-Representation CCTS – Core Component Technical Specification, v2.01 dated (UN/CEFAT)CCTS – Core Component Technical Specification, v2.01 dated (UN/CEFAT)Core Component Technical Specification, v2.01Core Component Technical Specification, v2.01 UBL – Universal Business Language, v1.0 Committee Draft dated (OASIS)UBL – Universal Business Language, v1.0 Committee Draft dated (OASIS)Universal Business Language, v1.0 Committee DraftUniversal Business Language, v1.0 Committee Draft SUMO, SIGMA-kee, … see: [OntologyPortal]SUMO, SIGMA-kee, … see: [OntologyPortal]OntologyPortal the Collaborative Work Environment (the cim3.net ‘CWE’) we are doing our work on, see: [a recent presentation]the Collaborative Work Environment (the cim3.net ‘CWE’) we are doing our work on, see: [a recent presentation]a recent presentationa recent presentation