onion ontologies in ontology community of practice leader
DESCRIPTION
3 ONION Ontologies In Ontology ePowerAssist Objective is ePowerAssist Quicker, greater maturity eBiz / eGov / eEnterprise /.. by providing critical mass componentry –Guideline Actuation open source specification open source software –Standard Operating Procedure Efficacy open source language SOA SOP agent –Ontology Evolution open source tool vendor accountable productTRANSCRIPT
ONION Ontologies In Ontology
Community of Practice Leader [email protected]
2
ONION Ontologies In Ontology
ePowerAssist
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
ONION Ontologies In Ontology
ePowerAssist
Objective is ePowerAssist
• Quicker, greater maturity eBiz / eGov / eEnterprise / .. by providing critical mass componentry
– Guideline Actuation• open source specification• open source software
– Standard Operating Procedure Efficacy• open source language• SOA SOP agent
– Ontology Evolution• open source tool• vendor accountable product
4
ONION Ontologies In Ontology
ePowerAssist
Towards Component Maturity
• 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
PLAN
ACT
COMMUNICATE
DO
CHECK
5
ONION Ontologies In Ontology
ePowerAssist
Acknowledging System SemanticsIT Semantics
Data Usage Semantics
System Interoperability
Service Quality
Data Dictionary / ERD
Info Engineering Model
Object Oriented Model / Thesaurus
DTD / XML Schema / Dublin Core
RDFS / UML / Topic Map / UNSPSC
OWL Ontology + Business Process Patterns
6
ONION Ontologies In Ontology
ePowerAssist
Discourse in a Service Oriented World
• Shared Understanding– Governance– Assurance– Interoperability
• Standard for Communications– Human & Software Agents– Multiple Interdependent Services
7
ONION Ontologies In Ontology
ePowerAssist
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
ONION Ontologies In Ontology
ePowerAssist
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
ONION Ontologies In Ontology
ePowerAssist
Object Classification
• Encapsulate Common Information – Hierarchical, Object Oriented– Incorporate CIM Scope
• Extend Core & Association Classes – ManagedElement, ManagedSystemElement,
LogicalElement, System, Service, …. – Dependency, Component, LogicalIdentity, ...
Ref. Distributed Management Task Force, Inc
10
ONION Ontologies In Ontology
ePowerAssist
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
OIL
XML & RDS
Frame based systems
Description Logics
11
ONION Ontologies In Ontology
ePowerAssist
Open Source Component
12
ONION Ontologies In Ontology
ePowerAssist
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
ONION Ontologies In Ontology
ePowerAssist
Conceptual Layer
Business Layer
Extension Layer
Implementation Layer
Identify Demo / Solution CoI’s Specific Requirements
External Alignment: Stds, Specs & Frameworks
Baseline Architecture for Business Artifacts for Stds
Perform Industry Survey of Leading Practices
Baseline Architecture for Required Technologies for Stds
Principles Training Materials
Transition Activities
Implementation
Determine Tactics: Use Case / Scope / Transition
.
Project Mgmt: Cost / Schedule / Risks, etc.
Design & Development (Integration/Programming)Requirements Test Plan, Data, & Testing
Deploy
Lower Semantic Alignment
Identify Authoritative Sources Identify Business Concepts / Atomics
Business Object Identification
Develop/Add to Terms Service Patterns
Discover/Define Services
Reporting Requirements
Identify Form/Transaction
Recognize Business Model
Business Process
Define Workflow/ChoreographyDefine Roles & Security
Define Events/Triggers
Develop Guidelines / Alignments - Maps
Describe Scenarios & Interface Types
Outreach
Identify Like/Exact Terms
Enterprise Architecture Fit / Compliance
Property
Location
Person
Publish
AddressService
HomeWork
Part of
Is A
Terms Service
• Concept• Declaration•Taxonomy
Stds, Specificationsand Frameworks
Transaction
BaseBase
Identify Community of Interest (CoI) Development
Condition (Rule)
Alignment - Maps
Identify Stakeholders
Business Case Analysis
Feasibility, Risk, Cost Benefit
Determine Scope: In Scope / Out of Scope List Success Metrics Per Stakeholder
Vision Statement
Pinpoint Challenges / Issues
Identify Initiative Champions
Solution Envisioning
ContextCollaboration
ServicesLink
Self-Synchronization
MetaLink
Publish
Ontology
Business Objects
Form
Develop Proposal
PhasedDemonstrations
Brochures - Press Collaboration - Collection
Documentation
Communication
Develop Concept
Baseline Capability Inventory
Define Concept
Add/Converge/Link OntologiesCodify/List Concepts
Define Slice & Dice (Filter) TacticsDashboard Loaders
Identify Facets (Classification) Define Value-chain Visibility Strategy
Business Intelligence
Dashboard Setup & Security
Include Facet in Navigation Framework
netC
entri
c C
once
ptua
l Mod
el
Upper Semantic Alignment
Identify Event Condition (Rule)
Attribute; Mandatory vs. Optional Appendix B: Terms Alignment
Codelist Sub/Superset
Physical – Content AssemblyTraining
Memorandum of Understanding (CPP/A) Appendix A: Interface Specification
Interface (Publish/Subscribe, etc)
Develop/Join Social Working Environment
Assumptions Assertion Evaluation
Determine (Meta) Link Opportunities
Exceptions & Notifications
Feedback – Lessons Learned
Brochure Per Community
Pathway
Story
Derive Community Requirements
How do you know the initiative is done?
Business CentricMethodologyChecklist
Outcome : XML for CoI Procedures ?
ONION CoP is an open forum
http://ontolog.cim3.net/cgi-bin/wiki.pl?MeetingsCalls