OOR/ConferenceCall 2011 06 17

= OpenOntologyRepository: Architecture & API Workshop-VI - Fri 2011_06_17 =

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

Session Co-chairs: KenBaclawski & ToddSchneider

Conference Call Details:

 * Date: Friday, 17-Jun-2011
 * Start Time: 9:00pm EDT / 6:00am PDT / 3:00pm CEST / 2:00pm BST / 13:00 UTC
 * ref: World Clock
 * Expected Call Duration: 1.0~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


 * In-session chat-room url: http://webconf.soaphub.org/conf/room/oor_20110617


 * RSVP  to [mailto:peter.yim@cim3.com 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.)


 * This session, like all other Ontolog events, is open to the public. Information relating to this session is shared on this wiki page: http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2011_06_17


 * 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

 * Attended:
 * KenBaclawski (co-chair)
 * JouniTuominen
 * TimDarr
 * LeoObrst
 * ToddSchneider (co-chair)
 * MichaelGruninger
 * AliHashemi


 * Expecting:


 * Regrets:
 * PeterYim
 * MikeDean

Agenda Ideas:
please insert any additional items below (along with your name for follow-up purposes)


 * The specifications to be discussed at the these workshops are the following (not necessarily discussed in this order):
 * the OOR Architecture
 * the OOR API
 * the Organizing Plan
 * the default development platform

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 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.

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

The following are relevant prior meetings:


 * Architecture & API Specification Development Workshop-V - OOR/ConferenceCall_2011_05_20
 * Architecture & API Specification Development Workshop-IV - OOR/ConferenceCall_2011_04_22
 * 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: KenBaclawski & MichaelGruninger - Panelists: KenBaclawski+ToddSchneider, AldoGangemi+AlessandroAdamou, JouniTuominen+KimViljanen, EricChan - 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:


 * KenBaclawski & ToddSchneider took the chair and welcome everyone
 * review and adopt agenda
 * KenBaclawski volunteered to keep a record of the proceedings

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


 * see above

3. Key items for review and discussion today:


 * "OOR Architecture & API Specification Development Workshop-VI:" (Archives)


 * 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.
 * Each OOR instance declares what ontology languages it supports.
 * Every OOR instance MUST support RDFS.
 * This is required because the metadata is expressed in OMV.
 * OMV is written in OWL, but it may be sufficient to require only RDFS. This needs to be investigated.
 * Other ontology languages MAY be supported.
 * For each metadata attribute, it will be specified whether it is required or optional.
 * It MUST be specified whether the ontology is available (or to be available in the future).
 * The ontology language MUST be specified.
 * Other attributes will be handled offline by MichaelGruninger based on the OMV specification.
 * An ontology must satisfy other requirements depending on the ontology language.
 * Syntax checking is always required.
 * Consistency checking is required with some time limit.


 * [ chat transcript of the session]
 * ToddSchneider: 4. Quality and Gatekeeping. We distinguish between gatekeeping and quality control. Gatekeeping criteria are 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.
 * ToddSchneider: Gatekeeping impacts metadata
 * ToddSchneider: Gatekeeping will need to vet the metadata to ensure entrance criteria are met.
 * ToddSchneider: Syntax checking is the responsibility of the language module.
 * ToddSchneider: Each
 * ToddSchneider: Each OOR instance must declare the representation languages
 * ToddSchneider: Each OOR instance must declare the representation language module it spports.
 * ToddSchneider: Will OOR Metadata be represented in OWL?
 * ToddSchneider: Every OOR shall support RDF
 * TimDarr: I do not see why metadata would need to support OWL. RDF should be sufficient.
 * ToddSchneider: Correction: Every OOR shall support RDFs
 * TimDarr: RDFS, I should say.
 * ToddSchneider: OMV is written in OWL
 * TimDarr: I don't think that OMV really takes advantage of OWL features.
 * ToddSchneider: Tim, I don't know if Michael is reading the chat.
 * TimDarr: OK, I have a bad connection and am just putting in my two cents.
 * MichaelGruninger: From Chapter 5 of the OMV Report 2.4.1: As aforementioned, OMV is formalized as an OWL ontology.
 * TimDarr: sorry - i just lost my connection. will call back
 * TimDarr: Let me ask my question here (cell phone connection is bad).
 * ToddSchneider: Gatekeeping criteria will include an attribute to indicate whether the ontology exists or the metadata represents an advertisement.
 * TimDarr: Are we assuming that the ontology (files) will be physically present in the repo, or can the repo contain the URL of the ontology that a user can use to access the ontology?
 * ToddSchneider: The location of the actual ontology is the responsibility of Administration.
 * TimDarr: Thanks! I am back on the call, but cell phone signal is not good.
 * TimDarr: Gone again ...
 * ToddSchneider: Metadata needs to include an attribute for the 'availability' of the ontology
 * ToddSchneider: 'Location' of the ontology must be provided.
 * ToddSchneider: Representation language of the ontology is a required attribute.
 * ToddSchneider: Michael will provide a preliminary list of required metadata attributes.
 * ToddSchneider: Submission process will be asynchronous
 * ToddSchneider: Minimal language dependency submission is syntax validation
 * ToddSchneider: Consistency checking, to some extent, will be required for submission
 * ToddSchneider: Need an attribute to represent that it is consistent, which then will require another field to identify the reasoner used to do the consistency checking
 * ToddSchneider: Ken has already developed the gatekeeper module which should provide enough to specify it for OOR
 * ToddSchneider: Ken's gatekeeper module already has a mechanism to configure the registration workflow for a community

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

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

