Actions

OpenOntologyRepository Architecture: Difference between revisions

Ontolog Forum

imported>KennethBaclawski
(Fix PurpleMediaWiki references)
 
No edit summary
 
Line 1: Line 1:
http://ontolog.cim3.net/file/work/OOR/OOR-Logo/OOR_banner_sm.png  
[[File:OOR-Logo.png]]
 
= [[OpenOntologyRepository]] ([[OOR]]) Initiative - Architecture  =
= [[OpenOntologyRepository]] ([[OOR]]) Initiative - Architecture  =


Line 125: Line 124:


[[Category:OOR]]
[[Category:OOR]]

Latest revision as of 15:10, 14 December 2022

OOR-Logo.png

OpenOntologyRepository (OOR) Initiative - Architecture

This page is for documentation related to the architecture of the "open ontology repository" we are planning to implement through the OOR initiative.

Adopted

... (enter adopted items here)

Key Discussions

Proposed for Adoption

From the 11 March 2001 Meeting -

searchOntologyMetadata

11 March 2011 - I'd like to suggest a small change to the (first) proposed method of the OOR specification.

Instead of 'searchOntologyMetadata' I suggest 'findOntologies'. Of course, as agreed, to execute or actualize this method the system would need to search the metadata. But the intent, from a user's perspective, is to find the ontology/ontologies that meet their criteria (the arguments of the method): the what.

Searching is a 'how' - there can many ways to find what is being looked for.

Finding is a 'what' - The end goal or intent of taking the action.

And yes, I'm also appealing to the semantic differences between these two words. From WordNet 2.0,

Search - the activity of looking thoroughly in order to find something

Find - discover or determine the existence

Again from a users perspective, and the one I think best used to understand the intent of any system, they want to find something. Searching is just one way to accomplish this.

13 March 2011 - I like to suggest a revision to my revision, just 'find()'. The argument would define what is to be found.

Getting Organized

  • Organizing Plan - see: /GettingOrganized
  • and ... Key Discussion above

Ideas, Candidates, Proposals and References

  • /Candidate03 (KenBaclawski & ToddSchneider) - OOR Software Architecture (Draft)
  • /From_COLORE (MichaelGruninger)
  • /From_ONKI (JouniTuominen & KimViljanen)
  • /From_ICOM (EricChan)
  • /From_STLab (AlessandroAdamou & AldoGangemi)
  • /Candidate01 - Java interfaces and shell classes - proposed by FarrukhNajmi/2008.01.28
    • ... Farrukh Najmi has subsequently decided to leave the OOR team as he needs to pursue his repository ideas for commercial purposes

OOR Architecture preliminary alignment call - Tue 17-Feb-2009

Date / Time: Tue 2009.02.17 - 10:00am PST / 1:00pm EST

Attended: BenjaminDai, Mike Dean, Michael Grüninger, Ken Baclawski, Todd Schneider, Peter P. Yim

Discussion notes:

  • trying to get ready for a software architecture that the oor-dev (OOR development) community can contribute into
  • first "sandbox" instance, based on the NCBO-BioPortal technology, being built out
    • first "sandbox" virtual machine just became ready (from CIM3)
    • Benjamin & team is trying to get the instance ready by the Feb-19 session
      • Benjamin will have some initial content
      • Mike will be happy to add some seed content too
        • Benjamin ask if Mike could sent those to him (for now)
        • Benjamin will also let Mike know when the sandbox is ready for user upload
  • For the Feb-19 session
    • Mike: suggest the NCBO folks provide a list of features working on now, and near-term on BioPortal
    • Ken: asking for an OOR architecture
    • Todd: asked Mark for the BioPortal architecture
      • Benjamin has been working on this - see:
      • Todd will help to get a set of UML diagrams made for the architecture (maybe not before Feb-19, though)
  • Going foward with the OOR development
    • Benjamin & Mike: a fork? or a subversion branch which will eventually merging back to BioPortal?
    • on the BioPortal gforge repository or on the oor-SemWebCentral gforge repository?
    • ALL: decision to, at least for the time being, OOR will take a subversion branch and work off the BioPortal gforge repository
      • we'll aim at eventually merging the code back to BioPortal
      • Mike: the oor-SemWebCentral gforge repository will still be available if anyone (say, for a sub-project) needs it
      • we'll defer to Benjamin & Mike to develop some simply controls as to who can commit, who has access, etc.
  • Benjamin: BioPortal development is in two major projects - Core (REST services) and Presentation (ruby on rails)
  • Mike: suggest doing sessions of "code walkthrough" for developers who will be joining the team

- call adjourned: 10:55am PST

- Notes by Peter P. Yim - for those who were at the meeting, please review and edit the notes as you see fit. =ppy