My presentation to BIoIT World Congress 2010, Boston MA, April, 2010. The slideshow describes the SADI Semantic Web Service framework, and how we are using SADI to begin personalizing the data exploration and analysis experience for biomedical and clinical researchers
1. Personalizing medical research using Semantics Mark Wilkinson, PI Bioinformatics, Heart + Lung Institute @ St. Paul’s Hospital Vancouver, BC, Canada
9. >1000 X more data in the “Deep Web” than in Web pagesPrimarily databases and analytical algorithms
10. Accessing these databases and analytical algorithms “transparently”, based on individual researcher’s ideas, beliefs, preferenceswill help us personalize medical research
11. Mark Butler (2003) Is the semantic web hype? Hewlett Packard laboratories presentation at MMU, 2003-03-12
12. Semantic Web?(my definition) An information system where machines can receive information from one source, re-interpret it, and correctly use it for a purpose that the source had not anticipated.
22. SADI Best Practice #1 Make the implicit explicit… A Web Service should create triples linking the input data to the output data, thus explicitly describing the semantic relationship between them
23. SADI Best Practice #1 This is what bioinformatics Web Services implicitly do anyway! Easy to implement this as a best-practice
24. SADI Observation #2:GET and POST GET guarantees the response relates to the request URI in a very precise and predictable way POST does not…
25. SADI Observation #2:GET and POST That’s why Web Services have a fundamentally different behaviour than the Semantic Web
26. SADI Observation #2:GET and POST We can fix that! (without breaking any existing rules or standards!)
27. SADI Best Practice #2 SUBJECT URI of the output graph (triples) is the sameas the SUBJECT URI of the input graph (triples) (the output is “about” the input... Now explicitly!)
28. Consequence The “Semantics” of our interaction with the Web Service are now explicitandidentical to the “Semantics” of GET
29. SADI Web Service Interfaces Service Interfaces defined by two OWL classes:
32. SADI Web Service Interfaces My Service consumes OWL Individuals of Class #1 and returns OWL Individuals of Class #2 …but the URI of those two individuals is the same!(see best practice #2)
33. How do we discover services? Since input and output are about the same “thing”, we can automatically determine what a service doesby comparing the Input and Output OWL classes
34. How do we find services? Automatically index services in a registry based on what properties (predicates) Services add to their respective input data-types
35. EXAMPLE Input Data: BRCA1 rdf:type Gene ID Output Data: BRCA1 hasDNASequence AGCTTAGCCA… Registry Index: Service provides “hasDNASequence” property to Gene IDs
36. Now we can answer questions like “what is the DNA sequence of BRCA1?” Discover a service that creates the DNA Sequence property of gene identifiers
52. …but I’m supposed to be personalizing research… Let’s make this a little more personal by bringing in Ontologies
53. My Definition of Ontology (for this talk) Ontologies explicitly define the things that exist in “the world” based on what propertieseach kind of thing must have
54. Ontology Spectrum Frames (Properties) Thesauri “narrower term” relation Selected Logical Constraints (disjointness, inverse, …) Catalog/ ID Formal is-a Informal is-a Formal instance General Logical constraints Terms/ glossary Value Restrs.
55. Demo #2 Discover instances of OWL classes from data that doesn’t exist…
56. Show me patients whose creatinine level is increasing over time, along with their latest BUN and creatinine levels. PREFIX regress: <http://sadiframework.org/examples/regression.owl#> PREFIX patients: <http://sadiframework.org/ontologies/patients.owl#> PREFIX pred: <http://sadiframework.org/ontologies/predicates.owl#> SELECT ?patient ?bun ?creat FROM <http://sadiframework.org/ontologies/patients.rdf> WHERE { ?patient patients:creatinineLevels ?collection . ?collection regress:hasRegressionModel ?model . ?model regress:slope ?slope FILTER (?slope > 0) . ?patient pred:latestBUN ?bun . ?patient pred:latestCreatinine ?creat . }
57.
58.
59.
60. Show me patients with elevated creatinine along with their latest BUN and creatinine levels PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> PREFIX patients: <http://sadiframework.org/ontologies/patients.owl#> PREFIX pred: <http://sadiframework.org/ontologies/predicates.owl#> SELECT ?patient ?bun ?creat FROM <http://sadiframework.org/ontologies/patients.rdf> WHERE { ?patient rdf:typepatients:ElevatedCreatininePatient . ?patient pred:latestBUN ?bun . ?patient pred:latestCreatinine ?creat . }
62. Regression models have features like slopes and intercepts… and so onThe class is completely decomposed until a set of required Services are discoveredcapable of creating all these necessary properties
63. Successful decomposition of the OWL class to discover the need for a LinearRegression Web Service, and so on
65. OWL Class restrictions converted into workflows SPARQL queries converted into workflows Reasoning happening in parallel with query executionData fulfilling OWL models is discovered, or generated through running analytical tools SADI and CardioSHARE
68. Show me patients whose creatinine level is increasing over time, along with their latest BUN and creatinine SELECT ?patient ?bun ?creat FROM <http://sadiframework.org/ontologies/patients.rdf> WHERE { ?patient rdf:typepatients:ElevatedCreatininePatient . ?patient pred:latestBUN ?bun . ?patient pred:latestCreatinine ?creat . }
69. I created a small ontologydescribing my definition ofan Elevated Creatinine Patient
79. What’s a fancy word for a world-view that you make-up? Hypothesis
80. Current Research We believe that ontologies and hypothesesare, in some ways, the same “thing”……simply assertions about individuals that may or may not existIf an instance of a class exists, then the hypothesis is “validated”
81. Recap SADI Semantic Web Services generate triples; the predicates of those triples are indexed... Period. For a given query, determine which properties are available, and which need to be discovered/generated Find services that generate the properties we need
82. Semantic Web An information system where machines can receive information from one source, re-interpret it, and correctly use it for a purpose that the source had not anticipated. My Purpose!!
83. What SADI + SHARE supports Re-interpretation We constantly compare the collection of properties, gathered from third-parties worldwide, to whatever world-model (query/ontology) we wish to view it through. MY world model
84. What SADI + SHARE supports Novel re-use There is no way for the provider to dictate how their data should be used, or how it should be interpreted. They simply add their properties into the “cloud” and those properties are used in whatever way is appropriate for me.
85. Important “wins” Data remains distributed – no warehouse! Data is not “exposed” as a SPARQL endpoint greater provider-control over computational resources Yet data appears to be a SPARQL endpoint… no modification of SPARQL or reasoner required.
86. And all this because SADI simply requires that the input URI is the same as the output URI
87. Join us! We have recently received funding from CANARIEto assist and train service providersin deploying their own SADI Semantic Web Services Come join us – we’re having a lot of fun!! http://sadiframework.org
88. Credits Benjamin VanderValk (SADI & CardioSHARE) Luke McCarthy (SADI & CardioSHARE) SoroushSamadian (CardioSHARE) Microsoft Research Fin This presentation available on SlideShare: keywords ‘wilkinson’ ‘BioIT-2010’
89. Credits Benjamin VanderValk(SADI & CardioSHARE) Luke McCarthy (SADI & CardioSHARE) SoroushSamadian(CardioSHARE)