The document describes DBpedia Viewer, an interface for exploring DBpedia data. It leverages DBpedia services and tools to provide an intuitive interface that reduces information overload. The viewer uses AngularJS for dynamic rendering of entities from Virtuoso. It features entity summaries, search, language filtering, mapping integration, and "triple actions" that enable custom interactions and functionality based on entity properties.

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

5. DBpedia Services - Spotlight

6. DBpedia Services - Lookup

7. LD Tools - RelFinder

8. DBpedia tools - Mappings wiki

9. LD Tools - LODLive

10. LD Tools - Virtuoso fct pluin

11. DBpedia Viewer
● Intuitive & interactive
● Integrative (tools)
○ Triple Action Framework
● Client-based rendering
○ No-JS support (defaults to old interface)
● Reduces information overload on previous
DBpedia UI

12. DBpedia Viewer - Technology
● Data: Virtuoso Triplestore
○ Exposes SPARQL endpoint
● Server: VSP
○ Client bootstrapping
○ Non-Javascript visitors (old UI)
● Client: AngularJS
○ Dynamic UI
○ Direct use of SPARQL endpoint (from JS)

13. DBpedia Viewer - Features
1. Pretty box: short entity summary
2. Search bar: search entities (lookup)
3. Language filtering: primary & fallback
4. Triple filtering : just helpful
5. Shortcuts: just helpful too
6. Previews: preview other resource
7. Maps: shows entity on map
8. Triple Actions: actions bound to triples

14. DBpediaViewer-Features

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

22. ASK
{ :Audience :hasQuestion ?q }
Sponsored by GSoC 2013https://github.com/dbpedia/dbpedia-vad-i18n