How To Join (while the session is in progress)    (2JUU)

OpenOntologyRepository: OOR Team Conference Call - Fri 2010-11-19    (2JLK)

Session Title: "(Post-BioPortal fork) OOR Architecture and API - Take-II"    (2JS8)

Session Co-chairs: KenBaclawski (NEU) & MichaelGruninger (U of Toronto)    (2JS9)

Panelists:    (2JSA)

... Please refer also to the notes from the last regular meeting at: OOR/ConferenceCall 2010_10_01 and the three recent pertinent sessions:    (2JQK)

Archives:    (2JSG)

Conference Call Details:    (2JPC)

Attendees    (2JPZ)

Resources:    (2JT0)

Agenda & Proceedings    (2JQ8)

Session Topic: "Getting OOR Development Going - Take-IV"    (2JLN)

Abstracts:    (2JTK)

we have decided to organize a second panel session: "(Post-BioPortal fork) OOR Architecture and API - Take-II" to continue discussion on the (post-BioPortal fork) OOR Architecture and API, and explore more proposals and options. In particular, we want, especially, to hear from those who are planning to contribute code to OOR, but have not had a chance to present their work, and tell us what they plan to bring to the table, and have suggestions about the system architecture.    (2JTM)

Panel Member Talks:    (2JTN)

Abstract: ...    (2JTQ)

ref. Proposed Domain Model - xml html    (2JTU)

Abstract: I will give an overview    (2JTT)

Abstract: ... We propose an OOR architecture consisting of simple APIs, ontology repository implementations conforming to these APIs and a registry of these repositories. Together these components create an OOR network that can be used to build services utilizing content from different ontology repositories. The approach is based on an observation that there are different kinds of use cases, ontologies, ontology service providers, etc., and therefore it may not be possible to implement a single OOR server that addresses all possible needs. We suggest that the OOR initiative should focus on APIs and enabling an ecosystem of ontology repositories, not on doing everything by ourselves. Test suites and baseline implementations for APIs are needed for validating API implementations on different ontology repositories and testing the APIs.    (2JTX)

Abstract: ...    (2JU0)

Abstract: ... The Open Ontology Repository provides repository services for a wide range of ontological resources. The OOR architecture should provide spaces for discussion, creation, maintenance, and collaboration on those resources. That will require general content management repositories and collaboration services. Two OASIS TC’s, namely Content Management Interoperability Services (CMIS) TC and OASIS Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services TC, are defining standards to promote interoperability of content management repositories and collaboration services. CMIS v1.0 is an approved standard with an open source implementation provided by Apache Chemistry.    (2JU3)

ICOM is a framework for integrating a broad range of domain models for collaboration. ICOM adopts the CMIS domain model for Folder, Document, Version Control, and Relationship. ICOM complements the content management domain with Community, User, Group, Role (directory domain of LDAP), Space (team workspace), Category (taxonomy), and Tag. ICOM extends the content management domain to represent Unified Message, Calendar, Task List, Address Book, Blog, Wiki, Forum, Conference, Presence, Social Network, and other collaboration artifacts. ICOM TC members are editing a draft of that standard and incubating a Java Persistence API (JPA) prototype framework. The ICOM POJO classes are portable to any JPA provider. It is appropriate to release the POJO classes independently of the JPA prototype framework under an appropriate open source library license.    (2JUZ)

I will be providing an overview of the ICOM model and the JPA prototype framework to illustrate the value-add that ICOM can bring to the services of the Open Ontology Repository.    (2JV0)

Transcript of the online chat during the session:    (2JU4)

 see raw transcript [ here].    (2JU5)
 (for better clarity, the version below is a [ re-organized and lightly edited chat-transcript].)
 Participants are welcome to make light edits to their own contributions as they see fit.    (2JU6)
    -- begin of chat session --    (2JU7)

(chat transcript ... coming!)    (2JU8)

     -- end of chat session --    (2JU9)

Audio Recording of this Session    (2JUA)

Proposed Architectural Approaches:    (2JUI)

http://ontolog.cim3.net/file/work/OpenOntologyRepository/2010-11-19_OOR-Architecture-API-2/revised-OOR-architecture-proposal--ToddSchneider-KenBaclawski_20101119.jpg    (2JUK)

... coming!    (2JUM)

http://ontolog.cim3.net/file/work/OpenOntologyRepository/2010-11-19_OOR-Architecture-API-2/proposed-architecture-slide--viljanen-tuominen_20101119.jpg    (2JUO)

... coming!    (2JUQ)

http://ontolog.cim3.net/file/work/OpenOntologyRepository/2010-11-19_OOR-Architecture-API-2/proposed-OOR-architecture--EricChan-ICOM_20101119a.jpg    (2JUS)

For the record ...    (2JUT)