Public Requirements

From NCBO Wiki
Revision as of 20:49, 25 January 2007 by Rubin (talk | contribs)
Jump to navigation Jump to search

1. URI Requirements

Basic functional URI requirements

  1. Provide persistent URIs for all content in BioPortal terminologies and ontologies
  2. All URIs will contain the version info for the terminology so that new terminology releases do not invalidate older URIs (ie, no URI ever disappears).
  3. All URIs provided by NCBO will have a base format of ""
  4. The URI will contain the version number of the terminology/ontology so that NCBO provides unique URIs for every term in every version.
  5. Enable people to refer to a URI that always points to the most current version of a term

Future URI requirements

  1. Add a link between URIs of different versions of the same term (in doing so have a "linked list" representing the history). This is purely additive so this will not affect the task of making URIs unique and persistent per version.

2. Web API


3. Load scripts to incorporate new ontologies into BioPortal

  1. Load SNOMED and ICD
  2. Load newly submitting ontologies into LexGrid

4. Ontology alignment (Show mappings of terms in different ontologies)

  1. Display the mapping of a term in one ontology to a term in another ontology as a distinct link in graph view.
  2. Permit upload of bulk mappings
  3. Permit user to create a new mapping to a selected term

5. Basic ontology diff (compare ontology versions)

  1. Pre-compute diffs for versions of all ontologies in BioPortal
  2. Present tabular display of differences between two selected versions of ontologies

6. Critical enhancements to BioPortal 1.0

  1. Prioritize feature requests collected thus far

7. UVIC Jambalaya applet for advanced ontology visualization

  1. Create Java applet of Jambalaya, adapted to make API calls to BioPortal

8. Ontology Marginal Notes

  1. Permit user to select an ontology class in BioPortal and create structured and free text annotations on ontology classes

9. Integrate Degree of Interest Models into BioPortal

  1. Integrate Diamond prototype currently in Protege into BioPortal