Difference between revisions of "Data Repository and Data Services"
From phenoscape
(→Web services) |
(→Term info) |
||
| Line 12: | Line 12: | ||
'''URI''' | '''URI''' | ||
| − | < | + | <BASE URI>/term/{term_id} |
'''Returns''' | '''Returns''' | ||
Revision as of 18:30, 10 November 2008
Contents
Data loader
A data loader application to refresh the data in the Phenoscape database on a daily basis is under development. The application is being developed as a Perl module which:
- Downloads curated NeXML files from the Phenoscape SVN repositories
- Drops and recreates the database
- Loads the requisite ontologies into the database
- Loads the data from the curated NeXML files into the database, and
- Invokes the OBD reasoner to elicit implicit information from the data and adds them to the database
Web services
Each service may support multiple media types. The desired media type can be specified by appending ?media=json or similar to the request URL.
Term info
URI
<BASE URI>/term/{term_id}
Returns
JSON: <javascript> {
"id" : "TAO:0001700",
"name" : "caudal-fin stay",
"definition" : "Bone that is located anterior to the caudal procurrent rays. Caudal fin stays are unpaired bone."
"parents" :
[
{
"relation" : "OBO_REL:is_a",
"id" : "TAO:0001514",
"name" : "bone"
},
{
"relation" : "OBO_REL:part_of",
"id" : "TAO:0000862",
"name" : "caudal fin skeleton"
}
],
"children" : [] // if there are children, this content should be in the same format as the parents list
} // how should xrefs, etc. be represented, property_value definitions? </javascript>
OWL-RDF:
TBD...
If there is no term with the given ID, the service should return "404 Not Found".
Handling of anonymous post-compositions
Autocomplete
URI
Returns <base>/term/search/{text}
