Actions

OOR/ConferenceCall 2011 07 29: Difference between revisions

Ontolog Forum

imported>KennethBaclawski
(Fix PurpleMediaWiki references)
 
(No difference)

Latest revision as of 07:32, 9 January 2016

OpenOntologyRepository: Architecture & API Workshop-VII - Fri 2011_07_29

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

Session Chair: Ken Baclawski & Todd Schneider

Conference Call Details

  • Date: Friday, 29-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

Since we did not have a quorum, it was decided (by the three who were in attendance) to postpone the workshop. We spend some time updating one another on latest relevant developments in the OOR-related world and then adjourned the meeting.

In-session chat-transcript

Peter P. Yim: Welcome to the

OpenOntologyRepository: Architecture & API Workshop-VII - Fri 2011_07_29

Topic: "OOR Architecture & API Specification Development Workshop-VII"

Session Chair: Ken Baclawski & Todd Schneider

Session page: http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2011_07_29

.

Peter P. Yim: Hi Ken ...

Ken Baclawski: Good morning Peter

Peter P. Yim: good morning

Peter P. Yim: it's the summer, and a lot of people are still away ...

therefore, like the 2011_07_08 session, I suggest we postpone if we do not have 5

or more participants ( ref. http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2011_07_08#nid2VNQ )

anonymous morphed into Todd Schneider

Todd Schneider: I concur with Peter's suggestion (and I'm very tired)

Ken Baclawski: The new UI code has been checked in. The sandbox and source code are now consistent.

Ken Baclawski: The ontology categories have not yet been updated. This will be handled soon.

Peter P. Yim: OOR sandbox url: http://sandbox.oor.net/ (or http://oor-01.cim3.net/ )

Peter P. Yim: we need to revisit meeting times ... and also find out if we want to meet

much at all in August because of the summer

Peter P. Yim: REMINDER: important OOR team meeting next Friday 2011_08_05 ... don't miss it!

Peter P. Yim: -- session ended 6:55am PDT --

The agenda below was not covered during the call!

1. Meeting called to order:

  • ______ took the chair and welcome everyone
  • ______ volunteered to keep a record of the proceedings
  • review and adopt agenda

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

  • review of agenda

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]:

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:
    • 2011_08_05 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
  • Call adjourned at: 6:55 am PDT

--

notes taken by: Peter P. Yim / 2011.07.29-7:12am PDT

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


Resources