Actions

Ontolog Forum

OpenOntologyRepository Meeting - Fri 2011_07_08

Topic: Originally planned "OOR Architecture & API Specification Development Workshop-VII" for this session is postponed

Session Chair: Ken Baclawski

Conference Call Details

  • Date: Friday, 8-Jul-2011
  • Start Time: 6:00am PDT / 9:00am EDT / 3:00pm CEST / 2:00pm BST / 13:00 UTC
  • Expected Call Duration: 1.0~1.5 hours
  • Dial-in Number:
    • from a US telephone (US): +1-218-844-8060 (domestic long distance cost will apply)
    • When calling in from a phone, use Conference ID: "4389979#"
    • from Europe, call:
      • Austria 0820-4000-1577
      • Belgium 070-35-9992
      • France 0826-100-280
      • Germany 01805-00-7642
      • Ireland 0818-270-037
      • Italy 848-390-179
      • Spain 0902-886-056
      • Switzerland 0848-560-327
      • UK 0844-581-9148
    • callers from other countries please dial into either one of the US or European numbers
  • RSVP to peter.yim@cim3.com appreciated, ... or simply just by adding yourself to the "Expected Attendee" list below (if you are a member of the team.)
  • Please note that this session may be recorded, and if so, the audio archive is expected to be made available as open content, along with the proceedings of the call to our community membership and the public at-large under our prevailing open IPR policy.

Attendees

  • Expecting:
    • ... if you are coming to the meeting, please add your name above (plus your affiliation, if you aren't already a member of the community) above, or e-mail <peter.yim@cim3.com> so that we can reserve enough resources to support everyone's participation. ...

Agenda Ideas

please insert any additional items below (along with your name for follow-up purposes)

  • The specifications to be discussed at the these workshops are the following (not necessarily discussed in this order):
    • the OOR Architecture
    • the OOR API
    • the Organizing Plan
    • the default development platform

Abstract

As a result of the two OOR Architecture and API panel sessions back in Oct & Nov-2010, we have been exposed to a large number of architecture and API candidates for ontology repositories. We have had requirements for the OOR, at least in broad outline form, since the Ontology Summit 2008. We have been running an OOR sandbox based on BioPortal. Most recently, we have forked from the BioPortal code base with the intention of proceeding separately with the development of a reference implementation.

At this series of meetings, we are going through the process of producing the actual OOR specification. It will be run as a workshop where the straw man proposal will be discussed and modified as needed.

The various architectures and APIs for ontology repositories presented for consideration are available at OpenOntologyRepository_Architecture

Here is the straw man architecture: OpenOntologyRepository_Architecture/Candidate03

In addition, there is an API of the core services that was obtained from BioPortal, which is not entirely compatible with the straw man architecture, but furnishes a starting point. This API will also be discussed and modified as needed.

Here is the API expressed in WSDL: http://www.ccs.neu.edu/home/kenb/oor/OORService.wsdl

Here is the API expressed in Java: http://www.ccs.neu.edu/home/kenb/oor/OORI.java

Finally, we need to agree on a plan for completing the development of the specification.

Here is the proposed organizing plan: OpenOntologyRepository_Architecture/GettingOrganized

We encourage all participants to update your candidate contributions to ensure your ideas are known and understood.

The following are relevant prior meetings:

Agenda & Proceedings

1. Meeting called to order:

  • Peter P. Yim volunteered to keep a record of the proceedings
  • review and adopt agenda
    • Ken / Peter: if we don't ave a critical mass of attendees, we will postpone this workshop to a later date
      • [decision]: the workshop is postponed ... we'll just exchanged among those who are present "what's new" and plan on the next few meeting. ... see below

2. Roll Call & Adoption of last meeting's minutes:

3. Key items for review and discussion today:

  • Announcements and Urgent Matters:
  • Review of action item(s) from the previous meeting(s)
  • from 2011.06.17 - Michael Grüninger will examine the OMV to determine which attributes are required and which are optional.
  • from 2011.06.17 - Ken Baclawski will send KEEPER (the gatekeeping software) to Todd Schneider who will generate the UML.
  • "OOR Architecture & API Specification Development Workshop-VII:" (Archives)

... items below are mostly from the previous workshop, and will be updated as this session progresses.

  • Gatekeeping specifies the a set of minimal requirements that any ontology within the OOR has to meet. The latter are intended to enable the users of the OOR to find quickly ontologies that fit their needs; the criteria are not supposed to ensure the quality of the ontologies.
    • Each OOR instance declares what ontology languages it supports.
    • Every OOR instance MUST support RDFS.
      • This is required because the metadata is expressed in OMV.
      • OMV is written in OWL, but it may be sufficient to require only RDFS. This needs to be investigated.
    • Other ontology languages MAY be supported.
    • For each metadata attribute, it will be specified whether it is required or optional.
      • It MUST be specified whether the ontology is available (or to be available in the future).
      • The ontology language MUST be specified.
      • Other attributes will be handled offline by Michael Grüninger based on the OMV specification.
    • An ontology must satisfy other requirements depending on the ontology language.
      • Syntax checking is always required.
      • Consistency checking is required with some time limit.
  • chat transcript of this session:
    • Peter P. Yim: since it is the summer, and a lot of people are on travel or have other plans, may I suggest we postpone this workshop if we do not have 5 or more attendees
    • Peter P. Yim: I have subscribed myself to the BioPortal's [bioontology-support] mailing list ... I suggest members of this team should subscribe to that, if they aren't already - ref. https://mailman.stanford.edu/mailman/listinfo/bioontology-support
    • Peter P. Yim: in the next OOR team meeting, I would like to briefly discuss the above too.
    • Peter P. Yim: new ISO effort for Ontology Interoperability, entitled: "OntoIOp" - see: http://ontolog.cim3.net/forum/ontolog-forum/2011-05/msg00034.html
    • Peter P. Yim: officially: New Work Item Proposal ISO/NP 17347 - Ontology Integration and Interoperability (OntoIOp)
    • Peter P. Yim: encourage everyone to (or get an appropriate colleague to) participate in this effort - contact the ISO representative of your country about your interest!
    • Peter P. Yim: ... since we did not have quorum, the "Architecture & API Workshop-VII" is now postponed to Friday 2011.07.29
    • Peter P. Yim: Next Friday (2011.07.15), we'll have our regular OOR team meeting (making up for the one we canceled in 2011.07.01) ... we probably want to discuss whether we should take it slow in August too, because a lot of people will be on vacation (especially our friends in Europe.)
    • Peter P. Yim: no meeting on Friday (2011.07.22) - IAOA is co-organizing the "Vespucci Summer Institute" on "Process Ontology" in Florence, Italy that week - see: http://vespucci.org/programme

Consensus, Conclusions & Follow-up Actions:

  • we are postponing this workshop to Fri 2011-07-29

4. Any Other Business:

5. Action items:

6. Schedule Next Meeting & Adjourn:

  • Next Meeting: How about ...
    • 2011_07_15 Friday: regular OOR Team meeting
      • we need to discuss if we want to take it slow (maybe just one or at most 2 meetings) in August
    • 2011_07_22 Friday: no meeting
    • 2011_07_29 Friday: Architecture & API Workshop-VII [co-chair: Ken Baclawski & ToddSchneider]
  • Call adjourned at: 6:38 am PDT

--

notes taken by: Peter P. Yim / 2011.07.08-7:00am PDT

All participants, please review and edit to enhance accuracy and granularity of the documented proceedings.


Resources