OntologySummit2008/Idea

= Ideas & Suggestions for OntologySummit2008 =

Please provide your ideas for our OntologySummit2008 by entering them directly on this page.

This workspace is for Ontolog members only. If you want to join the community, please refer to our Membership details. Please identify yourself and date your input for ease of follow-up. If you are referring to discussion on the [ontolog-forum], please provide the hyperlink to the corresponding message on the archives

Suggested Topics
please provide a title and a brief description below:


 * Issues and Implementation of an Open Ontology Repository
 * PeterYim, LeoObrst, MikeDean - see planning meeting discussion at: ConferenceCall_2008_01_03


 * Revisiting the development of a common upper ontology - ref. 2006 UpperOntologySummit/UosJointCommunique
 * PatCassidy: http://ontolog.cim3.net/forum/ontolog-forum/2007-12/msg00169.html


 * The "Common Logic" ISO standard
 * JohnSowa: http://ontolog.cim3.net/forum/ontolog-forum/2007-12/msg00178.html


 * Revisiting the ontology "Framework" developed during OntologySummit2007 - ref. OntologySummit2007_JointCommunique
 * PaolaDiMaio: http://ontolog.cim3.net/forum/ontolog-forum/2007-12/msg00182.html


 * "The Role of Ontologies in Semantic Interoperability"
 * ref. BrandNiemann - http://ontolog.cim3.net/forum/ontolog-forum/2008-01/msg00065.html


 * "Ontologizing and Harmonizing Standards"
 * ref. BrandNiemann - http://ontolog.cim3.net/forum/ontolog-forum/2008-01/msg00065.html


 * Here is my suggestion on the Ontology Summit:


 * Main topic would be the open ontology repository, with some time reserved for a

revisitation of the previous two summit results. We would have three email threads prior to the meeting, one for each of these topics. (--SteveRay / 2008.01.15)


 * "Mapping and Integration: Ontologies Unite" (Interoperability for Open Repositories and Registries)
 * see my comment below (--MichelleRaymond / 2008.01.22)



Suggested criteria on proposing and selecting topics for OntologySummit2008

 * the topic should be of the kind worthy of being addressed in an Ontology "Summit" (--PeterYim/2007.12.22)
 * Question to all: what would be the kind of topic that is important and urgent enough to capture the passion ans imagination of the broader ontology community?


 * please make sure suggested topics are consistent with the missions of the organizers, namely that of: (--PeterYim/2007.12.22)
 * (a) NIST, or more specifically, the theme of "Interoperability" (since our final face-to-face meeting will be part of the "NIST Interoperability Week 2008" ,
 * (b) Ontolog - ref. our Charter, and
 * (c) other co-organizers/co-sponsors who will be joining us to get this initiative going.


 * proposers of specific topics should be ready to contribute time and effort to help with organization work if their suggested topic gets adopted. (--PeterYim/2007.12.22)



Other Ideas and Suggestions
controlled organizational process -- the main parts of this should not be open to the whole list, I believe, because this puts people off when their mailboxes become full of what for them are irrelevant detail. Also it is not efficient for targeted decision making. (--BarrySmith/2008.01.21)
 * I would like to put in a plea for a more

of, though I suspect there needs to be a DL subset specified to make real inroads into OWL.
 * I agree with you that CL/IKL is something we should be making something


 * The issue with upper ontologies is how to make them compatible. (I do

not think many are, even the 3D ones). The work I have been doing over the last year has been showing me that there is the possibility of 3D ontologies that, whilst not strictly compatible, are fairly directly mappable to the kind of 4D ontology I am working on. It is just that I think that is probably a minority sport.


 * I would also support looking at the differences between existing (upper)

ontologies. I think just understanding the differences and the consequences would be useful.


 * I do not have a good feeling about an open ontology. Unless it is along

John Sowas ideas of a lattice of theories, where competing theories can sit side by side, I see difficulties in reaching agreement on almost anything. And if you do have a lattice of theories, there is a big danger of an incomprehensible mess. The amount of work is also imense.


 * (--MatthewWest/2008.01.22)


 * Regarding "Mapping and Integration: Ontologies Unite" (Interoperability for Open Repositories and Registries)


 * My view into topic (MichelleRaymond): Approaches for mapping and integration services as applied to multi-level, multi-source resources, to include:


 * 1) Interoperable and scalable ontology repositories
 * 2) Associated ontologically valid information repositories
 * 3) Associated taxonomically valid resource registries
 * 4) Associated standard vocabulary based document/message headers wrapping registry and repository data.


 * Focus: Strongly lean on levels 1 (one) and 3 (three).


 * (--MichelleRaymond/2008.01.22)


 * Possible Areas under Ontology Repository


 * Repository Architecture
 * - Functional Requirements
 * - Structure of Repository
 * - Connection Mechanisms between Repositories
 * - Layers for Data Types
 * Repository Management
 * - Users and Roles Authentication
 * - Monitoring Conformity of Ontology
 * Mapping and Integration
 * - Compatibility of Data
 * - Integrating Multi-domain Taxonomies
 * Applications and Services
 * - Common Approach
 * - Registry of Resources
 * - Vocabulary Extraction and Conversion
 * (--MichelleRaymond/2008.01.22)
 * - Registry of Resources
 * - Vocabulary Extraction and Conversion
 * (--MichelleRaymond/2008.01.22)
 * (--MichelleRaymond/2008.01.22)



