OpenOntologyRepository (OOR) Initiative - Architecture (184N)
This page is for documentation related to the architecture of the "open ontology repository" we are planning to implement through the OOR initiative. (184O)
Adopted (184P)
... (enter adopted items here) (184Q)
Proposed for Adoption (184R)
... (enter adopted items here) (184S)
- Summarizing from the OntologySummit2008 discourse (1TAK)
Ideas & Candidates (184T)
... (enter ideas and candidates here) (184U)
- /Candidate01 - Java interfaces and shell classes - proposed by FarrukhNajmi/2008.01.28 (184V)
- ref. ... (184W)
- /Candidate02 - proposed by MikeDean/2008.06.06 (184X)
- /Candidate03 - BioPortal architecture (by NCBO) -- BenjaminDai (1TAM)
OOR Architecture preliminary alignment call - Tue 17-Feb-2009 (1TAN)
Date / Time: Tue 2009.02.17 - 10:00am PST / 1:00pm EST Attended: BenjaminDai, MikeDean, MichaelGruninger, KenBaclawski, ToddSchneider, PeterYim Expecting: MikeDean, BenjaminDai, MichaelGruninger, ... (1TAO)
Discussion notes: (1TAP)
- trying to get ready for a software architecture that the oor-dev (OOR development) community can contribute into (1TIF)
- first "sandbox" instance, based on the NCBO-BioPortal technology, being built out (1TIG)
- For the Feb-19 session (1TIJ)
- Mike: suggest the NCBO folks provide a list of features working on now, and near-term on BioPortal (1TIK)
- Ken: asking for an OOR architecture (1TIL)
- Todd: asked Mark for the BioPortal architecture (1TIM)
- Benjamin has been working on this - see: (1TIN)
- http://www.bioontology.org/wiki/index.php/NCBO-OOR_Development (1TIO)
- Benjamin solicits feedback on how this developer documentation can be improved to better help the expanding development community. This wiki page focuses on both developer architects and developers with familiarity with aspect-oriented programming. (1TIZ)
- http://www.bioontology.org/wiki/index.php/NCBO_Developer_Communications (1TIP)
- Benjamin shares this documentation to potentially re-use developer collaboration strategies currently used by the NCBO. Of course, OOR developers will have their own OOR tools (e.g., the OOR dev mailing list). (1TJ8)
- Todd will help to get a set of UML diagrams made for the architecture (maybe not before Feb-19, though) (1TIY)
- Benjamin has been working on this - see: (1TIN)
- Going foward with the OOR development (1TIQ)
- Benjamin & Mike: a fork? or a subversion branch which will eventually merging back to BioPortal? (1TIR)
- on the BioPortal gforge repository or on the oor-SemWebCentral gforge repository? (1TIS)
- ALL: decision to, at least for the time being, OOR will take a subversion branch and work off the BioPortal gforge repository (1TIU)
- we'll aim at eventually merging the code back to BioPortal (1TIV)
- Mike: the oor-SemWebCentral gforge repository will still be available if anyone (say, for a sub-project) needs it (1TIW)
- we'll defer to Benjamin & Mike to develop some simply controls as to who can commit, who has access, etc. (1TIX)
- Benjamin: BioPortal development is in two major projects - Core (REST services) and Presentation (ruby on rails) (1TIT)
- Todd requested that Benjamin makes a comparison between what BioPortal has to offer against the OpenOntologyRepository_Requirement. This will occur after the Feb-19th session (1TJ0)
- Mike: suggest doing sessions of "code walkthrough" for developers who will be joining the team (1TJ1)
- call adjourned: 10:55am PST (1TJ6)
- Notes by PeterYim - for those who were at the meeting, please review and edit the notes as you see fit. =ppy (1TJ7)
