1 / 27

Ontology Summit 2016: Semantics for Interoperability Ecosystems

This summit discusses the challenges, processes, and methodologies in achieving semantic interoperability across domains, and presents strategies and approaches to facilitate semantic interoperability. It also highlights the importance of ontology design patterns, reference ontologies, and common conceptual models.

reder
Download Presentation

Ontology Summit 2016: Semantics for Interoperability Ecosystems

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. Ontology Summit 2016Ontologies within Semantic Interoperability EcosystemsFraming the Conversation: Communique Discussion Points(working draft/please do not distribute)April 28, 2016 Donna Fritzsche & Michael Gruninger <insert all authors>

  2. Communique Outline • Introduce & Present Key Findings • Contextualize the Material: Past Summit Topics • Discuss in Detail A. Thoughts & Dialogue <insert MG’s questions/discussion points> B. Challenges C. Processes & Methodologies D. Conversational Framework • Present Final Recommendations A. Strategies & Approaches which Facilitate Semantic Interoperability B. Tactics with Facilitate Semantic Interoperability Ontology Summit 2016 Discussion

  3. Introduce & Present Key Findings

  4. Introduction <insert key points> Ontology Summit 2016 Discussion

  5. Communicate Summit Highlights THEMES Heterogeneity Problem Achieving Semantic Interoperability across domains is difficult. There are only a few successes. There is low adoption rate and reuse of ontology. We need integrated conceptual modeling and KE tools to build and bridge ontologies. SEMANTIC MODELS & TOOLS Reference Ontologies Crosswalks/Mappings Bridge Ontologies Ontology Design Patterns Common Conceptual Models (such as VIVO) PROCESSES & ACTION STEPS Alignment of Project Requirements (User, Stakeholder, Technical) with Semantic Model functionality Integration Techniques Development of Process and Degree of Cooperation/Collaboration between groups developing Semantic Models. Vocabulary Harmonization “Identifying & defining data owners” “Create consistent and integrated vocabularies at the group and organizational level” Ontology Summit 2016 Discussion

  6. Communicate Summit Highlights MEASURES & QA “How do we verify and validate these structures (ontology efficacy)? (i.e. if an ontology is created to do some thing, x; who verifies it actually does, x?)” Consider: • Accuracy/ Correctness • Completeness/Scope • Expressivity • Integrity • Clarity • Usefulness • Complexity • Learnability/Usability • Translatability Discuss Markers for Successful Semantic Interoperability (ref Patil) • Fewer User Decisions • Less Contextual Intelligent Information • Increased Structured Integration with other Domains Discuss SCOPE Ontology Summit 2016 Discussion

  7. Participate in the Semantic Interoperability Ecosystem DEVELOPMENT PROCESS & SCOPE Adopt Pilot Programs “Early, small deliveries that demonstrate value help get more and more acceptanceenthusiasticsupporttrue engagement and active participation “ “Roll out needs to start with one domain area / deliverable, then two in parallel, then scale up from there as policies, methodology, metrics and related processes are established and mature” “Select deliveries based on high value use cases and regulatory importance, determined via business analysis” GOVERNANCE & COLLABORATION “No agreement or controlling body or process to coordinate efforts and/or to validate ontologies and their axioms” “Centralization of the management and governance of the vocabulary is critical to ensure harmonization, coordinated development, quality, continuous improvement “ Identify roles, actions and responsibilities that are appropriate to the governance and collaboration tasks at hand. (DF – paraphrased) EXTERNAL REGULATIONS “By their own admission, about half of the Global-Systematically Important Banks (G-SIBs) are going to fail to comply with Basel III Risk Data Aggregation and Reporting Requirements (RDARR)* TOOLS State of Current Tools and Future Needs. Most presenters indicated a need for better tools. “Editing and Visualization of Large-scale ontologies poses new challenges for existing ontology tools.” Relationship to and efficiency of conventional reasoning tools. Ontology Summit 2016 Discussion

  8. Summarize Key Observations by Domain GEOSCIENCES Achieving Semantic Interoperability across domains is difficult. eHEALTH External Regulations PHARMA & BIOSCIENCES External Regulations Ontology Summit 2016 Discussion

  9. Summarize Key Observations by Domain ENGINEERING & MANUFACTURING FINANCE External Regulations to meet. “Some trouble spots in Risk Managements: • Data Architecture & IT Infrastructure • Accuracy & Integrity: • Timeliness • Adaptability” RETAIL … Ontology Summit 2016 Discussion

  10. Summarize Key Observations regarding Development Environments How would we like to frame this conversation. Need input. OPEN SOURCE TOOLS COMMERCIAL TOOLS CLOUD … Ontology Summit 2016 Discussion

  11. Contextualize the Material:Past Summit Topics

  12. The Role Of Upper Ontologies (2006)Examine, Question and Extend Past Summit Findings Domain: Earth Sciences (is this statement generalizable?) Upper-level and many domain ontologies are important to such SI but there are challenges: Challenge: There seems to be no one taxonomic hierarchy we can agree on. Many of the upper and domain ontologies are • hard to understand or have too many terms, • are too abstract, • with too complicated axioms to understand and yet • remain too far from real data. Many of the upper and domain ontologies impose ontological commitments that may not be acceptable by all interested parties who have 'local' vocabularies and meanings. Like AI systems in the past they may also be too brittle - small changes are not easily incorporated or compromise the semantics. Recommendation: ?(bridging concepts/vocabs)? Update to 2006 Findings: Ontology Summit 2016 Discussion

  13. Ontology, Taxonomy, Folksonomy: Understanding the Distinctions (2007)Examine, Question and Extend Past Summit Findings Domain: Current State: Strength: Challenge: Recommendation: Update to 2007 Findings: Ontology Summit 2016 Discussion

  14. Towards Ontology-based Standards (2009)Examine, Question and Extend Past Summit Findings Domain: Finance/Risk Management Current State: (*slide 14/Kendall) • BCBS 239 requires “integrated data taxonomies and architecture across the • banking group” – i.e., a “ground truth” for risk data • A vocabulary provides the basis for ground truth. It is comprised of metadata and a unified, logical, consistent approach to concept identification, naming, representation • An ISO 704 based approach provides the rigor required to develop the terminology required as the starting point for a compliant business vocabulary • Analysis of relationships and other business rules, mapping to FIBO as appropriate, and identification of gaps where further ontology development is needed is the result of step 4 Recommendation: DF: Apply above current state considerations to other domains. There is strength and appeal regarding the idea of “ground truth” vocabularies. Update to 2009 Findings: Domain: Earth Sciences (is this statement generalizable?) Challenge: “Various types of standards that do exist are, for the most part, heterogeneous, meaning they: • are mostly fragmented and disconnected, describing potentially relatable concepts • lack a grounding in foundational semantics. • may use the same or similar terms but with differences in semantics. • are described using different formal (or non-formal) languages. As a result major problems exist when standard driven efforts and products are combined reflecting differences in conceptualization, semantic drift upon new problem formulation.” Recommendation: * Some glue such as via a reference ontology is needed to integrate and harmonize these.” Update to 2009 Findings: Ontology Summit 2016 Discussion

  15. Towards Ontology-based Standards (2009)Examine, Question and Extend Past Summit Findings Domain: Retail Current State Observation: Use of Schema.org Strength: Challenge: Recommendation: Update to 2009 Findings: Ontology Summit 2016 Discussion

  16. Ontology for Big Systems (2012)Examine, Question and Extend Past Summit Findings Domain: Current State: Challenge: Recommendation: Update to 2012 Findings: Domain: Current State: Challenge: Recommendation: Update to 2012 Findings: Ontology Summit 2016 Discussion

  17. Ontology Evaluation across the Ontology Lifecycle (2013) Examine, Question and Extend Past Summit Findings Domain: Current State: Challenge: Recommendation: Update to 2013 Findings: Ontology Summit 2016 Discussion

  18. Big Data and Semantic Web Meet Applied Ontology (2014)Examine, Question and Extend Past Summit Findings Domain: Current State: Challenge: Recommendation: Update to 2014 Findings: Domain: Current State: Challenge: Recommendation: Update to 2014 Findings: Ontology Summit 2016 Discussion

  19. The Internet of Things: Toward Smart Networked Systems and Societies (2015)Examine, Question and Extend Past Summit Findings Domain: Current State: Challenge: Recommendation: Update to 2015 Findings: Ontology Summit 2016 Discussion

  20. Discuss in Detail

  21. In-Depth Discussion (Deep dive on several topics highlighted in earlier slides) Thoughts & Dialogue • The Role of Ontologies • Ontology Design • Terminology & Issues • <Key Dialogue from the Mailing List> Challenges • Heterogeneity Problem • Insufficient Tools • Appropriate Level of Collaboration & Governance Processes & Methodologies • Use Case & Requirement Alignment with Semantic Model/Ontology (right tool for the job) • Vocabulary Harmonization • Bridging Vocabularies • Domain Vocabularies Conversational Framework • Characterization of Use Cases and Requirements • Characterization of Semantic Models (what functionality do they offer consuming applications/ecosystem participants) • Measures of Appropriate Semantic Interoperability • Conditions and Requirements for Successful SI Projects Ontology Summit 2016 Discussion

  22. Present Final Recommendations

  23. Final Recommendations Strategies & Approaches which Facilitate Semantic Interoperability <insert> Tactics which Facilitate Semantic Interoperability <insert> Ontology Summit 2016 Discussion

  24. Appendix

  25. Ontology Summit 2016 Process • Present a series of virtual talks highlighting projects from different domains • Examine, question and extend past summit findings including but not limited to communiqués addressing: • The Role of Upper Ontologies (2006) • Ontology-based Standards (2009) • Ontology Evaluation across the Ontology Lifecycle (2013) • The Internet of Things: Toward Smart Networked Systems and Societies (2015) • Abstract a conversational toolkit from the sessions, supported with examples from the sessions • Capture the results in the 2016 Summit Communiqué, with expanded supporting material provided on the web • Conclude the summit theme at the in-person Symposium Ontology Summit 2016 Discussion

  26. Framing the Conversation Panel: Goals Our goal is to build a shared framework which will facilitate discussions regarding the role of ontologies within semantic interoperability ecosystems. We will discuss themes, models, processes, functionality, considerations, measures, and scope which shed light on or help to communicate the Semantic Interoperability Ecosystem to a broaderaudience. We will purposely focus on the role of ontologies within these frameworks. Examples will be used to illustrate our points. It is hoped that the results of this session will help to frame and target the discussions in the domain-specific tracks to follow in the coming weeks. Together with findings from previous summits, this framework will provide a foundation and help facilitate and direct conversation. Ontology Summit 2016 Discussion

  27. Communique Discussion • Abstract a conversational toolkit from the sessions, supported with examples from the sessions. • Work towards a shared framework which will facilitate discussions regarding the role of ontologies within semantic interoperability ecosystems. • Consider themes, models, processes, functionality, considerations, measures, and scope which shed light on or help to communicate the Semantic Interoperability Ecosystem to a broader audience. • Discuss Pros, Cons and Context of Use for various models and approaches. • Time allowing, continue to examine, question and extend past summit findings including but not limited to communiqués addressing: • The Role of Upper Ontologies (2006) • Ontology-based Standards (2009) • Ontology Evaluation across the Ontology Lifecycle (2013) • The Internet of Things: Toward Smart Networked Systems and Societies (2015) Ontology Summit 2016 Discussion

More Related