Suggested Content Committee Discussion
Given that:


 * 1 - the Launch Event, is February 7th * 2008_02_07 - Thursday: OntologySummit2008 Launch Event - ConferenceCall_2008_02_07  
 * 2 - we need a starting topic structure before the Logistics Committee meets
 * 3 - the Logistics Committee should meet before the Launch Event

we need to get a suggested Topic Structure quickly.

Toward that end, a starting point for topic suggestions is provided below.

Content Committee - Step One: Select and Structure Discussion Topics for Summit Discussion Threads
Objective: Provide an information structure for topics initially opened for discussion to be announced at the OntologySummit2008 Launch Event.

Please see the message http://ontolog.cim3.net/forum/ontology-summit/2008-01/msg00001.html which suggests an approach to gathering, culling and structuring OntologySummit2008 discussion treads.

Topic Structure Discussion
The title for the OntologySummit2008 is "Toward an Open Ontology Repository" This is the focus under which we are structuring topics.

There will also be discussion threads stemming from the focus of previous Ontology Summits. These will also need Synopsis Pages and will likely develop topic areas under the main topic once the discussion has started.

Possible topics for "Toward an Open Ontology Repository"
Note: The initial numbering is to aid in discussion and organization of topics.

001.	Purpose of Ontology Repositories Research and Implementation

002.	Alignment with Common Upper Ontology

003.	Connectivity of Information Sources and Knowledge Services

004.	Improve Data Registry creation, services and maintenance

005.	Best practices for Ontology Repositories

006.	Interoperability

007.	Ontology Mapping and Repository Integration

008.	Connection Mechanisms between Repositories

009.	Ontology Repository Architecture

0010.	Functional Requirements

0011.	Structure of Repository

0012.	Objects and Classifications in the Repository

0013.	Scope and View into the Repository Contents

0014.	Infrastructure for Repository Support and Services

0015.	Layers for Data Types

0016.	Use of a Repository Upper Ontology

0017.	Contents of an Ontology Repository

0018.	Instantiating a Taxonomically Valid Registry

0019.	Common Vocabulary Tags for retrieved data for Repository, Stored Ontology or Information Registry

0020.	Repository Management

0021.	Life-Cycle of Ontology Repositories

0022.	Ontology Metadata and Version Control

0023.	Modular Ontology Connection and Management

0024.	Users and Roles

0025.	Logging and Metrics

0026.	Quality

0027.	Compatibility of data when crossing with other Repositories

0028.	Monitoring conformity of Ontology in Repository

0029.	Validation of Ontology against Encoding Standard (ex: OWL or RDFS)

0030.	Consistency within Ontology in Repository

0031.	Services and Support Applications

0032.	Standardized Approaches to Service Design, Development and Interfaces

0033.	Browse, Search, Query and Index Application to Ontology Repositories

0034.	Editing and Annotation of Ontologies and the Repository holding the Ontologies

0035.	Visual Representations of Ontology Repositories

0036.	Registry of Resources Infrastructure and ties to Ontology Repository

0037.	Mapping and Integration within and cross Ontology Repositories

0038.	Compatibility of Data across Ontologies

0039.	Integrating Multi-domain Taxonomies

0040.	Ontology versus Taxonomy versus Vocabulary Mappings

0041.	Vocabulary Extraction and Conversion

0042.	Useful Tagging of extracted data

