Difference between revisions of "Hierarchy Services"
Jump to navigation
Jump to search
Line 3: | Line 3: | ||
There are 3 major hierarchy services. | There are 3 major hierarchy services. | ||
+ | All of them takes as argument: | ||
+ | * An ontology version id or an ontology virtual id (In that second case, the latest version of the ontology is used). | ||
+ | * A conceptId | ||
+ | * '''Optional arguments:''' | ||
+ | ** level=<integer> - limits results to a given level in the hierarchy | ||
+ | ** offset=<integer> – results offset (used for pagination) | ||
+ | ** limit=<integer> – limits the number of results | ||
+ | == Parent & Children services == | ||
− | + | * '''Signature''': ./concepts/parents/{ontlogyVersionId}/{conceptId}[?{optional args}] | |
+ | * '''Example''': http://rest.bioontology.org/bioportal/concepts/parents/13578/Melanoma | ||
− | == | + | == Paths service == |
== Sibling service == | == Sibling service == |
Revision as of 11:15, 23 April 2009
The hierarchy services provide information about ontology, such as is_a transitive closure, precomputed by NCBO. The hierarchy services information is based on the <SubClass> & <SuperClass>. Those relations most of the time represent is_a hierarchies.
There are 3 major hierarchy services. All of them takes as argument:
- An ontology version id or an ontology virtual id (In that second case, the latest version of the ontology is used).
- A conceptId
- Optional arguments:
- level=<integer> - limits results to a given level in the hierarchy
- offset=<integer> – results offset (used for pagination)
- limit=<integer> – limits the number of results
Parent & Children services
- Signature: ./concepts/parents/{ontlogyVersionId}/{conceptId}[?{optional args}]
- Example: http://rest.bioontology.org/bioportal/concepts/parents/13578/Melanoma