> don't address the question. We store the NCBI taxonomy in a nested-set > representation in a postgres database. We've done this simply for > speed of retrieval - I'd be interested to know how an rdf triple store > performs - eg in response to a query like 'get all species of > primates'. This is something I'd be very much interested in as well. Some non-biology examples would include queries such as: SELECT ?x WHERE (?x partOf* ?y) to retrieve all x that are directly or indirectly a part of y, or SELECT ?x WHERE (?x rdf:type* ?y) to retrieve all x that are instances of y or one of its subclasses. One solution I am aware of is to have a rule engine and store inferred statements explicitly. if x hasParent y y hasParent z then x hasAncester z if p occursIn x x hasAncestor y then p occursIn y SELECT ?p WHERE (?p hasAncestor ?x) This approach of course increases the size of the data considerably and furthermore complicates updates, so if anyone has come up with a more elegant solution I'm very much interested.Received on Monday, 29 March 2004 10:39:17 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:52:05 GMT