1 / 14

ONION Ontologies In Ontology

ONION Ontologies In Ontology. Community of Practice Leader CarlMattocks@checkmi.com. What is “Ontologies In Ontology”. ONION is an open source semantic reference tool for the business of information technology (many terms have novel or dual meanings)

johnathons
Download Presentation

ONION Ontologies In Ontology

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. ONION Ontologies In Ontology Community of Practice Leader CarlMattocks@checkmi.com

  2. What is “Ontologies In Ontology” • ONION is an open source semantic reference tool for the business of information technology (many terms have novel or dual meanings) • ONION is structured as a Community of Practice (COP) ontology that has multiple, domain specific, layers. The content of each layer is scoped by the set of IT topics that are relevant to a particular Community of Interest (COI) or Community of Action (COA). • Foundational layers of the ONION are aligned with the public specifications of: IT Service Management Best Practice; IT Control Frameworks; Information Security; IT Auditor Control Objectives ; and Service Oriented Architecture (SOA). • Classification schema(s), the ONION core uses explicit links to controlled vocabularies as they become publicly available: Especially, those for IT Infrastructure (classes, properties, methods, values) and Open Source Components (XML elements, attributes)

  3. Objective is ePowerAssist • Quicker, greater maturity eBiz / eGov / eEnterprise / .. by providing critical mass componentry • Guideline Actuation • open source specification • open source software • Standard Operating ProcedureEfficacy • open source language • SOA SOP agent • Ontology Evolution • open source tool • vendor accountable product

  4. Quality Management Maturity Uncertainty, Awakening, Enlightenment, Wisdom, Certainty Software Maturity Initial, Repeatable, Defined, Managed, Optimal Supplier Maturity Adversarial, Transitional, Partnership ISO 9004 Maturity No Formal, Reactive, Stable Formal, Continuous Improvement, Best Practice Towards Component Maturity COMMUNICATE PLAN DO ACT CHECK

  5. Acknowledging System Semantics System Interoperability IT Semantics OWL Ontology + Business Process Patterns RDFS / UML / Topic Map / UNSPSC DTD / XML Schema / Dublin Core Object Oriented Model / Thesaurus Info Engineering Model Data Dictionary / ERD Data Usage Semantics Service Quality

  6. Discourse in a Service Oriented World • Shared Understanding • Governance • Assurance • Interoperability • Standard for Communications • Human & Software Agents • Multiple Interdependent Services

  7. Slices of Practice, Action, Audit • OGC ITIL, ISO 20000 • IT Service Management • ISACA COBIT Framework • e.g. Statement on Auditing Standard 94 • ISO/IEC 27001, ISO 17799 • Information Security • COSO Int. Control Framework • Audit Control Objectives • e.g. SOX 404, SAS 48, SAS 70 • OASIS BCM Framework • CoI procedures effective interoperability mechanisms

  8. Single Reference Model • Assertions of Activities, Flows, KPIs • Data Dictionary items • Class / Element / Datatype • Events • State Transition Values • Templates • Forms, Messages, Archetypes • Data Model Subject Areas • CMDB - configuration • CPDB - capacity

  9. Ref. Distributed Management Task Force, Inc Object Classification • Encapsulate Common Information • Hierarchical, Object Oriented • Incorporate CIM Scope • Extend Core & Association Classes • ManagedElement, ManagedSystemElement, LogicalElement, System, Service, …. • Dependency, Component, LogicalIdentity, ...

  10. Actionable Knowledge Gap • Description Logics • Encode Concepts / rich class and Sets of objects • Enable Active Inference e.g. automatic classification • Explain Semantic reasoning with Metadata and Data • Evolve Role knowledge via relationships • Conjunction • Important when understanding Configuration • Disjunction • Critical when a change of state is a trigger for action • Negation, Exists / Value (restriction) • Significant when process completion is the measure of success Description Logics Frame based systems OIL XML & RDS

  11. Open Source Component

  12. Outcome : XML for Understanding ? • OWL (WC3) • Metadata & data providing formal conceptualization of a particular domain of interest. Used both by humans and systems to aid information exchange and integration • Common Logic XCL (ISO/IEC) • XML-based syntax for common logic, designed for use by mechanical systems to interchange logical content Image from HubbleSite, NASA, and the Space Telescope Science Institute

  13. ImplementationLayer . Implementation Upper Semantic Alignment Solution Envisioning Memorandum of Understanding (CPP/A) Appendix A: Interface Specification Self-Synchronization Form Project Mgmt: Cost / Schedule / Risks, etc. Identify Event  Condition (Rule) Transaction Collaboration Appendix B: Terms Alignment Determine Tactics: Use Case / Scope / Transition Identify Initiative Champions Context netCentric Conceptual Model Base Design & Development (Integration/Programming) Attribute; Mandatory vs. Optional MetaLink Phased Demonstrations Requirements  Test Plan, Data, & Testing Codelist Sub/Superset Link Interface(Publish/Subscribe, etc) Deploy Services How do you know the initiative is done? Physical – Content Assembly Training Publish Feedback – Lessons Learned Extension Layer Condition (Rule) Outreach External Alignment: Stds, Specs & Frameworks Communication Alignment - Maps Identify Community of Interest (CoI) Development Training Materials Perform Industry Survey of Leading Practices Stds, Specifications and Frameworks Identify Demo / Solution CoI’s Specific Requirements Principles Develop/Join Social Working Environment Baseline Architecture for Business Artifacts for Stds Transition Activities Brochure Per Community Baseline Architecture for Required Technologies for Stds Collaboration - Collection Work Derive Community Requirements Develop Guidelines / Alignments - Maps Brochures - Press Home Documentation Is A Business Layer Business Case Analysis Business Process Business Intelligence Business Objects Vision Statement Define Value-chain Visibility Strategy Reporting Requirements Publish Identify Stakeholders Identify Facets (Classification) Define Events/Triggers Pinpoint Challenges / Issues Include Facet in Navigation Framework Identify Form/Transaction Service Assumptions  Assertion Evaluation Define Slice & Dice (Filter) Tactics Business Object Identification Address Feasibility, Risk, Cost Benefit Dashboard Loaders Discover/Define Services List Success Metrics Per Stakeholder Dashboard Setup & Security Define Roles & Security Determine Scope: In Scope / Out of Scope Exceptions & Notifications Define Workflow/Choreography Part of Conceptual Layer Story Lower Semantic Alignment Ontology Describe Scenarios & Interface Types Identify Business Concepts / Atomics Person Develop Concept Identify Authoritative Sources Pathway Define Concept Location Identify Like/Exact Terms Patterns Develop/Add to Terms Service Recognize Business Model Property Add/Converge/Link Ontologies Business Centric Methodology Checklist • Concept • Declaration • Taxonomy Develop Proposal Codify/List Concepts Baseline Capability Inventory Terms Service Determine (Meta) Link Opportunities Enterprise Architecture Fit / Compliance Outcome : XML for CoI Procedures ?

  14. ONION CoP is an open forum http://ontolog.cim3.net/cgi-bin/wiki.pl?MeetingsCalls

More Related