Carole Goble<br />“Shopping for data should be as easy as shopping for shoes!!”<br />
The Semantic Web<br />This time… it’s personal!<br />Mark Wilkinson, PI Bioinformatics, Heart + Lung Institute @ St. Paul’...
My Lab<br />
Engineering <br />& <br />Research<br />
Programmers<br />& <br />Students<br />
Coolness!<br />& <br />Study of Coolness!<br />
Middleware<br />
Robert Stevens<br />
Shouldn’t beseen!<br />
DEMO...to give you incentive to listen to the rest of the presentation <br />
Show me patients with elevated creatinine along with their latest BUN and creatinine levels<br />PREFIX rdf: <http://www.w...
VOILA!<br />
There was no database... <br />
There was no warehouse...<br />
There was no patient data anywhere annotated as “Elevated Creatinine Patient”<br />
How did I answer a question where the required data didn’t exist?<br />(...no, I didn’t just make it up LOL!)<br />
In the beginning was the problem...<br />
The Problem<br />
The Problem<br />
The Holy Grail:(circa 2002)<br />Align the promoters of all serine threonine kinases involved exclusively in the regulatio...
The Problem<br />
The Problem<br />
The Solution??<br />
Why not?<br />Heart<br />Heart<br />
You don’t know what I know!<br />
You don’t thinkhow I think!<br />
No Personalization!<br />
So… what can we do?<br />
What we need<br />
How do we make Bruce’s knowledge machine-readable?<br />
Ontologies!<br />
Two Problems with that…<br />
#1 Ontology Spectrum<br />Frames<br />(Properties)<br />Thesauri<br />“narrower<br />term”<br />relation<br />Selected<br ...
#1 Ontology Spectrum<br />Frames<br />(Properties)<br />Thesauri<br />“narrower<br />term”<br />relation<br />Selected<br ...
#1 Ontology Spectrum<br />WHY?<br />Frames<br />(Properties)<br />Thesauri<br />“narrower<br />term”<br />relation<br />Se...
#1 Ontology Spectrum<br />Because it fulfils XYZ<br />WHY?<br />Frames<br />(Properties)<br />Thesauri<br />“narrower<br /...
Because I say so?!?That’s not very... Personal...<br />
No room for disagreement<br />
No place for scientific discourse<br />
It is what it is...Because I say so!<br />
Clay Shirky“Ontology is over-rated”http://www.shirky.com/writings/ontology_overrated.html<br />
If we’re going to personalize the Semantic WebWe must change the way we create and use classification systems(“shelves”)<b...
“Get rid of the shelf”- Clay Shirkey<br />
You don’t know what I know!<br />
So don’t tell MEhow data should be interpreted!<br />
How do we get rid of the shelf?<br />
This is going to hurt...<br />
Web Servicesvs.Semantic Web<br />
Web Servicesare not “connected” to the Semantic WebWhy?<br />
Web ServicesXML + XML SchemaSemantic WebRDF + OWL<br />
Web ServicesPOST of SOAP-XMLSemantic WebGET of RDF-XML<br />
Web ServicesNo (rigorous) semanticsSemantic WebRich, flexible semantics<br />
Web Services&Semantic WebFundamentally and deeply different Web technologies! <br />
>1000 X more data!<br />
Accessing these databases and analytical algorithms “transparently”, based on an individual researcher’s <br />ideas, beli...
Mark Butler (2003) Is the semantic web hype? Hewlett Packard laboratories presentation at MMU, 2003-03-12<br />
Semantic Web?(my definition)<br />An information system where machines can receive information from one source,re-interpre...
Re-interpretation<br />Correct re-use<br />Both are critical to the personalization of research<br />
Building a personalized Semantic Web…<br />Step-by-step…<br />
Semantic Automated Discovery and Integrationhttp://sadiframework.org(open source)<br />MicrosoftResearch<br />Founding par...
“best-practices” for Semantic Web Service provision<br />
standards-compliant<br />
Lightweight(only 2 “rules”)<br />
Rules come from observations:<br />
SADI Observation #1:<br />Web Services in Bioinformatics create implicitbiologicalrelationships between their input and ou...
SADI Observation #1:<br />
SADI Best Practice #1<br />Make the implicit explicit…<br />A Web Service should create “triples” linking the input data t...
SADI Best Practice #1<br />This is what bioinformatics Web Services implicitly do anyway! Easy to implement this as a best...
SADI Observation #2:HTTP GET and POST<br />GET guarantees the response relates to the request URI in a very precise and pr...
SADI Observation #2:GET and POST<br />That’s why Web Services have a fundamentally different behaviour than the Semantic W...
SADI Observation #2:GET and POST<br />We can fix that!<br />(without breaking any existing rules or standards!)<br />
SADI Best Practice #2<br />SUBJECT URI of the output graph (triples)<br /> is the sameas the SUBJECT URI of the input grap...
Consequence<br />The “Semantics” of our interaction with the Web Service are now explicitandidentical to the “Semantics” o...
SADI Web Service Interfaces<br />Service Interfaces defined by two OWL classes:<br />
SADI Web Service Interfaces<br />OWL Class #1:  My Input Class<br />
SADI Web Service Interfaces<br />OWL Class #2:  My Output Class<br />
SADI Web Service Interfaces<br />My Service consumes OWL Individuals of Class #1and returns OWL Individuals of Class #2<br...
How do we discover services?<br />Since input and output are about the same “thing”, we can automatically determine what a...
How do we discover services?<br />Automatically index services in a registry based on what properties (predicates) Service...
EXAMPLE<br />  Input Data:  BRCA1   rdf:type    Gene ID<br />  Output Data:     BRCA1    hasDNASequence    AGCTTAGCCA…<br ...
Now we can answer questions like <br />“what is the DNA sequence of BRCA1?”<br /> Discover a SADI Web Service that genera...
Okay, enough tech gobbledygookWhat will this do for ME?<br />
Demo #1<br />
Imagine there is a “virtual database” containing all of the data from all of the databases,together with the output ofever...
How do we query that database?<br />
“SHARE”Semantic Health And Research EnvironmentSADI client application<br />
What pathways does UniProt protein P47989 belong to?<br />PREFIX pred: <http://sadiframework.org/ontologies/predicates.owl...
Recapwhat we just saw<br />A standard SPARQL query was entered into SHARE, a SADI-aware query engine<br />
Recapwhat we just saw<br />The query was interpreted to extract the properties being queried and these were passed to SADI...
Recapwhat we just saw<br />SADIsearched-for, found, and accessed all databases and/or analytical tools capable of generati...
Recapwhat we just saw<br />We posed, and answered a complex database query <br />WITHOUT A DATABASE<br />(in fact, the dat...
The Holy Grail:<br />Align the promoters of all serine threonine kinases involved exclusively in the regulation of cell so...
Cool!<br />
 …but I’m supposed to be personalizing research…<br />Let’s make this a little more personal by bringing in Ontologies<br />
My Definition of Ontology (for this talk)<br />Ontologies explicitly define the things that exist in “the world” based on ...
 Ontology Spectrum<br />Frames<br />(Properties)<br />Thesauri<br />“narrower<br />term”<br />relation<br />Selected<br />...
Demo #2<br />Discover instances of OWL classes <br />from data that doesn’t exist…<br />
Data exhibits “late binding”<br />
Late binding:“purpose and meaning” <br />of the data isnot determined untilthe moment it is required<br />
Benefit<br />of late binding<br />Data is amenable to<br />constant re-interpretation <br />...MY interpretation<br />
How?<br />DO NOT <br />PRE-CLASSIFY DATA<br />Just hang properties on it<br />
Ontologies are in the “Frames” area of the Ontology spectrum, and therefore can leverage SADI and be “executed” as workflo...
???<br />
Did you just say<br /> “execute ontologies as workflows?!”<br />
Show me patients with elevated creatinine along with their latest BUN and creatinine levels<br />PREFIX rdf: <http://www.w...
Start burrowing through the OWL class  find that we need aregression model OWL class<br />
Regression models have features like slopes and intercepts… and so onThe class is completely decomposed until a set of req...
Successful decomposition of the OWL class to discover <br />the need for a LinearRegression Web Service, and so on<br />
VOILA!<br />
Current Research ProjectBenjamin VandervalkThere are many ways to resolve these ontologies and queries into workflowsMy st...
The Holy Grail:<br />Align the promoters of all serine threonine kinases involved exclusively in the regulation of cell so...
OWL Class restrictions converted into workflows<br />SPARQL queries converted into workflows<br />Reasoning happening in p...
I still don’t seehow this is“Personal”??<br />
SELECT ?patient ?bun ?creat<br />FROM <http://sadiframework.org/ontologies/patients.rdf><br />WHERE {<br />	?patient rdf:t...
I created a small ontologydescribing my definition ofan Elevated Creatinine Patient<br />
… it was MY ontology!<br />
I can re-use it<br />
I can modify it as I change myworld-view<br />
I can publish it for others to use<br />
Others can modify it to fit THEIRworld-view<br />
My personal world-view is being dynamically resolved againstglobal data and knowledge<br />
…but it’s bigger than that…<br />
“Elevated Creatinine Patient”<br />
I made that up!  It came out of my head!<br />
What’s another word for a world-view that you make-up?<br />Hypothesis<br />
Current Research Project We believe that ontologies and hypothesesare, in some ways, the same “thing”……simply assertions a...
Current Research ProjectSoroushSamadiane-Copy Clinical Outcomes investigations to determine if Outcomes hypothesescan be m...
Recap<br />SADI Semantic Web Services generate triples; the predicates of those triples are indexed... Period.<br />For a ...
Semantic Web<br />An information system where machines can receive information from one source, re-interpret it, and corre...
What SADI + SHARE supports<br />Re-interpretation<br />We constantly compare the collection of properties, gathered from t...
What SADI + SHARE supports<br />Novel re-use<br />There is no way for the provider to dictate how their data should be use...
And all this because SADI simply requires<br />that the input URI <br />is the same <br />as the output URI<br />
Important “wins”<br />
Data remains distributed<br />no warehouse!<br />
Data is not “exposed” as a SPARQL endpoint<br />greater provider-control over computational resources<br />
Semi-automated  SADI service writing and deployment<br />Taverna<br />Semantically-guided  SADI service discovery and pipe...
Where do we go from here?<br />
Consent<br />
Who defines my consent?<br />
IRB<br />(in Canada REB)<br />
Where’s MY opinionin that process?<br />
New Research Project - iConsent<br />I define an ontology describing the conditions under which I would allow my bio/medic...
New Research Project - iConsent<br />Researchers approach the database with an “instance” of their study (e.g. an instance...
New Research Project - iConsent<br />For Patient:<br />Personalized access to personal information<br />Much more granular...
New Research Project - iConsent<br />For Researcher:<br />Access to more data from willing patients<br />Automated profili...
Simple and Open WINS!<br />Join us!<br />We have recently received funding from CANARIEto assist and train service provide...
                          Credits<br />Benjamin VanderValk (SADI & CardioSHARE)<br />Luke McCarthy (SADI & CardioSHARE)<br...
 Credits<br />Benjamin VanderValkMSc Student <br />Bioinformatics Training Programme<br />Luke McCarthy Lead Programmer, S...
Microsoft Research<br />
Upcoming SlideShare
Loading in …5
×

The Semantic Web - This time... its Personal

1,092 views
1,073 views

Published on

My presentation on SADI, SHARE, CardioSHARE, and the new iConsent project. Presented to the faculty and students at Stanford Medical Informatics, Palo Alto, USA. May 14th, 2010.

How do we make the semantic web, and medical research, more personal? (both for the researcher and for the patient) I present some ideas we're exploring

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,092
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
18
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

The Semantic Web - This time... its Personal

  1. 1. Carole Goble<br />“Shopping for data should be as easy as shopping for shoes!!”<br />
  2. 2. The Semantic Web<br />This time… it’s personal!<br />Mark Wilkinson, PI Bioinformatics, Heart + Lung Institute @ St. Paul’s Hospital<br />Vancouver, BC, Canada<br />
  3. 3. My Lab<br />
  4. 4. Engineering <br />& <br />Research<br />
  5. 5. Programmers<br />& <br />Students<br />
  6. 6. Coolness!<br />& <br />Study of Coolness!<br />
  7. 7. Middleware<br />
  8. 8. Robert Stevens<br />
  9. 9.
  10. 10. Shouldn’t beseen!<br />
  11. 11.
  12. 12. DEMO...to give you incentive to listen to the rest of the presentation <br />
  13. 13. Show me patients with elevated creatinine along with their latest BUN and creatinine levels<br />PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> <br />PREFIX patients: <http://sadiframework.org/ontologies/patients.owl#> <br />PREFIX pred: <http://sadiframework.org/ontologies/predicates.owl#> <br />SELECT ?patient ?bun ?creat<br />FROM <http://sadiframework.org/ontologies/patients.rdf><br />WHERE {<br /> ?patient rdf:typepatients:ElevatedCreatininePatient .<br /> ?patient pred:latestBUN ?bun . <br /> ?patient pred:latestCreatinine ?creat . <br />}<br />
  14. 14. VOILA!<br />
  15. 15. There was no database... <br />
  16. 16. There was no warehouse...<br />
  17. 17. There was no patient data anywhere annotated as “Elevated Creatinine Patient”<br />
  18. 18. How did I answer a question where the required data didn’t exist?<br />(...no, I didn’t just make it up LOL!)<br />
  19. 19. In the beginning was the problem...<br />
  20. 20. The Problem<br />
  21. 21. The Problem<br />
  22. 22. The Holy Grail:(circa 2002)<br />Align the promoters of all serine threonine kinases involved exclusively in the regulation of cell sorting during wound healing in blood vessels.<br />Retrieve and align 2000nt 5' from every serine/threonine kinase in Mus musculus expressed exclusively in the tunica [I | M |A] whose expression increases 5X or more within 5 hours of wounding but is not activated during the normal development of blood vessels, and is <40% homologous in the active site to kinases known to be involved in cell-cycle regulation in any other species.<br />
  23. 23. The Problem<br />
  24. 24. The Problem<br />
  25. 25. The Solution??<br />
  26. 26. Why not?<br />Heart<br />Heart<br />
  27. 27. You don’t know what I know!<br />
  28. 28. You don’t thinkhow I think!<br />
  29. 29. No Personalization!<br />
  30. 30. So… what can we do?<br />
  31. 31. What we need<br />
  32. 32. How do we make Bruce’s knowledge machine-readable?<br />
  33. 33. Ontologies!<br />
  34. 34. Two Problems with that…<br />
  35. 35. #1 Ontology Spectrum<br />Frames<br />(Properties)<br />Thesauri<br />“narrower<br />term”<br />relation<br />Selected<br />Logical<br /> Constraints<br />(disjointness, <br />inverse, …) <br />Catalog/<br />ID<br />Formal<br />is-a<br />Informal<br />is-a<br />Formal<br />instance<br />General<br />Logical<br />constraints<br />Terms/<br />glossary<br />Value Restrs.<br />Originally from AAAI 1999- Ontologies Panel by Gruninger, Lehmann, McGuinness, Uschold, Welty;<br /> – updated by McGuinness.<br />Description in: www.ksl.stanford.edu/people/dlm/papers/ontologies-come-of-age-abstract.html<br />
  36. 36. #1 Ontology Spectrum<br />Frames<br />(Properties)<br />Thesauri<br />“narrower<br />term”<br />relation<br />Selected<br />Logical<br /> Constraints<br />(disjointness, <br />inverse, …) <br />Catalog/<br />ID<br />Formal<br />is-a<br />Informal<br />is-a<br />Formal<br />instance<br />General<br />Logical<br />constraints<br />Terms/<br />glossary<br />Value Restrs.<br />
  37. 37. #1 Ontology Spectrum<br />WHY?<br />Frames<br />(Properties)<br />Thesauri<br />“narrower<br />term”<br />relation<br />Selected<br />Logical<br /> Constraints<br />(disjointness, <br />inverse, …) <br />Catalog/<br />ID<br />Formal<br />is-a<br />Informal<br />is-a<br />Formal<br />instance<br />General<br />Logical<br />constraints<br />Terms/<br />glossary<br />Value Restrs.<br />
  38. 38. #1 Ontology Spectrum<br />Because it fulfils XYZ<br />WHY?<br />Frames<br />(Properties)<br />Thesauri<br />“narrower<br />term”<br />relation<br />Selected<br />Logical<br /> Constraints<br />(disjointness, <br />inverse, …) <br />Catalog/<br />ID<br />Formal<br />is-a<br />Informal<br />is-a<br />Formal<br />instance<br />General<br />Logical<br />constraints<br />Terms/<br />glossary<br />Value Restrs.<br />BecauseI say so!<br />
  39. 39. Because I say so?!?That’s not very... Personal...<br />
  40. 40.
  41. 41. No room for disagreement<br />
  42. 42. No place for scientific discourse<br />
  43. 43. It is what it is...Because I say so!<br />
  44. 44. Clay Shirky“Ontology is over-rated”http://www.shirky.com/writings/ontology_overrated.html<br />
  45. 45. If we’re going to personalize the Semantic WebWe must change the way we create and use classification systems(“shelves”)<br />
  46. 46. “Get rid of the shelf”- Clay Shirkey<br />
  47. 47. You don’t know what I know!<br />
  48. 48. So don’t tell MEhow data should be interpreted!<br />
  49. 49. How do we get rid of the shelf?<br />
  50. 50. This is going to hurt...<br />
  51. 51. Web Servicesvs.Semantic Web<br />
  52. 52. Web Servicesare not “connected” to the Semantic WebWhy?<br />
  53. 53. Web ServicesXML + XML SchemaSemantic WebRDF + OWL<br />
  54. 54. Web ServicesPOST of SOAP-XMLSemantic WebGET of RDF-XML<br />
  55. 55. Web ServicesNo (rigorous) semanticsSemantic WebRich, flexible semantics<br />
  56. 56. Web Services&Semantic WebFundamentally and deeply different Web technologies! <br />
  57. 57.
  58. 58. >1000 X more data!<br />
  59. 59. Accessing these databases and analytical algorithms “transparently”, based on an individual researcher’s <br />ideas, beliefs, and preferenceswill help us personalize medical research<br />
  60. 60. Mark Butler (2003) Is the semantic web hype? Hewlett Packard laboratories presentation at MMU, 2003-03-12<br />
  61. 61. Semantic Web?(my definition)<br />An information system where machines can receive information from one source,re-interpret it, and correctly use itfor a purpose that the source had not anticipated.<br />
  62. 62. Re-interpretation<br />Correct re-use<br />Both are critical to the personalization of research<br />
  63. 63. Building a personalized Semantic Web…<br />Step-by-step…<br />
  64. 64. Semantic Automated Discovery and Integrationhttp://sadiframework.org(open source)<br />MicrosoftResearch<br />Founding partner<br />
  65. 65. “best-practices” for Semantic Web Service provision<br />
  66. 66. standards-compliant<br />
  67. 67. Lightweight(only 2 “rules”)<br />
  68. 68. Rules come from observations:<br />
  69. 69. SADI Observation #1:<br />Web Services in Bioinformatics create implicitbiologicalrelationships between their input and output<br />
  70. 70. SADI Observation #1:<br />
  71. 71. SADI Best Practice #1<br />Make the implicit explicit…<br />A Web Service should create “triples” linking the input data to the output data, thus explicitly describing the semantic relationship between them <br />
  72. 72. SADI Best Practice #1<br />This is what bioinformatics Web Services implicitly do anyway! Easy to implement this as a best-practice<br />
  73. 73. SADI Observation #2:HTTP GET and POST<br />GET guarantees the response relates to the request URI in a very precise and predictable way<br />POST does not…<br />
  74. 74. SADI Observation #2:GET and POST<br />That’s why Web Services have a fundamentally different behaviour than the Semantic Web<br />
  75. 75. SADI Observation #2:GET and POST<br />We can fix that!<br />(without breaking any existing rules or standards!)<br />
  76. 76. SADI Best Practice #2<br />SUBJECT URI of the output graph (triples)<br /> is the sameas the SUBJECT URI of the input graph (triples)<br />(the output is “about” the input... Now explicitly!)<br />
  77. 77. Consequence<br />The “Semantics” of our interaction with the Web Service are now explicitandidentical to the “Semantics” of GET<br />
  78. 78. SADI Web Service Interfaces<br />Service Interfaces defined by two OWL classes:<br />
  79. 79. SADI Web Service Interfaces<br />OWL Class #1: My Input Class<br />
  80. 80. SADI Web Service Interfaces<br />OWL Class #2: My Output Class<br />
  81. 81. SADI Web Service Interfaces<br />My Service consumes OWL Individuals of Class #1and returns OWL Individuals of Class #2<br />…but the URI of those two individuals is the same!(see best practice #2)<br />
  82. 82. How do we discover services?<br />Since input and output are about the same “thing”, we can automatically determine what a service doesby comparing the Input and Output OWL classes<br />
  83. 83. How do we discover services?<br />Automatically index services in a registry based on what properties (predicates) Services add to their respective input data<br />
  84. 84. EXAMPLE<br /> Input Data: BRCA1 rdf:type Gene ID<br /> Output Data: BRCA1 hasDNASequence AGCTTAGCCA…<br /> Registry Index: Service provides “hasDNASequence” property to Gene IDs<br />
  85. 85. Now we can answer questions like <br />“what is the DNA sequence of BRCA1?”<br /> Discover a SADI Web Service that generates the DNA Sequence property for gene identifiers<br />
  86. 86. Okay, enough tech gobbledygookWhat will this do for ME?<br />
  87. 87. Demo #1<br />
  88. 88. Imagine there is a “virtual database” containing all of the data from all of the databases,together with the output ofevery conceivable analysis<br />
  89. 89. How do we query that database?<br />
  90. 90. “SHARE”Semantic Health And Research EnvironmentSADI client application<br />
  91. 91. What pathways does UniProt protein P47989 belong to?<br />PREFIX pred: <http://sadiframework.org/ontologies/predicates.owl#><br />PREFIX ont: <http://ontology.dumontierlab.com/><br />PREFIX uniprot: <http://lsrn.org/UniProt:><br />SELECT ?gene ?pathway <br />WHERE { <br /> uniprot:P47989 pred:isEncodedBy ?gene . <br /> ?gene ont:isParticipantIn ?pathway . <br />}<br />
  92. 92.
  93. 93.
  94. 94.
  95. 95. Recapwhat we just saw<br />A standard SPARQL query was entered into SHARE, a SADI-aware query engine<br />
  96. 96. Recapwhat we just saw<br />The query was interpreted to extract the properties being queried and these were passed to SADI for Web Service discovery<br />
  97. 97. Recapwhat we just saw<br />SADIsearched-for, found, and accessed all databases and/or analytical tools capable of generating those properties<br />
  98. 98. Recapwhat we just saw<br />We posed, and answered a complex database query <br />WITHOUT A DATABASE<br />(in fact, the data didn’t even have to exist...)<br />
  99. 99. The Holy Grail:<br />Align the promoters of all serine threonine kinases involved exclusively in the regulation of cell sorting during wound healing in blood vessels.<br />Retrieve and align 2000nt 5' from every serine/threonine kinase in Mus musculus expressed exclusively in the tunica [I | M |A] whose expression increases 5X or more within 5 hours of wounding but is not activated during the normal development of blood vessels, and is <40% homologous in the active site to kinases known to be involved in cell-cycle regulation in any other species.<br />
  100. 100. Cool!<br />
  101. 101. …but I’m supposed to be personalizing research…<br />Let’s make this a little more personal by bringing in Ontologies<br />
  102. 102. My Definition of Ontology (for this talk)<br />Ontologies explicitly define the things that exist in “the world” based on what propertieseach kind of thing must have<br />
  103. 103. Ontology Spectrum<br />Frames<br />(Properties)<br />Thesauri<br />“narrower<br />term”<br />relation<br />Selected<br />Logical<br /> Constraints<br />(disjointness, <br />inverse, …) <br />Catalog/<br />ID<br />Formal<br />is-a<br />Informal<br />is-a<br />Formal<br />instance<br />General<br />Logical<br />constraints<br />Terms/<br />glossary<br />Value Restrs.<br />
  104. 104. Demo #2<br />Discover instances of OWL classes <br />from data that doesn’t exist…<br />
  105. 105. Data exhibits “late binding”<br />
  106. 106.
  107. 107. Late binding:“purpose and meaning” <br />of the data isnot determined untilthe moment it is required<br />
  108. 108. Benefit<br />of late binding<br />Data is amenable to<br />constant re-interpretation <br />...MY interpretation<br />
  109. 109. How?<br />DO NOT <br />PRE-CLASSIFY DATA<br />Just hang properties on it<br />
  110. 110. Ontologies are in the “Frames” area of the Ontology spectrum, and therefore can leverage SADI and be “executed” as workflows<br />
  111. 111. ???<br />
  112. 112. Did you just say<br /> “execute ontologies as workflows?!”<br />
  113. 113. Show me patients with elevated creatinine along with their latest BUN and creatinine levels<br />PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> <br />PREFIX patients: <http://sadiframework.org/ontologies/patients.owl#> <br />PREFIX pred: <http://sadiframework.org/ontologies/predicates.owl#> <br />SELECT ?patient ?bun ?creat<br />FROM <http://sadiframework.org/ontologies/patients.rdf><br />WHERE {<br /> ?patient rdf:typepatients:ElevatedCreatininePatient .<br /> ?patient pred:latestBUN ?bun . <br /> ?patient pred:latestCreatinine ?creat . <br />}<br />
  114. 114. Start burrowing through the OWL class  find that we need aregression model OWL class<br />
  115. 115. 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<br />
  116. 116. Successful decomposition of the OWL class to discover <br />the need for a LinearRegression Web Service, and so on<br />
  117. 117. VOILA!<br />
  118. 118. Current Research ProjectBenjamin VandervalkThere are many ways to resolve these ontologies and queries into workflowsMy student Benjamin is currently studying optimization of this query resolution strategyInteresting counterpart to DBMS query resolution because there are no indices for Web Services, and other issues (e.g. Service speed) are an important factor.<br />
  119. 119. The Holy Grail:<br />Align the promoters of all serine threonine kinases involved exclusively in the regulation of cell sorting during wound healing in blood vessels.<br />Retrieve and align 2000nt 5' from every serine/threonine kinase in Mus musculus expressed exclusively in the tunica [I | M |A] whose expression increases 5X or more within 5 hours of wounding but is not activated during the normal development of blood vessels, and is <40% homologous in the active site to kinases known to be involved in cell-cycle regulation in any other species.<br />
  120. 120. OWL Class restrictions converted into workflows<br />SPARQL queries converted into workflows<br />Reasoning happening in parallel with query executionData fulfilling OWL models is discovered, or generated through running analytical tools<br />SADI and CardioSHARE<br />
  121. 121. I still don’t seehow this is“Personal”??<br />
  122. 122. SELECT ?patient ?bun ?creat<br />FROM <http://sadiframework.org/ontologies/patients.rdf><br />WHERE {<br /> ?patient rdf:typepatients:ElevatedCreatininePatient .<br /> ?patient pred:latestBUN ?bun . <br /> ?patient pred:latestCreatinine ?creat . <br />}<br />
  123. 123. I created a small ontologydescribing my definition ofan Elevated Creatinine Patient<br />
  124. 124. … it was MY ontology!<br />
  125. 125. I can re-use it<br />
  126. 126. I can modify it as I change myworld-view<br />
  127. 127. I can publish it for others to use<br />
  128. 128. Others can modify it to fit THEIRworld-view<br />
  129. 129.
  130. 130. My personal world-view is being dynamically resolved againstglobal data and knowledge<br />
  131. 131. …but it’s bigger than that…<br />
  132. 132. “Elevated Creatinine Patient”<br />
  133. 133. I made that up! It came out of my head!<br />
  134. 134. What’s another word for a world-view that you make-up?<br />Hypothesis<br />
  135. 135. Current Research Project We believe that ontologies and hypothesesare, in some ways, the same “thing”……simply assertions about individuals that may or may not exist<br />
  136. 136. Current Research ProjectSoroushSamadiane-Copy Clinical Outcomes investigations to determine if Outcomes hypothesescan be modeled as OWL ontologies and automatically resolved by SHARE<br />
  137. 137. Recap<br />SADI Semantic Web Services generate triples; the predicates of those triples are indexed... Period.<br />For a given query, determine which properties are available, and which need to be discovered/generated<br />Find services that generate the properties we need<br />
  138. 138. Semantic Web<br />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.<br />My Purpose!!<br />
  139. 139. What SADI + SHARE supports<br />Re-interpretation<br />We constantly compare the collection of properties, gathered from third-parties worldwide, to whatever world-model (query/ontology) we wish to view it through.<br />MY world model<br />
  140. 140. What SADI + SHARE supports<br />Novel re-use<br />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 “data cloud” and those properties are used in whatever way is appropriate forME.<br />
  141. 141. And all this because SADI simply requires<br />that the input URI <br />is the same <br />as the output URI<br />
  142. 142. Important “wins”<br />
  143. 143. Data remains distributed<br />no warehouse!<br />
  144. 144. Data is not “exposed” as a SPARQL endpoint<br />greater provider-control over computational resources<br />
  145. 145. Semi-automated SADI service writing and deployment<br />Taverna<br />Semantically-guided SADI service discovery and pipelining<br />SADI Plug-ins<br />
  146. 146. Where do we go from here?<br />
  147. 147.
  148. 148.
  149. 149. Consent<br />
  150. 150. Who defines my consent?<br />
  151. 151. IRB<br />(in Canada REB)<br />
  152. 152. Where’s MY opinionin that process?<br />
  153. 153. New Research Project - iConsent<br />I define an ontology describing the conditions under which I would allow my bio/medical data to be used<br />Type of study, funding source, type of information<br />Highly granular, highly detailed<br />Highly PERSONAL<br />
  154. 154. New Research Project - iConsent<br />Researchers approach the database with an “instance” of their study (e.g. an instance of the OBI)<br />Semantic negotiation between my ontology and their study parameters determines which aspects of my data they are allowed access to (if any)<br />
  155. 155. New Research Project - iConsent<br />For Patient:<br />Personalized access to personal information<br />Much more granular than current consent models<br />
  156. 156. New Research Project - iConsent<br />For Researcher:<br />Access to more data from willing patients<br />Automated profiling of data you weren’t allowed access to – detection of sample bias!<br />
  157. 157. Simple and Open WINS!<br />Join us!<br />We have recently received funding from CANARIEto assist and train service providersin deploying their own SADISemantic Web Services<br />Come join us – we’re having a lot of fun!!<br />http://sadiframework.org<br />http://twitter.com/sadiframework<br />
  158. 158. Credits<br />Benjamin VanderValk (SADI & CardioSHARE)<br />Luke McCarthy (SADI & CardioSHARE)<br />SoroushSamadian (CardioSHARE)<br />Microsoft Research<br />Fin <br />This presentation available on SlideShare: keywords ‘sadi’, ‘wilkinson’<br />
  159. 159. Credits<br />Benjamin VanderValkMSc Student <br />Bioinformatics Training Programme<br />Luke McCarthy Lead Programmer, SADI<br />SoroushSamadian<br />PhD Student<br />Bioinformatics Training Programme<br />
  160. 160. Microsoft Research<br />

×