Actions

Ontolog Forum

Revision as of 07:31, 9 January 2016 by imported>KennethBaclawski (Fix PurpleMediaWiki references)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

OpenOntologyRepository: Architecture & API Workshop-IV - Fri 2011_04_22

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

Session Co-chairs: Ken Baclawski & Todd Schneider

Conference Call Details

  • Date: Friday, 22-Apr-2011
  • Start Time: 9:00pm EDT / 6:00am PDT / 3:00pm CEST / 2:00pm BST / 13:00 UTC
  • Expected Call Duration: ~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 meeting are the following (not necessarily discussed in this order):
    • the OOR Architecture
    • the OOR API
    • the Organizing Plan
    • the default development platform
  • Peter: we should really try to get into a position whereby people can start contributing code ASAP

Abstract

As a result of the two OOR Architecture and API panel sessions, we have seen a large number of architectures and APIs 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.

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

At this meeting we begin 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.

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 to up date your candidate contributions to ensure your ideas are known and understood.

The following are relevant prior meetings:

  • Architecture & API Specification Development Workshop-III - OOR/ConferenceCall_2011_03_25
  • Architecture & API Specification Development Workshop-II - OOR/ConferenceCall_2011_03_11
  • Architecture & API Specification Development Workshop-I - OOR/ConferenceCall_2011_03_04
  • 2011.02.04 discussion
  • 2010_11_19 - Friday: OOR Panel Discussion - "(Post-BioPortal fork) OOR Architecture and API - Take-II" - Co-chairs: Ken Baclawski & Michael Grüninger - Panelists: KenBaclawski+ToddSchneider, AldoGangemi+AlessandroAdamou, JouniTuominen+KimViljanen, Eric Chan - OOR/ConferenceCall_2010_11_19   
  • 2010_10_15 - Friday: OOR Project Team Member Conference Call - discussion on the (post-BioPortal fork) OOR Architecture and API - OOR/ConferenceCall_2010_10_15   

Agenda & Proceedings

1. Meeting called to order:

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

  • Announcements:
    • Todd & Peter: Doug Skuce will be joining the team
    • Ken: our NSF proposal (for OOR) was declined
    • Ken: NEU-Google patent infringement lawsuit settled; some research funding may come through as a result

3. Key items for review and discussion today:

  • "OOR Architecture & API Specification Development Workshop-IV:" (Archives)

3.0) Adopting (formally) the work from the last workshop, modulo any discussion/modifications entered on the wiki page.

3.1) Resolve / Finalize the first method proposed

3.2) Starting with the Registrar, as identified in your use cases, specify the functions to support that role starting with the use cases. Thereafter, move on to Accreditor, Steward, Process Manager, and Submitter. ... For each of the roles we also have to keep in mind any coupling to representation languages (relative to the actions taken).

Consensus, Conclusions & Follow-up Actions:

  • The interface for searching ontology metadata will consist of a single method:
    • The method will be called find.
    • The method will have a single parameter consisting of a SPARQL query.
    • The return value of the method will be a SPARQL result set.
    • Metadata will be represented using a named RDF graph.
    • The metadata RDF graph will use the following name: http://metadata.oor.net
    • Metadata will be based on an extension of OMV.
      • The OMV extension may include a notion of domain specification or topics, represented as text.
    • Metadata will be federated, so it is a single named RDF graph, no matter how many OOR instances there are.

-- begin in-session chat-transcript --

see: above

-- end of in-session chat-transcript --

4. Any Other Business:

5. Action items:

6. Schedule Next Meeting & Adjourn:

  • Next Meeting:
    • next week - we will be having the "Architecture & API Workshop Take-V" on Fri 2011.04.29
    • see developing session page is at OOR/ConferenceCall_2011_04_29
    • Fri 2011.04.29 - 9:00pm EDT / 6:00am PDT / 3:00pm CEST / 2:00pm BST / 13:00 UTC (ref. worldclock)
    • Note: earlier resolution: all team members please (if possible) block out Fridays 1.5 Hr
    • ref. our doodle poll (see: http://doodle.com/a2snxkpkd8hhxek4 ), looks like we can settle in on two new meeting times - a 6:00am PT (14:00 UTC) and an 8:30am PT (16:30 UTC) (or something in between) ...
  • Call adjourned at: 7:16 am PDT

--

notes taken by: Peter P. Yim / 2011.04.22-7:18am PDT

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

Resources



Retrieved from "https://ontologforum.com/index.php?title=OOR/ConferenceCall_2011_04_22&oldid=2091"