From OntologPSMW

Jump to: navigation, search
[ ]


OpenOntologyRepository: Architecture & API Workshop-VIII - Tue 2011_10_11     (1)

Topic: "OOR Architecture & API Specification Development Workshop-VIII"     (1A)

  • Shared-screen support (VNC session), if needed, will be started 5 minutes before the call at:     (1C5)
    • view-only password: "ontolog"     (1C5A)
    • if you plan to be logging into this shared-screen option (which the speaker may be navigating), and you are not familiar with the process, please try to call in 5 minutes before the start of the session so that we can work out the connection logistics. Help on this will generally not be available once the presentation starts.     (1C5B)
    • people behind corporate firewalls may have difficulty accessing this. If that is the case, and where appropriate, please download the [ slides] and running them locally. The speaker(s) will prompt you to advance the slides during the talk.     (1C5C)
  • Discussions and Q & A:     (1C6)
    • (Unless the conference host has already muted everyone) Please mute your phone, by pressing "*2" on your phone keypad, when a presentation is in progress. To un-mute, press "*3"     (1C6A)
    • You can type in your questions or comments through the browser based chat session by:     (1C6B)
      • instructions: once you got access to the page, click on the "settings" button, and identify yourself (by modifying the Name field). You can indicate that you want to ask a question verbally by clicking on the "hand" button, and wait for the moderator to call on you; or, type and send your question into the chat window at the bottom of the screen.     (1C6C1)
    • (when everyone is muted) If you want to speak or have questions or remarks to make, please "raise your hand (virtually)" by click on the "hand button" (lower right) on the chat session page. You may speak when acknowledged by the speaker or the session moderator (again, press "*3" on your phone to unmute). Test your voice and introduce yourself first before proceeding with your remarks, please. (Please remember to click on the "hand button" again (to lower your hand) and press "*2" on your phone to mute yourself after you are done speaking.)     (1C6D)
    • thanks to the folks, one can now use a jabber/xmpp client (e.g. gtalk) to join this chatroom. Just add the room as a buddy - (in our case here) ... Handy for mobile devices!     (1C6E)
  • RSVP to appreciated, ... or simply just by adding yourself to the "Expected Attendee" list below (if you are a member of the team.)     (1C8)
  • 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.     (1C10)

Attendees     (1E)

  • Expecting:     (1E2)
    • ... 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 <> so that we can reserve enough resources to support everyone's participation. ...     (1E3A)

Agenda Ideas     (1F)

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

Abstract     (1G)

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.     (1G1)

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.     (1G2)

The various architectures and APIs for ontology repositories presented for consideration are available at OpenOntologyRepository_Architecture     (1G3)

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.     (1G5)

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

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

The following are relevant prior meetings:     (1G11)

Agenda & Proceedings     (1H)

1. Meeting called to order:     (1H2)

2. Roll Call & Adoption of last meeting's minutes:     (1H6)

3. Key items for review and discussion today:     (1H10)

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

  • 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.     (1H18)

--- Chat transcript begin: ---     (1H21)

Welcome to the OpenOntologyRepository: Architecture & API Workshop-VIII - Tue 2011_10_11     (1H22)

Proceedings:     (1I)

Todd Schneider: Here's where we are at, in terms of consensus arrived at from the     (1I1)

previous "OOR Architecture and API" workshops:     (1I2)

0) The interface for searching ontology metadata will consist of a single method     (1I3)

0.a) The method will have a single parameter consisting of a SPARQL query.     (1I4)

0.b) The return value of the method will be a SPARQL result set.     (1I5)

0.c) Metadata will be represented using a named RDF graph.     (1I6)

0.d) Metadata will be based on an extension of OMV.     (1I7)

o The OMV extension may include a notion of domain specification or     (1I8)

topics, represented as text.     (1I9)

0.e) Metadata will be federated, so it is a single named RDF graph, no matter     (1I10)

how many OOR instances there are. pics, represented as text.     (1I11)

0.f) Metadata will be federated, so it is a single named RDF graph, no matter     (1I12)

how many OOR instances there are.     (1I13)

1) Each OOR instance must declare the representation language module it supports.     (1I14)

2) Every OOR shall support RDFS     (1I15)