0043.	Reasoning Services

0044.	Implementation of Ontology Repositories

0045.	Current Gaps in Ontology Repository Viability

0046.	Data Storage and Retrieval Methods

0047.	Repository API

0048.	Repository Use Cases

0049.	Development Practices and Examples

0050.	Test Practices and Examples

0051. Stability of Open Ontologies


 * Comments
 * Hypothesis: Truly Open Ontology stability in terms of consistency and even data validity is tenuous when anyone can make modifications.
 * Issue: If these modifications are then made available to anyone through a repository, is the value of the ontology to the retriever's usage not constantly in question? (--MichelleRaymond/2008.01.30)

0052. Collect ontology of ontologies (PeterYim/2008.02.01)


 * Comments
 * Shows the Ontologies that may go into Repositories

0053. Communiqué and Mission Statement (PeterYim/2008.02.01)

0054. Ontology of Ontologies

0055. Quality Metrics

0056. State of the Art in Ontology Repository Work

0057. Standards work

0058. Current implementation

0059. Issues and lessons learned

0060. Early adopters of an open ontology repository

Potential starting point of discussion of Topic Structure
I. Toward an Open Ontology Repository - "Straw man" Topic Structure


 * 1.	Purpose of Ontology Repositories Research and Implementation (001)
 * 1.1.	Alignment with Common Upper Ontology (002)
 * 1.2.	Connectivity of Information Sources and Knowledge Services (003)
 * 1.3.	Improve Data Registry creation, services and maintenance (004)
 * 1.4.	Best practices for Ontology Repositories (005)
 * 1.5.	Interoperability (006)
 * 1.5.1.	Ontology Mapping and Repository Integration (007)
 * 1.5.2.	Connection Mechanisms between Repositories (008)


 * 2.	Ontology Repository Architecture (009)
 * 2.1.	Functional Requirements (0010)
 * 2.2.	Structure of Repository (0011)
 * 2.2.1.	Objects and Classifications (0012)
 * 2.2.2.	Scope and View (0013)
 * 2.3.	Infrastructure for Repository Support and Services (0014)
 * 2.4.	Layers for Data Types (0015)
 * 2.4.1.	Repository Upper Ontology (0016)
 * 2.4.2.	Ontology Repository (0017)
 * 2.4.3.	Taxonomically Valid Registry (0018)
 * 2.4.4.	Common Vocabulary Tags for retrieved data (0019)


 * 3.	Repository Management (0020)
 * 3.1.	Life-Cycle of Ontology Repositories (0021)
 * 3.2.	Ontology Metadata and Version Control (0022)
 * 3.3.	Modular Ontology Connection and Management (0023)
 * 3.4.	Users and Roles (0024)
 * 3.5.	Logging and Metrics (0025)
 * 3.6.	Quality (0026)
 * 3.6.1.	Compatibility of data when crossing with other Repositories (0027)
 * 3.6.2.	Monitoring conformity of Ontology (0028)
 * 3.6.3.	Validation of Ontology against Encoding Standard (0029)
 * 3.6.4.	Consistency within Ontology	(0030)


 * 4.	Support Applications and Services (0031)
 * 4.1.	Standardized Approaches to Service Design, Development and Interfaces (0032)
 * 4.2.	Browse, Search, Query and Index Application to Ontology Repositories (0033)
 * 4.3.	Editing and Annotation of Ontologies and the Repository holding the Ontologies (0034)
 * 4.4.	Visual Representations of Ontology Repositories (0035)
 * 4.5.	Registry of Resources Infrastructure and ties to Ontology Repository (0036)
 * 4.6.	Mapping and Integration within and cross Ontology Repositories (0037)
 * 4.6.1.	Compatibility of Data cross Ontologies (0038)
 * 4.6.2.	Integrating Multi-domain Taxonomies (0039)
 * 4.6.3.	Ontology versus Taxonomy versus Vocabulary Mappings (0040)
 * 4.7.	Vocabulary Extraction and Conversion (0041)
 * 4.8.	Useful Tagging of extracted data (0042)
 * 4.9.	Reasoning Services (0043)


 * 5.	Implementation of Ontology Repositories (0044)
 * 5.1.	Current Gaps in Ontology Repository Viability (0045)
 * 5.2.	Data Storage and Retrieval Methods (0046)
 * 5.3.	Repository API (0047)
 * 5.4.	Repository Use Cases (0048)
 * 5.5.	Development Practices and Examples (0049)
 * 5.6.	Test Practices and Examples (0050)

