From OntologPSMW

Jump to: navigation, search
[ ]

Contents

OpenOntologyRepository: Architecture & API Workshop-VI - Fri 2011_06_17     (1)

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

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

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, 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 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.     (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:     (1H1)

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

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

  • 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.     (1H9)
    • Each OOR instance declares what ontology languages it supports.     (1H9A)
    • Every OOR instance MUST support RDFS.     (1H9B)
      • This is required because the metadata is expressed in OMV.     (1H9B1)
      • OMV is written in OWL, but it may be sufficient to require only RDFS. This needs to be investigated.     (1H9B2)
    • Other ontology languages MAY be supported.     (1H9C)
    • For each metadata attribute, it will be specified whether it is required or optional.     (1H9D)
    • An ontology must satisfy other requirements depending on the ontology language.     (1H9E)

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

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

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

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

4. Any Other Business:     (1H15)

5. Action items:     (1H16)

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


Resources     (1I)


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