3) Quality and Gatekeeping. We distinguish between gatekeeping and quality control.     (1I16)

Definition: Gatekeeping specifies the a set of minimal requirements that any     (1I17)

ontology within the OOR has to meet. The latter are intended to     (1I18)

enable the users of the OOR to find quickly ontologies that fit     (1I19)

their needs; the criteria do not ensure the quality of the ontologies.     (1I20)

3.a) Gatekeeping will vet the metadata associated with an ontology to ensure     (1I21)

entrance criteria are met.     (1I22)

3.b) For each metadata attribute, it will be specified whether it is required     (1I23)

or optional.     (1I24)

3.b.i) It MUST be specified whether the ontology is available (or to be     (1I25)

available in the future).     (1I26)

3.b.ii) The ontology language MUST be specified.     (1I27)

3.b.iii) Other attributes will be handled offline by Michael Gruninger     (1I28)

based on the OMV specification.     (1I29)

3.c) An ontology must satisfy other requirements depending on the ontology     (1I30)

language.     (1I31)

3.d) Syntax checking is always required and the responsibility of the language     (1I32)

3.e) Consistency checking is required with some time limit.     (1I34)

3.f) Gatekeeping criteria will include an attribute to indicate whether the     (1I35)

ontology exists or the metadata represents an advertisement.     (1I36)

3.g) The location of the actual ontology is the responsibility of Administration.     (1I37)

3.h) Metadata needs to include an attribute for the 'availability' of the ontology     (1I38)

3.i) 'Location' of the ontology must be provided.     (1I39)

3.j) The representation language of the ontology is a required attribute.     (1I40)

3.k) Michael will provide a preliminary list of required metadata attributes.     (1I41)

3.l) Submission process will be asynchronous     (1I42)

Peter P. Yim: moving us forward ...     (1I43)

Peter P. Yim: now that we have the partitioning (architecturally), we need to adopt a     (1I44)

development platform (say, something like "eclipse"), and start having     (1I45)

team members claim ownership to developing specific modules     (1I46)

Peter P. Yim: also (important), please refer to the BioPortal "tab" implementation details     (1I49)

Todd Schneider: The 'administration' module is responsible for advertising which     (1I51)

representation languages an instance supports.     (1I52)

Peter P. Yim: All: we might want to partition some of the work to sizes that fit,     (1I53)

say, work by a student in 3-months (which might mean work that takes     (1I54)

an experienced developer a couple of weekends or a month to do)     (1I55)

Todd Schneider: The next Architecture meeting will focus on development platform and work partitioning     (1I56)

Todd Schneider: The next meeting will be on Tue 1 November 2011, same time     (1I57)

Todd Schneider: Homework: learn more about the Eclipse and its capabilities;     (1I58)

Read Paul Alexander's page on tabs     (1I59)

Peter P. Yim: we'll make that (choice of platform and work partitioning) as the main focus of     (1I61)

our next team meeting (Tue 2011.11.01)     (1I62)

Todd Schneider: We need to motivate contributors to provide 'comic' book level descriptions     (1I63)

of their work     (1I64)

Peter P. Yim: -- session ended 9:38am --     (1I65)

--- Chat transcript end: ---     (1I66)

Consensus, Conclusions & Follow-up Actions:     (1I67)

4. Any Other Business:     (1I68)

5. Action items:     (1I69)

6. Schedule Next Meeting & Adjourn:     (1I70)

  • Next Meeting:     (1I71)
    • "OOR Metadata Workshop" - Tue 2011.10.18 same time (that's next Tuesday)     (1I71A)
    • after that, there will be an joint "Ontology and Standards" session on Thu 2011.10.20 (watch for announcements)     (1I71B)
    • no meeting during the week of Oct-24 (as ISWC-2011 will be in session)     (1I71C)
    • then we'll be having the next OOR team meeting, same time on Tue 2011.11.01     (1I71D)
      • where we will cover the [ items discussed today] .. and, do make sure you have time to look over what's listed as [ homework] too, before the meeting, if possible!     (1I71D1)

notes taken by: Peter P. Yim / 2011.10.11-10:10am PDT     (1I74)

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

Resources     (1J)

This page has been migrated from the OntologWiki - Click here for original page     (1J16)