Changes between Version 61 and Version 62 of ImplementationBootcamp

Timestamp:

2010/02/12 10:47:34 (14 years ago)

Author:

jerven

Comment:

--

ImplementationBootcamp

@@ -207 +207 @@
 http://www.w3.org/RDF/Validator/
 
-== How should I build the URI's of my resources ==
-  * see Data_Provider_Session
-  * for the unknown/non-existing URI's (link a resource that was not described before ) it was suggested to use '''urn:void:mydatabase:id'''. For example '''urn:void:mylab:table0980:row1:col10'''.
-
 == SPARQL ==
 
@@ -240 +236 @@
 
 === What is reasoning? ===
+
+Reasoning can be used in a few ways. It can be used to infer data that was not hard coded into the database.
+e.g. Triples are added in the store that you did not encode.
+
+an example.
+
+ProteinA :interactsWith ProteinB
+
+without reasoning when you ask
+{{{
+sparql  ?with where (ProteinB :interactsWith ?with)
+}}}
+will return no results. When the owl statement is added
+
+:interactsWith owl:inverseOf :interactsWith
+
+Then the same query will return proteinA as ?with.
+
+You can also introduce classes as shown by the SADI example. To make more readable queries.
+For example give me all human proteins known to be a kinase.
+e.g. 
+{{{
+select ?p where {?p a :Protein .
+?p :classifiedWith <http://purl.uniprot.org/keywords/418> .
+?p :organism <http://purl.uniprot.org/taxonomy/9606> .)
+}}}
+While
+{{{
+select ?p where (?p a :HumanKinase)
+}}}
+is much more readable to a human/biologist. This :HumanKinase type can be generated on the fly using owl inference.
+
+
+It can also be used to do quality control.
+e.g. when assigning the keyword complete proteome to an uniprot entry a chromosomal location must be known. When an entry is found for a with the keyword complete proteome but no chromosomal location. A contradiction is raised. i.e. and error. This allows us to notify a curator and fix this oversight. 
 
 === What reasoners are available? ===