SensoDat: Simulation-based Sensor Dataset of Self-driving Cars
DBpedia Viewer - LDOW 2014
1. DBpedia Viewer
An Integrative Interface for DBpedia
Leveraging the DBpedia Service Eco
System
#LDOW14 #WWW2014
#GSoC2013
Lukovnikov D., Kontokostas D., Stadler C., Hellmann S., Lehmann J.
2. Linked Data
● Perfect for machines
● Not so good for humans
○ Fine granularity (RDF triples)
○ Need to ingest triples
○ What is behind a resource URI?
● Imagine landing on a Pubby page
3. Linked Data @ DBpedia
● DBpedia extracts knowledge from Wikipedia
and publishes it as RDF
● 191 languages in v3.9 (08/13), 15 language
chapters & ~4M entities in English
● Various access points
○ RDF dumps, SPARQL endpoint & Linked Data
● Pubby-Like LD interface as a Virtuoso plugin
15. Triple Actions
● Defined by UI maintainer
⇒ easy means to extend UI
○ boilerplate already implemented
● Initially for:
○ user actions → interaction
● Proved useful for:
○ system actions → customization
16. Triple Actions - Main Semantics
● Bind: whether action applicable
○ based on values in triple and action state
● Execute: what to do when invoked
○ go to URL
○ query external resource / service
● State:
○ global: across all action instances
○ local: at one action instance only
17. Triple Actions - Extras
Additional hooks and features:
● Icon display:
○ may depend on state
● Title (ID) & description
● Legend entry
18. DBpedia Viewer - User Actions
● Text Annotation: Spotlight on long texts
● RelFinder: relationship finder tool
● LodLive & Virtuoso fct: alternative browsers
● Wikipedia: view source page
● Mappings Wiki: view mappings wiki page
⇒ may use any of the (subject, predicate, object) from a
triple
19. DBpedia Viewer - System actions
● Invisible to users
● Populate UI elements based on data
○ owl:sameAs → filter → pretty box
○ geocoordinates → show in map
● Implement data-triggered functionality
○ :wikiPageRedirects ⇒ redirect page
20. Conclusion
● Interactive additions and layout choices may
improve comprehensibility of data
○ While keeping the Linked Data philosophy
● JS with SPARQL via AJAX
○ Page construction in client → less server-side load
● Triple Actions
○ Easy customization (system actions)
○ More interaction (user actions)
21. Possible future
● Generalization for all datasets (LD Viewer)
● New actions
○ Push triple to Wikidata
○ Triple validation
● User behavior analysis for
○ Entity summarization
○ Entity ranking