II. Ontology Framework (OntologySummit2007) Recap Topics TBD

III. Upper Ontology (UpperOntologySummit) Recap Topics TBD


 * (--MichelleRaymond/2008.01.29)

Below are the results from the discussion of the first Content Planning Meeting

Next Step: Topic Area Champions revise thread topic structure for each Main Topic
Potential thread topics are the topics under each main topic in the hierarchy below. The Champions of each main topic will revise suggested thread topics. Their revisions are intended to provide initial scoping for each Main Topic. Scoping gives us the best chance to come up with substantive discourse to lead us toward an open ontology repository.

Of course, there will be migration of threads and topics based on the discussion participant's direction. The Main Topics and thread suggestions are simply to start us on a viable path toward an open ontology repository.

Objective: (refined from Initial Objective) Provide main topics to be opened as a thread for summit discussion and provide lists of suggested discussion topics that will be in scope of each main topic.

Topic Structure for further refinement by Main Topic Champions
I. Toward an Open Ontology Repository - "Launch Arrangement" of Topic Structure

[Summit-Focus]


 * 1  Communiqué and Mission Statement - Champions (to come from Organizing Committee)
 * 1.1  Purpose of Ontology Repositories Research and Implementation
 * 1.2  Connectivity of Information Sources and Knowledge Services
 * 1.3  Improve Data Registry creation, services and maintenance
 * 1.4  Interoperability
 * 1.5  Early adopters of an open ontology repository

[Repository-Arch]


 * 2  Ontology Repository Architecture - Champions (MichelleRaymond and RaviSharma)
 * 2.1  Functional Requirements
 * 2.2  Structure of Repository
 * 2.2.1  Objects and Classifications
 * 2.2.2  Scope and View
 * 2.3  Infrastructure for Repository Support and Services
 * 2.4  Layers for Data Types
 * 2.4.1  Repository Upper Ontology
 * 2.4.2  Ontology Repository
 * 2.4.3  Taxonomically Valid Registry
 * 2.4.4  Common Vocabulary Tags for retrieved data

[Ont-of-Ont]


 * 3  Ontology of Ontologies  - Champions (MichaelGruninger and PatHayes)
 * 3.1  Repository Management
 * 3.1.1  Life-Cycle of Ontology Repositories
 * 3.1.2  Ontology Metadata and Version Control
 * 3.1.3	  Modular Ontology Connection and Management
 * 3.1.4	  Users and Roles
 * 3.1.5	  Logging and Metrics
 * 3.2  Browse, Search, Query and Indexing for Ontology Repositories
 * 3.3  Editing and Annotation of Ontologies and the Repository holding the Ontologies
 * 3.4  Mapping and Integration within and cross Ontology Repositories
 * 3.4.1  Compatibility of Data cross Ontologies
 * 3.4.2  Integrating Multi-domain Taxonomies
 * 3.4.3  Ontology versus Taxonomy versus Vocabulary Mappings
 * 3.5 Alignment with OntologySummit2007 Framework
 * 3.6 Alignment with UpperOntologySummit

[Quality-Gate] (modified MichelleRaymond/2008.02.07)


 * 4  Quality and Gatekeeping (modified title MichelleRaymond/2008.02.07)  - Champions (BarrySmith and FabianNeuhaus)
 * 4.1  Compatibility of data when crossing with other Repositories
 * 4.2  Monitoring conformity of Ontology
 * 4.3  Validation of Ontology against Encoding Standard
 * 4.4  Consistency within Ontology

[State-of-Art]


 * 5  State of the Art in Ontology Repository Work - Champion (FrankOlken)
 * 5.1  Standards work
 * 5.2  Current implementation
 * 5.2.1  Data Storage and Retrieval Methods
 * 5.2.2  Repository API
 * 5.3  Issues and lessons learned
 * 5.3.1  Current Gaps in Ontology Repository Viability
 * 5.4  Development Practices and Examples
 * 5.5  Test Practices and Examples
 * 5.6  Best practices for Ontology Repositories

II. Ontology Framework (OntologySummit2007) Recap Topics TBD

III. Upper Ontology (UpperOntologySummit) Recap Topics TBD


 * (--MichelleRaymond/2008.02.01)
 * (--MichelleRaymond/2008.02.07)