Consensus, Conclusions & Follow-up Actions:

4. Any Other Business:

5. Action items:


 * MichaelGruninger will examine the OMV to determine which attributes are required and which are optional.
 * KenBaclawski will send KEEPER (the gatekeeping software) to ToddSchneider who will generate the UML.

6. Schedule Next Meeting & Adjourn:


 * Next Meeting:
 * Session on ISO 19763 with ElisaKendall [chair: MichaelGruninger] to be scheduled
 * 2011_07_01 Friday: regular OOR Team meeting
 * 2011_07_08 Friday: Architecture & API Workshop-VII [co-chair: KenBaclawski & ToddSchneider] ??


 * Call adjourned at: 7:00 am PDT

Resources

 * homepage - OpenOntologyRepository - http://OpenOntologyRepository.org
 * OOR Charter - To promote the global use and sharing of ontologies by: 1. establishing a hosted registry-repository; 2. enabling and facilitating open, federated, collaborative ontology repositories; 3. establishing best practices for expressing interoperable ontology and taxonomy work in registry-repositories.
 * "Ontology Repository" Definition - "An ontology repository is a facility where ontologies and related information artifacts can be stored, retrieved and managed"
 * Team mailling list:
 * OOR-Team discussion: [ oor-forum ]''' message archives - http://ontolog.cim3.net/forum/oor-forum/
 * OOR-Users discussion and support: [ oor-users ]''' message archives - http://ontolog.cim3.net/forum/oor-users/
 * Developers mailling list: [ oor-dev ] message archives - http://ontolog.cim3.net/forum/oor-dev/
 * proceedings of our previous meetings, panel discussions and workshops
 * the Joint OOR-OntologySummit2008 Panel Discussions:
 * 2008_02_28 - Thursday: Joint OOR-OntologySummit2008 Panel Discussion: "Ontology Registry and Repository Technology & Infrastructure Landscape" - Co-chairs: LeoObrst & FrankOlken; Panelists: BruceBargmeyer, MikeDean, MarkMusen, FarrukhNajmi & PeterYim - ConferenceCall_2008_02_28
 * 2008_03_27 - Thursday: Joint OOR-OntologySummit2008 Panel Discussion: "An Open Ontology Repository: Rationale, Expectations & Requirements - Session-1" - Chair: LeoObrst & FabianNeuhaus; Panelists: WilliamBug, EvanWallace, JohnLMcCarthy, KenBaclawski, PeterBenson & RexBrooks - ConferenceCall_2008_03_27
 * 2008_04_03 - Thursday: Joint OOR-OntologySummit2008 Panel Discussion: "An Open Ontology Repository: Rationale, Expectations & Requirements - Session-2" - Chair: LeoObrst & FabianNeuhaus; Panelists: DougLenat, DekeSmith, MarciaZeng, DeniseBedford, PatHayes, MalaMehrotra & RobRaskin - ConferenceCall_2008_04_03
 * 2008_04_10 - Thursday: Joint OOR-OntologySummit2008 Panel Discussion: "Developing an Ontology of Ontologies for OOR" - Co-chairs: BarrySmith & MichaelGruninger; Panelists: MichaelGruninger, PeterHaase, NatashaNoy & ElisaKendall - ConferenceCall_2008_04_10
 * the OOR Development panel sessions:
 * 2008_08_22 - Friday: OOR Panel Discussion: "Getting OOR Development Off the Ground: Identifying Synergies & Gaps" (Take-1) - Chair: LeoObrst; Panelists: MikeDean, MarkMusen, LiDing, BruceBargmeyer & BillAndersen - ConferenceCall_2008_08_22
 * 2009_02_19 - Thursday: Joint Ontolog-OOR Panel Discussion: "Getting OOR Development Off the Ground (Take-2): the work begins" - Chair: ToddSchneider; Panelists: MarkMusen, NatashaNoy, MikeDean, PaulBuitelaar / AndreasHarth, MathieuDaquin, KenBaclawski, MichaelGruninger - ConferenceCall_2009_02_19
 * 2009_07_16 - Thursday: Joint Ontolog-OOR Panel Discussion: "Integrated tools for ontology development and management: A field guide to the Stanford technology" - Chair: MarkMusen - Panelists: TaniaTudorache, TimRedmond, NatashaNoy - ConferenceCall_2009_07_16
 * 2009_07_30 - Thursday: Joint Ontolog-OOR Panel Discussion: "BioPortal and related Ontology Repository Implementations and Development" (Take-3) - Chair: NatashaNoy - Panelists: CarlosRueda, PaulAlexander, JohnGraybeal, MikeDean, StephenGranite, AlexGarcia, KenBaclawski - ConferenceCall_2009_07_30
 * 2010_02_19 - Friday: OOR Panel Discussion: "Coordinating our Open Ontology Repository Software Development" - Chair: MikeDean - Panelists: JimChatigny, MichaelGruninger, KenBaclawski, NatashaNoy - OOR/ConferenceCall_2010_02_19
 * 2010_04_01 - Thursday: Joint OOR-Ontolog Panel Session: "OOR Use Cases - Take-3" - Chair: KenBaclawski & ToddSchneider - Panelists: ToddSchneider, MatthewHettinger, KenBaclawski and MaximoGurmendez - ConferenceCall_2010_04_01
 * 2010_09_10 - Friday: Joint SIO-OOR-Ontolog Panel Discussion: "Common Logic (CL) Support for OOR" - Chair: JohnSowa - Panelists: JohnBateman-TillMossakowski, MichaelGruninger, CameronRoss, AdamPease, PatHayes - ConferenceCall_2010_09_10
 * 2010_09_17 - Friday: OOR Panel Discussion - "Getting OOR Development Going - Take-IV" Workshop - Co-chairs: ToddSchneider & MichaelGruninger - Panelists: ToddSchneider, MikeDean, NatashaNoy, ImmanuelNormann, KenBaclawski, MichaelGruninger - OOR/ConferenceCall_2010_09_17
 * 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
 * 2010_11_19 - Friday: OOR Panel Discussion - "(Post-BioPortal fork) OOR Architecture and API - Take-II" - Co-chairs: KenBaclawski & MichaelGruninger - Panelists: KenBaclawski+ToddSchneider, AldoGangemi+AlessandroAdamou, JouniTuominen+KimViljanen, EricChan - OOR/ConferenceCall_2010_11_19
 * 2011_03_04 - Friday: OOR "Architecture & API Specification Development Workshop-I" - Co-chairs: KenBaclawski & ToddSchneider - OOR/ConferenceCall_2011_03_04
 * 2011_03_11 - Friday: OOR - "Architecture & API Specification Development Workshop-II" - Co-chairs: KenBaclawski & ToddSchneider - OOR/ConferenceCall_2011_03_11
 * 2011_03_18 - Friday: OOR Metadata Workshop-I - Chair: MichaelGruninger - OOR/ConferenceCall_2011_03_18
 * 2011_03_25 - Friday: OOR - "Architecture & API Specification Development Workshop-III" - Co-chairs: KenBaclawski & ToddSchneider - OOR/ConferenceCall_2011_03_25
 * 2011_04_22 - Friday: OOR - "Architecture & API Specification Development Workshop-IV" - Co-chairs: KenBaclawski & ToddSchneider - OOR/ConferenceCall_2011_04_22
 * 2011_05_13 - Friday: OOR Metadata Workshop-II - Chair: MichaelGruninger - OOR/ConferenceCall_2011_05_13
 * 2011_05_20 - Friday: OOR - "Architecture & API Specification Development Workshop-V" - Co-chairs: KenBaclawski & ToddSchneider - OOR/ConferenceCall_2011_05_20
 * the OOR-IPR mini-series:
 * 2010_09_09 - Thursday: Joint OOR-Ontolog-NCBO-CC-IAOA-OASIS Panel Discussion - "IPR issues in Ontology and the OOR" session-1: an exposition on relevant IPR regimes - Keynote speaker: GeorgeStrawn - Chair: PeterYim - Panelists: JamieClark, JohnWilbanks, BrucePerens - ConferenceCall_2010_09_09
 * 2010_09_16 - Thursday: Joint OOR-Ontolog-NCBO-CC-IAOA-OASIS Panel Discussion - "IPR issues in Ontology and the OOR" session-2: what are the IPR issues relating to open ontology repositories (and ontologies in general)? - Chair: MarkMusen - Panelists: CameronRoss, AlanRector, JohnSowa, BrucePerens, JohnWilbanks, PeterYim - ConferenceCall_2010_09_16
 * 2010_09_30 - Thursday: Joint OOR-Ontolog-NCBO-CC-IAOA-OASIS Panel Discussion - "IPR issues in Ontology and the OOR" session-3: discussion and consensus on licensing arrangements for the OOR Initiative, and positions we might take on related IPR issues - chair: LeoObrst - Panelists: PeterYim, MikeDean, BrucePerens, JamieClark - ConferenceCall_2010_09_30
 * OntologySummit2008 homepage
 * OntologySummit2008_Communique
 * OntologySummit2008/FaceToFaceAgenda & Proceedings
 * The OOR Project Presentation (delivered at the OntologySummit2008 face-to-face workshop)
 * [ ontology-summit ] discussion archives - http://ontolog.cim3.net/forum/ontology-summit/2008-01/ (~5 months exchanges starting from Jan-2008)
 * Our key content pages:
 * OpenOntologyRepository_Scope
 * OpenOntologyRepository_Organization
 * OpenOntologyRepository_Process
 * OpenOntologyRepository_Policy
 * OpenOntologyRepository_IPR
 * OpenOntologyRepository_Requirement
 * OpenOntologyRepository_UseCases
 * OpenOntologyRepository_Architecture
 * OpenOntologyRepository_Approach
 * OpenOntologyRepository_Roadmap
 * OpenOntologyRepository_Plan
 * OpenOntologyRepository_Funding
 * OpenOntologyRepository_ResearchIssues
 * OpenOntologyRepository_ResearchActivity
 * OpenOntologyRepository_Development
 * OpenOntologyRepository_Metadata
 * OOR/ActiveMemberContribution
 * OOR Project site at SemWebCentral - http://oor.semwebcentral.org
 * Public sandbox instance of OOR (OOR-sandbox) - http://sandbox.oor.net/ontologies (previously http://oor-01.cim3.net/ontologies)
 * OOR_SandBox
 * NCBO - BioPortal
 * NCBO-OOR development documentation - http://www.bioontology.org/wiki/index.php/NCBO-OOR_Development