1 / 9

A Modular Software Architecture for OOR

This presentation discusses a modular software architecture for the Open Ontology Repository (OOR), emphasizing federation, collaborative editing sites, and support for various languages and policies. It also highlights the initial implementation and future plans for the project.

carlschultz
Download Presentation

A Modular Software Architecture for OOR

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Modular Software Architecture for OOR Mike Dean mdean@bbn.com OOR panel 22 August 2008

  2. Roadmap Summary • 1 public site + public/private instantiations • Emphasis on federation, including loose ontologies and collaborative editing sites • Apache Server-like modular software architecture • Sites select languages, metadata, repository, IPR and other policies, governance, etc. they want to support • Initial support for OWL and Common Logic • Leverage and “cross reference” related efforts while seeking dedicated funding • More details in slides 55-64 of Ontology Summit 2008 OOR Team Presentation

  3. OOR Project • OOR software development is now hosted as aproject on the SemWebCentral.org GForge site • http://projects.semwebcentral.org/projects/oor/ • Register for an account using New Account and send email to mdean@bbn.com to be added

  4. Initial implementation • Java interfaces (incomplete) and stub implementations • Generated Javadoc presented at http://ontolog.cim3.net/file/work/OOR/OOR-prototype--MikeDean_20080606/doc/ • Hasn’t yet evolved much past this point • Helpful feedback from Ravi Sharma and Carlos Rueda

  5. Module Hierarchy • Standard composable interfaces and (currently) stubbed example implementations • Each site selects which modules they want to support • Each module supports its own configuration options • Developers can “vote with their code” • Code available at http://oor.projects.semwebcentral.org/

  6. Abstraction • Try to incorporate as many options in modules, to maximize flexibility • Metadata vocabulary (e.g. OMV) – was originally part of core • Lifecycle model • States: created/submitted, accepted, edited, deprecated, etc. • Transitions • Modules can specify dependencies on other modules (e.g. language-specific gatekeepers)

  7. Event Model • Modules register handlers for lifecycle events • Handlers may preclude state transitions (e.g. gatekeepers) • Execution order based on module dependencies?

  8. Terms • Generalization of things that can be searched for and maintained in OOR • Person, Event, hasFather, owns, … • Each language defines its own TermTypes • OWL classes, properties, individuals • Common Logic concepts, predicates, … • SKOS concepts, labels, schemes, collections

  9. Next Steps • Continue refinement of interfaces • Start on implementations • Encapsulate existing components, e.g. from BioPortal, XMDR, etc. • Develop federation interfaces to other repositories • (Both are main motivations for this panel) • Initial operating capability • Downloadable software • Public instantiation on openontologyrepository.net (infrastructure provided by CIM3)

More Related