Finding knowledge, data and answers on the Semantic Web

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    5 Favorites

    Finding knowledge, data and answers on the Semantic Web - Presentation Transcript

    1. Finding knowledge, data and answers on the Semantic Web Tim Finin University of Maryland, Baltimore County http://ebiquity.umbc.edu/resource/html/id/202/ Joint work with Li Ding, Anupam Joshi, Yun Peng, Cynthia Parr, Pranam Kolari, Pavan Reddivari, Sandor Dornbush, Rong Pan, Akshay Java, Joel Sachs, Scott Cost and Vishal Doshi  http://creativecommons.org/licenses/by-nc-sa/2.0/ This work was partially supported by DARPA contract F30602-97-1-0215, NSF grants CCR007080 and IIS9875433 and grants from IBM, Fujitsu and HP.
    2. This talk
      • Motivation
      • Swoogle Semantic Web search engine
      • Use cases and applications
      • Observations
      • Conclusions
    3. Google has made us smarter
    4. But what about our agents?
      • Agents still have a very minimal understanding of text and images.
      tell register
    5. But what about our agents?
      • A Google for knowledge on the Semantic Web is needed by software agents and programs
      Swoogle Swoogle Swoogle Swoogle Swoogle Swoogle Swoogle Swoogle Swoogle Swoogle Swoogle Swoogle Swoogle Swoogle Swoogle tell register
    6. This talk
      • Motivation
      • Swoogle Semantic Web search engine
      • Use cases and applications
      • Observations
      • Conclusions
      • http://swoogle.umbc.edu/
      • Running since summer 2004
      • 1.8M RDF docs, 320M triples, 10K ontologies, 15K namespaces, 1.3M classes, 175K properties, 43M instances, 600 registered users
    7. Swoogle Architecture Analysis Index Discovery IR Indexer Search Services Semantic Web metadata Web Service Web Server Candidate URLs Bounded Web Crawler Google Crawler SwoogleBot SWD Indexer Ranking document cache SWD classifier human machine html rdf/xml … the Web Semantic Web Information flow Swoogle‘s web interface Legends
    8. A Hybrid Harvesting Framework Manual submission RDF crawling Bounded HTML crawling Meta crawling Seeds M Seeds H Seeds R Swoogle Sample Dataset Inductive learner the Web Google API call crawl crawl true would google
    9. Performance – Site Coverage
      • SW06MAR - Basic statistics (Mar 31, 2006)
        • 1.3M SWDs from 157K websites
        • 268M triples
        • 61K SWOs including >10K in high quality
        • 1.4M SWTs using 12K namespaces
      • Significance
        • Compare with existing works ( DAML crawler, scutter )
        • Compare SW06MAR with Google’s estimated SWDs
      SWDs per website Website
    10. Performance – crawlers’ contribution
      • High SWD ratio: 42% URLs are confirmed as SWD
      • Consistent growth rate: 3000 SWDs per day
      • RDF crawler: best harvesting method
      • HTML crawler: best accuracy
      • Meta crawler: best in detecting websites
      # of documents
    11. This talk
      • Motivation
      • Swoogle Semantic Web search engine
      • Use cases and applications
      • Observations
      • Conclusions
    12. Applications and use cases
      • Supporting Semantic Web developers
        • Ontology designers, vocabulary discovery, who’s using my ontologies or data?, use analysis, errors, statistics, etc.
      • Searching specialized collections
        • Spire: aggregating observations and data from biologists
        • InferenceWeb: searching over and enhancing proofs
        • SemNews: Text Meaning of news stories
      • Supporting SW tools
        • Triple shop: finding data for SPARQL queries
      1 2 3
    13. 1
    14. By default, ontologies are ordered by their ‘popularity’, but they can also be ordered by recency or size. 80 ontologies were found that had these three terms Let’s look at this one
    15. Basic Metadata hasDateDiscovered :  2005-01-17 hasDatePing :  2006-03-21 hasPingState :  PingModified type :  SemanticWebDocument isEmbedded :  false hasGrammar :  RDFXML hasParseState :  ParseSuccess hasDateLastmodified :  2005-04-29 hasDateCache :  2006-03-21 hasEncoding :  ISO-8859-1 hasLength :  18K hasCntTriple :  311.00 hasOntoRatio :  0.98 hasCntSwt :  94.00 hasCntSwtDef :  72.00 hasCntInstance :  8.00
    16.  
    17. rdfs:range was used 41 times to assert a value. owl:ObjectProperty was instantiated 28 times time:Cal… defined once and used 24 times (e.g., as range)
    18. These are the namespaces this ontology uses. Clicking on one shows all of the documents using the namespace. All of this is available in RDF form for the agents among us.
    19. Here’s what the agent sees. Note the swoogle and wob (web of belief) ontologies.
    20. We can also search for terms (classes, properties) like terms for “person”.
    21. 10K terms associated with “person”! Ordered by use. Let’s look at foaf:Person’s metadata
    22.  
    23.  
    24.  
    25. 87K documents used foaf:gender with a foaf:Person instance as the subject
    26. 3K documents used dc:creator with a foaf:Person instance as the object
    27. Swoogle’s archive saves every version of a SWD it’s seen.
    28.  
    29. 2
      • An NSF ITR collaborative project with
      • University of Maryland, Baltimore County
      • University of Maryland, College Park
      • U. Of California, Davis
      • Rocky Mountain Biological Laboratory
    30. An invasive species scenario
      • Nile Tilapia fish have been found in a California lake.
      • Can this invasive species thrive in this environment?
      • If so, what will be the likely consequences for the ecology?
      • So…we need to understand the effects of introducing this fish into the food web of a typical California lake
    31. Food Webs
      • A food web models the trophic (feeding) relationships between organisms in an ecology
        • Food web simulators are used to explore the consequences of changes in the ecology, such as the introduction or removal of a species
        • A locations food web is usually constructed from studies of the frequencies of the species found there and the known trophic relations among them.
      • Goal: automatically construct a food web for a new location using existing data and knowledge
      • ELVIS: Ecosystem Location Visualization and Information System
    32. East River Valley Trophic Web http://www.foodwebs.org/
    33. Species List Constructor
      • Click a county, get a species list
    34. The problem
      • We have data on what species are known to be in the location and can further restrict and fill in with other ecological models
      • But we don’t know which of these the Nile Tilapia eats of who might eat it.
      • We can reason from taxonomic data (simlar species) and known natural history data (size, mass, habitat, etc.) to fill in the gaps.
    35.  
    36. Food Web Constructor
      • Predict food web links using database and taxonomic reasoning.
      In an new estuary, Nile Tilapia could compete with ostracods (green) to eat algae. Predators (red) and prey (blue) of ostracods may be affected
    37. Evidence Provider
      • Examine evidence for predicted links.
    38. Status
      • Goal is ELVIS (Ecosystem Location Visualization and Information System) as an integrated set of web services for constructing food webs for a given location.
      • Background ontologies
        • SpireEcoConcepts: concepts and properties to represent food webs, and ELVIS related tasks, inputs and outputs
        • ETHAN (Evolutionary Trees and Natural History) Concepts and properties for ‘natural history’ information on species derived from data in the Animal diversity web and other taxonomic sources
      • Under development
        • Connect to visualization software
        • Connect to triple shop to discover more data
    39. UMBC Triple Shop
      • http://sparql.cs.umbc.edu/
      • Online SPARQL RDF query processing with several interesting features
      • Automatically finds SWDs for give queries using Swoogle backend database
      • Datasets, queries and results can be saved, tagged, annotated, shared, searched for, etc.
      • RDF datasets as first class objects
        • Can be stored on our server or downloaded
        • Can be materialized in a database or (soon) as a Jena model
      3
    40. Web-scale semantic web data access agent data access service the Web ask (“person”) Search vocabulary ask (“?x rdf:type foaf:Person”) inform (“foaf:Person”) Fetch docs Populate RDF database Query local RDF database inform (doc URLs) Search URIrefs in SW vocabulary Search URLs in SWD index Compose query Index RDF data
    41. Who knows Anupam Joshi? Show me their names, email address and pictures
    42. The UMBC ebiquity site publishes lots of RDF data, including FOAF profiles
    43. PREFIX foaf: <http://xmlns.com/foaf/0.1/> SELECT DISTINCT ?p2name ?p2mbox ?p2pix FROM ??? WHERE { ?p1 foaf:surname &quot;Joshi&quot; . ?p1 foaf:firstName “Anupam&quot; . ?p1 foaf:mbox ?p1mbox . ?p2 foaf:knows ?p3 . ?p3 foaf:mbox ?p1mbox . ?p2 foaf:name ?p2name . ?p2 foaf:mbox ?p2mbox . OPTIONAL { ?p2 foaf:depiction ?p2pix } . } ORDER BY ?p2name No FROM clause!
    44. Enter query w/o FROM clause! log in specify dataset
    45.  
    46.  
    47. 302 RDF documents were found that might have useful data.
    48. We’ll select them all and add them to the current dataset.
    49. We’ll run the query against this dataset to see if the results are as expected.
    50. The results can be produced in any of several formats
    51.  
    52. Looks like a useful dataset. Let’s save it and also materialize it the TS triple store.
    53.  
    54. We can also annotate, save and share queries.
    55. Work in Progress
      • There are a host of performance issues
      • We plan on supporting some special datasets, e.g.,
        • FOAF data collected from Swoogle
        • Definitions of RDF and OWL classes and properties from all ontologies that Swoogle has discovered
      • Expanding constraints to select candidate SWDs to include arbitrary metadata and embedded queries
        • FROM “documents trusted by a member of the SPIRE project”
      • We will explore two models for making this useful
        • As a downloadable application for client machines
        • As an (open source?) downloadable service for servers supporting a community of users.
    56. This talk
      • Motivation
      • Swoogle Semantic Web search engine
      • Use cases and applications
      • Observations
      • Conclusions
    57. Will Swoogle Scale? How?
      • Here’s a rough estimate of the data in RDF documents on the semantic web based on Swoogle’s crawling
      We think Swoogle’s centralized approach can be made to work for the next few years if not longer. 5x10 13 5x10 11 5x10 9 5x10 9 5x10 6 2008 5x10 11 5x10 9 5x10 7 5x10 7 1x10 6 2006 1x10 10 7.5x10 7 1.5x10 7 7x10 5 2x10 5 Swoogle3 7x10 9 5x10 7 7x10 6 3.5x10 5 1.5x10 5 Swoogle2 Bytes Triples Individuals Documents Terms System/date
    58. How much reasoning should Swoogle do?
      • SwoogleN (N<=3) does limited reasoning
        • It’s expensive
        • It’s not clear how much should be done
      • More reasoning would benefit many use cases
        • e.g., type hierarchy
      • Recognizing specialized metadata
        • E.g., that ontology A some maps terms from B to C
    59. A RDF Dictionary
      • We hope to develop an RDF dictionary.
      • Given an RDF term, returns a graph of its definiton
        • Term  definition from “official” ontology
        • Term+URL  definition from SWD at URL
        • Term+*  union definition
        • Optional argument recursively adds definitions of terms in definition excluding RDFS and OWL terms
        • Optional arguments identifies more namespaces to exclude
    60. This talk
      • Motivation
      • Swoogle Semantic Web search engine
      • Use cases and applications
      • Observations
      • Conclusions
    61. Conclusion
      • The web will contain the world’s knowledge in forms accessible to people and computers
        • We need better ways to discover, index, search and reason over SW knowledge
      • SW search engines address different tasks than html search engines
        • So they require different techniques and APIs
      • Swoogle like systems can help create consensus ontologies and foster best practices
        • Swoogle is for Semantic Web 1.0
        • Semantic Web 2.0 will make different demands
        • http://ebiquity.umbc.edu/
      Annotated in OWL For more information

    + ebiquityebiquity, 4 years ago

    custom

    2387 views, 5 favs, 1 embeds more stats

    Web search engines like Google have made us all sma more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 2387
      • 2386 on SlideShare
      • 1 from embeds
    • Comments 0
    • Favorites 5
    • Downloads 0
    Most viewed embeds
    • 1 views on http://ebiquity.umbc.edu

    more

    All embeds
    • 1 views on http://ebiquity.umbc.edu

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories