From OntologPSMW

Jump to: navigation, search
[ ]


OpenOntologyRepository: Architecture & API Workshop-IV - Fri 2011_04_22     (1)

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

  • RSVP to appreciated, ... or simply just by adding yourself to the "Expected Attendee" list below (if you are a member of the team.)     (1C6)
  • 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.     (1C8)

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)

  • Peter: we should really try to get into a position whereby people can start contributing code ASAP     (1F4)

Abstract     (1G)

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

The various architectures and APIs for ontology repositories are available at OpenOntologyRepository_Architecture     (1G2)

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.     (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 to up date 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:     (1H1)

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

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

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

3.1) Resolve / Finalize the first method proposed     (1H14)

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

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

-- begin in-session chat-transcript --     (1H20)

-- end of in-session chat-transcript --     (1H22)

4. Any Other Business:     (1H23)

5. Action items:     (1H24)

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

notes taken by: Peter P. Yim / 2011.04.22-7:18am PDT     (1H29)

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

Resources     (1I)

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