Building Semantic Web Based Applications with Watson

1,517
-1

Published on

Published in: Technology, Education
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,517
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
75
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide
  • I will not go into the details
  • I will not go into the details…
  • 1- human 2- Web services/API/Programs
  • What can the semantic web do bring to e-learning: knowledge and data….
  • What can the semantic web do bring to e-learning: knowledge and data….
  • Building Semantic Web Based Applications with Watson

    1. 1. Building Semantic Web Based Applications with Watson Mathieu d’Aquin and many other people The Knowledge Media Institute, The Open University [email_address]
    2. 2. The Semantic Web is growing http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData
    3. 3. Next Generation Semantic Web Applications Dynamically retrieving, exploiting and combining relevant semantic resources from the SW, at large Need for a Gateway to the Semantic Web
    4. 4. Next Generation Semantic Web Applications
    5. 5. Architecture
    6. 6. Collection
    7. 7. Interfaces: WUI <ul><li>Web User Interface: http://watson.kmi.open.ac.uk/WatsonWUI </li></ul>
    8. 8. Web services and API <ul><li>A SOAP Based API that provides the infrastructure to: </li></ul><ul><ul><li>F ind SW documents and retrieve metadata about them </li></ul></ul><ul><ul><li>Find entities (classes, properties, individuals) and explore their semantic description </li></ul></ul><ul><ul><li>Apply SPARQL queries to Semantic Web documents </li></ul></ul><ul><li>An initial REST Based API </li></ul><ul><li>But what applications (can) do with it? </li></ul>
    9. 9. Demonstrator: gowgle/wahoo <ul><li>An extension of a web search engine that suggests ways to extend a query thanks to online ontologies </li></ul><ul><li>Example with the query “ researcher ” </li></ul><ul><ul><li>Suggests “academic staff”, “Person”, etc. as terms to generalize the query, and </li></ul></ul><ul><ul><li>“ professor”, “PhD student” as terms to specialize the query </li></ul></ul><ul><ul><li>Without having to give the system any knowledge: everything comes from the Web! </li></ul></ul><ul><li>2 Versions: </li></ul><ul><ul><li>Gowgle (http://watson.kmi.open.ac.uk/gowgle): use the Google SOAP API and the Watson SOAP API </li></ul></ul><ul><ul><li>Wahoo (http://watson.kmi.open.ac.uk/wahoo): use the Yahoo! REST API and the Watson REST API </li></ul></ul>
    10. 10. Query Result from Yahoo! Term suggestions Add/Replace Screenshot of wahoo (REST based)
    11. 11. How to do it? <ul><li>Find ontologies containing the keyword “researcher” </li></ul><ul><ul><li>http://watson.kmi.open.ac.uk/API/semanticcontent/keywords?q= researcher </li></ul></ul><ul><li>… exactly “researcher” in the label or id of a class </li></ul><ul><ul><li>http://watson.kmi.open.ac.uk/API/semanticcontent/keywords?q= researcher &scope= LN+Label &ent= Class &match= Exact </li></ul></ul><ul><li>Find entities corresponding to “researcher” in ontology </li></ul><ul><ul><li>http://watson.kmi.open.ac.uk/API/entity/keyword?q= researcher &uri= http://calo.sri.com/core-plus-office &scope= LN+Label &ent= Class &match= Exact </li></ul></ul><ul><li>Find subclasses and superclasses of an entity </li></ul><ul><ul><li>http://watson.kmi.open.ac.uk/API/entity/subclasses? ent=http://calo.sri.com/core-plus-office#Researcher &uri= http://calo. sri.com/core-plus-office </li></ul></ul><ul><li>The rest is interface stuff and call to Yahoo! </li></ul>
    12. 12. Other functions <ul><li>Wahoo uses only a subset of the possibilities of the Watson API </li></ul><ul><li>Functions on SW documents (in SOAP and soon in REST): </li></ul>Find SW documents: listSemanticContents getSemanticContentByKeywords getSemanticContentByKeywordsWithRestrictions getBestCoverageWithRestrictions Basic Metadata: getCacheLocation getSemanticContentLocation getImports getNumberOfStatement getSizeInBytes getSemanticContentLanguages getDLExpressivness Content: listClasses listIndividuals listProperties executeSPARQLQuery Reviews (from Revyu.com): getNumbearOfReviews getAverageRating getRevyuURL
    13. 13. Other functions <ul><li>Functions on entities (in SOAP and soon in REST): </li></ul>Find Entities: getEntitiesByKeyword getEntitiesByKeywordWithRestriction getBelongsTo Relations: getRelationsFrom getRelationsTo getClasses getDifferentFrom getDisjointWith getDomain getDomainOf getEquivalentClasse getInstances getRange getRangeOf getSameIndividual getSubClasse getSuperClasses Literals: getLiteralsFor getLabels getComment
    14. 14. Real Applications <ul><li>PowerMagpie : Semantic Browsing </li></ul><ul><li>PowerAqua : Question Answering </li></ul><ul><li>Flor : Folksonomy Enrichment </li></ul><ul><li>MOAW : Putting URIs everywhere </li></ul><ul><li>Watson Plugin : Large Scale Knolwedge reuse in Ontology Engineering </li></ul><ul><li>Scarlet : Relation Discovery </li></ul><ul><li>Word Sense Disambiguation, Data Validation, … </li></ul>
    15. 15. And so… <ul><li>Watson is an ongoing work to build an infrastructure supporting the development of SW applications </li></ul><ul><ul><li>Room for contributions ;-) </li></ul></ul><ul><ul><li>And building applications is a form of contribution! </li></ul></ul><ul><li>Many additions currently in development </li></ul><ul><ul><li>Presentation of SW Documents/Ontologies, Ontology Summarization, Modularization </li></ul></ul><ul><ul><li>Classification of SW Documents/Ontologies, ontology directory </li></ul></ul><ul><ul><li>Infrastructure for publishing SW data/ontologies, data hosting </li></ul></ul><ul><ul><li>Efficient cross ontology querying </li></ul></ul><ul><ul><li>Detecting and managing relations between SW documents/ontologies (equivalences, similarity, versions, compatibility, etc.) </li></ul></ul><ul><ul><li>Combining automatic evaluation, user evaluation and trust for (customized) ranking </li></ul></ul><ul><ul><li>Exchange with the p2p networks for ontology sharing </li></ul></ul>
    16. 16. Thank you! Watson: http://watson.kmi.open.ac.uk Blog: http://watson.kmi.open.ac.uk/blog Mailing list: [email_address] Contact: [email_address]
    17. 17. The Semantic Web is growing… Lee, J., Goodwin, R. (2004) The Semantic Webscape: a View of the Semantic Web. IBM Research Report .
    18. 18. Ontologies Metadata <rdf:RDF> <channel rdf:about=“http://watson.kmi.open.ac.uk/blog”> <title>Elementaries - The Watson Blog</title> <link>http://watson.kmi.open.ac.uk:8080/blog/</link> <description> &quot;Oh dear! Where the Semantic Web is going to go now?&quot; -- imaginary user 23 </description> <language>en</language> <copyright>Watson team</copyright> <lastBuildDate>Thu, 01 Mar 2007 13:49:52 GMT</lastBuildDate> <generator>Pebble (http://pebble.sourceforge.net)</generator> <docs>http://backend.userland.com/rss</docs> … <rdf:RDF> <foaf:Image rdf:about='http://static.flickr.com/132/400582453_e1e1f8602c.jpg'> <dc:title>Zen wisteria</dc:title> <dc:description></dc:description> <foaf:page rdf:resource='http://www.flickr.com/photos/xcv/400582453/'/> <foaf:topic rdf:resource='http://www.flickr.com/photos/tags/vittelgarden/'/> <foaf:topic rdf:resource='http://www.flickr.com/photos/tags/wisteria/'/> <dc:creator> <foaf:Person><foaf:name>Mathieu d'Aquin</foaf:name> … <rdf:RDF> <owl:Ontology rdf:about=&quot;&quot;> <owl:imports rdf:resource=&quot;http://usefulinc.com/ns/doap#&quot;/> </owl:Ontology> <j.1:Organization rdf:ID=&quot;KMi&quot;> <rdfs:comment rdf:datatype=&quot;http://www.w3.org/2001/XMLSchema#string&quot; >The Knoledge Media Institute of the Open University, Milton Keynes UK</rdfs:comment> </j.1:Organization> <j.1:Document rdf:ID=&quot;KMiWebSite&quot;> … DOAP FOAF DC RSS TAP WORDNET NCI Galen Music … … … … … … UoD
    19. 19. Next Generation Semantic Web Applications NG SW Application Semantic Web Smart Features <ul><li>Able to exploit the SW at large </li></ul><ul><ul><li>Dynamically retrieving the relevant semantic resources </li></ul></ul><ul><ul><li>Combining several, heterogeneous Ontologies </li></ul></ul>
    20. 20. Design Principles <ul><li>Focused on quality </li></ul><ul><ul><li>Provides quality information about the collected ontologies and semantic data </li></ul></ul><ul><ul><li>Provides valuable services for semantic applications , to discover, select, exploit and combine semantic resources </li></ul></ul><ul><li>Provides a variety of query and access mechanisms </li></ul><ul><ul><li>For both humans (web interface) and machines (web serv., API) </li></ul></ul><ul><ul><li>To fit applications having different purposes and requirements </li></ul></ul><ul><ul><li>Ranging from Keyword search to ontology exploration and formal queries (SPARQL) </li></ul></ul><ul><li>Support for relations between ontologies </li></ul><ul><ul><li>Detecting redundancy, duplication, incompatibility (contradiction), modularization, versioning, etc. </li></ul></ul>

    ×