OpenOntologyRepository: Architecture & API Workshop-V - Fri 2011_05_20    (2T6K)

Topic: "OOR Architecture & API Specification Development Workshop-V"    (2T6L)

Session Co-chairs: KenBaclawski & ToddSchneider    (2U0V)

Conference Call Details:    (2T6M)

Attendees    (2T6Q)

Agenda Ideas:    (2TT5)

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

Abstract:    (2U1I)

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.    (2U1J)

The various architectures and APIs for ontology repositories are available at OpenOntologyRepository_Architecture    (2U1K)

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.    (2U1L)

Here is the straw man architecture: OpenOntologyRepository_Architecture/Candidate03    (2U1M)

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.    (2U1N)

Here is the API expressed in WSDL:    (2U1O)

Here is the API expressed in Java:    (2U1P)

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

Here is the proposed organizing plan: OpenOntologyRepository_Architecture/GettingOrganized    (2U1R)

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

The following are relevant prior meetings:    (2U1T)

Agenda & Proceedings    (2U21)

1. Meeting called to order:    (2U22)

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

3. Key items for review and discussion today:    (2U2D)

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

3.1) Resolve / Finalize the first method proposed    (2U2I)

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

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).    (2U2M)

3.3) Discussed today (2011.05.20)    (2U74)

Consensus, Conclusions & Follow-up Actions:    (2U2N)

 -- begin in-session chat-transcript --    (2U2X)
	PeterYim: Welcome to the    (2UO3)
	OpenOntologyRepository: Architecture & API Workshop-V - Fri 2011_05_20    (2UO4)
	Session Co-chairs: KenBaclawski & ToddSchneider    (2UO5)
	Ref. details at:    (2UO6)
	anonymous2 morphed into MichaelGruninger    (2UO7)
	anonymous morphed into MikeDean    (2UO8)
	KenBaclawski: The current UI is "uniform" in the sense that everyone has access to every screen. Since OOR users 
                      will have different roles, would it make sense to change this design?    (2UO9)
	KenBaclawski: Should security rules and gatekeeping rules be done together? This integrates the workflow with security.    (2UOA)
	ToddSchneider: Depends on what gatekeeping means?    (2UOB)
	ToddSchneider: Gatekeeping - The Gatekeeping component shall be responsible for enforcing role based behaviors which 
                       include access control; Behaviors will be represented as rules    (2UOC)
	PeterYim: ref. "Quality and Gatekeeping" on the OntologySummmit2008_Communique 
                  -    (2UOD)
	MichaelGruninger: There is some ambiguity in the terms within the architecture (such as Gatekeeping and Administration). 
        For each of these terms we should explicitly specify the functionalities that correspond to the component within the architecture.    (2UOE)
 -- end of in-session chat-transcript --    (2U2Y)

4. Any Other Business:    (2U2Z)

5. Action items:    (2U30)

6. Schedule Next Meeting & Adjourn:    (2U31)

 notes taken by: PeterYim / 2011.05.27-7:18am PDT
 All participants, please review and edit to enhance accuracy and granularity of the documented proceedings.    (2U39)

Resources    (2U3A)