Dr. Leo Obrst MITRE March 14, 2006 Upper Ontology Summit Issues: Opportunities and Challenges Tuesday, March 14, 2006 Upper Ontology Summit NIST.

Slides:



Advertisements
Similar presentations
Upper Ontology Summit March 14, 2006 Michael Gruninger Semantic Technologies Laboratory University of Toronto.
Advertisements

Units of Measure - How many standards?. 2 What is a standard? A standard is nothing more than an agreement across a particular community of interest,
Upper Ontology Summit Tuesday March 14 The BFO perspective Barry Smith Department of Philosophy, University at Buffalo National Center.
Dr. Leo Obrst MITRE March 14, 2006 Upper Ontology Summit Issues: Opportunities and Challenges Tuesday, March 14, 2006 Upper Ontology Summit NIST.
2008 Ontology Summit Launch Event February 7, 2008 OntologySummit2008 is a joint NIST-Ontolog-NCOR initiative, supported by multiple communities and a.
Dr. Leo Obrst Information Semantics Command & Control Center July 17, 2007 Ontologies Can't Help Records Management Or Can They?
Languages & Inference Appropriate layering Do we need a logic? Do we need Description Logic? Legacy data; database storage vs inference Tolerant/anytime.
David J. Sammons, Dean UF International Center. Southern Association of Colleges and Schools: SACS is our regional accrediting authority. The last SACS.
Upper Ontology Summit March 15, 2006 Michael Gruninger Semantic Technologies Laboratory University of Toronto.
Ontologies: Dynamic Networks of Formally Represented Meaning Dieter Fensel: Ontologies: Dynamic Networks of Formally Represented Meaning, 2001 SW Portal.
Data Science for Business: Semantic Verses Dr. Brand Niemann Director and Senior Data Scientist Semantic Community
Software Connectors Software Architecture. Importance of Connectors Complex, distributed, multilingual, modern software system functionality and managing.
C-OWL: contextualizing ontologies Fausto Giunchiglia October 22, 2003 Paolo Bouquet, Fausto Giunchiglia, Frank van Harmelen, Luciano Serafini, and Heiner.
WSDL Park, Hyunho 2005/07/28. Introduction Web services have been around for a long time in primitive form. Limitation of the primitive form:
Fusion and Automation Fusion and Automation Human Cognitive and Visualization Issues Jean-Remi Duquet Marc Gregoire Maura Lohrenz Kesh Kesavados Elisa.
Overview of OASIS SOA Reference Architecture Foundation (SOA-RAF)
OASIS Reference Model for Service Oriented Architecture 1.0
Ontology Library Systems: The key to successful Ontology Re-use Ying Ding & Dieter Fensel Supported by OnToKnowledge.
Where are the Semantics in the Semantic Web? Michael Ushold The Boeing Company.
Semantics For the Semantic Web: The Implicit, the Formal and The Powerful Amit Sheth, Cartic Ramakrishnan, Christopher Thomas CS751 Spring 2005 Presenter:
S&I Data Provenance Initiative Presentation to the HITSC on Data Provenance September 10, 2014.
Web Service Architecture Part I- Overview and Models (based on W3C Working Group Note Frank.
Systems Engineering Foundations of Software Systems Integration Peter Denno, Allison Barnard Feeney Manufacturing Engineering Laboratory National Institute.
CORDRA Philip V.W. Dodds March The “Problem Space” The SCORM framework specifies how to develop and deploy content objects that can be shared and.
Towards a hypothesis for the Mediator’s Abroad project Di Bretherton ACPACS 1/8/2007.
Objective- and Strategic Analysis
BY Karen Liu, Ph. D. Indiana State University August 18,
Reasoning with context in the Semantic Web … or contextualizing ontologies Fausto Giunchiglia July 23, 2004.
Shelter Training 08b – Belgium, 16 th –18 th November, 2008 based on content developed by p This session describes the benefits of developing a strategic.
Cross Cutting 1 Project Governance Steering Committees of Projects / Project Advisory Boards Zoltán Mihók – COD Serbia Handicap International seminar«
TFTM Interim Trust Mark/Listing Approach Paper Analysis of Current Industry Trustmark Programs and GTRI PILOT Approach Discussion Deck TFTM Committee.
Categories of Vocabulary Compatibility Dmitry Lenkov Oracle.
Draft – discussion only Content Standards WG (Documents and Data) Proposed HITSC Workgroup Evolution 1 Architecture, Services & APIs WG Transport and Security.
HECSE Quality Indicators for Leadership Preparation.
Example of OOR Architecture Open Ontology Repository Architecture – Some Considerations March, 2008 Dr. Ravi Sharma Senior Enterprise Architect Technology.
Ontology Summit 2015 Track C Report-back Summit Synthesis Session 1, 19 Feb 2015.
Understanding to InterGrid and WAG Dr. ZhenChun Huang Tsinghua Univ. NRSCC/RSGS/SIG Team Sep, 2006.
Taken from Schulze-Kremer Steffen Ontologies - What, why and how? Cartic Ramakrishnan LSDIS lab University of Georgia.
A Context Model based on Ontological Languages: a Proposal for Information Visualization School of Informatics Castilla-La Mancha University Ramón Hervás.
Leo Obrst, Fabian Neuhaus MITRE, NIST An Open Ontology Repository: Rationale, Expectations & Requirements Session.
Christoph F. Eick University of Houston Organization 1. What are Ontologies? 2. What are they good for? 3. Ontologies and.
Co-Champions: Ram D. Sriram (NIST) Leo Obrst (MITRE) Ontology Summit 2015: Internet of Things: Toward Smart Networked Systems and Societies Virtual Panel.
Scalable Trust Community Framework STCF (01/07/2013)
Dictionary based interchanges for iSURF -An Interoperability Service Utility for Collaborative Supply Chain Planning across Multiple Domains David Webber.
16/11/ Semantic Web Services Language Requirements Presenter: Emilia Cimpian
LTSC Report to SAB1 Learning Technology Standing Committee Sponsor Report October, 2006.
No Longer Under Our Control? The Nature and Role of Standards in the 21 st Century Library William E. Moen School of Library and Information Sciences Texas.
Copyright 2008, The MITRE Corporation Dr. Leo Obrst MITRE Information Semantics Group Information Discovery & Understanding Dept. Command & Control Center.
Semantic Data Extraction for B2B Integration Syntactic-to-Semantic Middleware Bruno Silva 1, Jorge Cardoso 2 1 2
Leo Obrst, Fabian Neuhaus MITRE, NIST An Open Ontology Repository: Rationale, Expectations & Requirements Session.
Building Consensus C&S 563. BAD Consensus n Those who oppose do not speak up at meeting. n Everyone nodding in unison but not really agreeing with the.
Upper Ontology Summit The BFO perspective Barry Smith Department of Philosophy, University at Buffalo National Center for Ontological Research National.
Of 24 lecture 11: ontology – mediation, merging & aligning.
February 2, PM ET. Since the Summit… WE LISTENED…. Here’s what’s happening….. Curriculum Working Group is hard at work …… Why we are having these.
Spotlight on ‘standards’: 2004 update Sue Halbwirth University of Technology Sydney 5 th Annual Conference ACTKM Forum 14 October 2004 Standards Australia.
Lisbon, 30 th March 2016 Gianluca Luraschi Gonçalo Cadete “Towards a Methodology for Building.
Conduction of a simulation considering cascading effects
SNOMED CT Education SIG: Strategic Plan Review
Ontology Framework: Results of Ontology Summit 2007
SysML v2 Formalism: Requirements & Benefits
The Role of Ontologies for Mapping the Domain of Landscape Architecture An introduction.
Siri Jodha Khalsa CIRES, Univ. of Colorado
Model-Driven Analysis Frameworks for Embedded Systems
Ontology Reuse In MBSE Henson Graves Abstract January 2011
Regional Architecture Development for Intelligent Transportation
Conduction of a simulation considering cascading effects
Developing a shelter strategy
Semantic Web Towards a Web of Knowledge - Projects
Backward mapping – planning template
ONTOMERGE Ontology translations by merging ontologies Paper: Ontology Translation on the Semantic Web by Dejing Dou, Drew McDermott and Peishen Qi 2003.
Presentation transcript:

Dr. Leo Obrst MITRE March 14, 2006 Upper Ontology Summit Issues: Opportunities and Challenges Tuesday, March 14, 2006 Upper Ontology Summit NIST

2 Ontology Elephants There is no single real elephant There must be an upper elephant An elephant is abstract An elephant is very abstract There must be a purpose for an elephant: use cases? An elephant is really very simple An elephant is the result of consensus Open vs. Closed Elephant There are only distributed elephants & their mappings

3 1. Points of Agreement 1.We desire semantic interoperability. 2.We agree that a mere taxonomy is insufficient for that. 3.We agree that axioms are an indispensable part of creating semantic interoperability. What types of semantic interoperability require axioms and what types could be achieved with taxonomies with verbal definitions? 4.We agree to disagree on the best way to achieve interoperability: establishing (partial) alignments/correspondence, common subset, common upper ontology, etc., as will be discussed in (II). We agree that the best combination of mechanisms may emerge from the work to be undertaken 5.We agree that the dialog on making upper ontologies interoperable will contribute to improvements in the existing upper ontologies.

4 2. Opportunities and Challenges Modularity: How to Achieve? Incompatibilities? Lattice/poset of theories? 3-D vs. 4-D vs. 3-D/4-D Other? 2.Mapping among the terms/axioms of the relevant upper ontologies Term to term maps Bridging axioms Finding consistent common interpretation subsets Create a reference library of upper ontologies Express in a common language: CLIF or some other CL dialect, IKL?  Do we need a common language for expressing commonalities and differences? Identifying an intersecting subset of terms/axioms of the relevant upper ontologies Identifying areas where agreement is easy vs. areas where agreement would be difficult Barriers to agreement, e.g., assumptions on which ontologies are based  Scope of these assumptions: do two ontologies based on different assumptions have no points of agreement or are some elements neutral with respect to assumptions?  Seek agreement on what needs to defined, rather than reach agreement on definitions? 3.Criteria for evaluating ontologies, including application-based criteria Criteria for evaluating ontologies, including application-based criteria Methods for evaluating ontologies, including protocols and testbeds Certification?

5 3. Next Steps? 1.Create a consortium or working group Align with existing standards organization? Independent: New committee under NCOR, ECOR, JCOR: Upper Ontology Reconciliation and Mapping Committee? 2.Identify (or begin to identify) pairs of upper ontologies and/or content elements across upper ontologies where alignment work would be particularly appropriate 3.Seek joint funding to address 2 and 3.1 and Other?