Compositional Term Submission Tool: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
No edit summary
Line 42: Line 42:
Dependencies: [[Transition to OWL]]
Dependencies: [[Transition to OWL]]


==== Benchmarks ====
==== Reasoner Benchmarks ====


Need to test various OWL reasoners, simulate evolution of GO
Need to test various OWL reasoners, simulate evolution of GO

Revision as of 16:16, 9 August 2010

Project lead: Chris

Coordinates with: ontology-editors

An increasing number of terms coming in from sourceforge are automatable compositional terms - particularly regulation terms. The compositional term request system allows annotators to use a web template system to instantaneously get the term they require, provided it conforms to an existing pre-determined template. A reasoner is used to place the term automatically in the hierarchy.

Project Dependencies


Status

#v1 is available to curators, currently on regulation requests are live


Deliverables

v1

v1 is obo-format dependent, uses a custom reasoner, and relies on various ad-hoc scripts

v1 report

A report on the v1 implementation is available:

v2

v2 will be a port of #v1

  • implemented in Java
  • works off of OBO or OWL files
  • uses OWLAPIv3
  • runs in TomCat
  • uses OWL reasoners

Dependencies: Transition to OWL

Reasoner Benchmarks

Need to test various OWL reasoners, simulate evolution of GO