Linked Data for Development Part 3: Hands On Session

Victor de BoerVU University Amsterdam

Recap• Linked Data for Development• From Big data (IATI) to Small data (locally

created)

Downscaling Linked Data:1. usable on small, affordable, hardware

deployed in various connectivity contexts;2. accessible to individuals with varied

cultural backgrounds / literacy levels;3. relevant and directly useful to the target

public they aim to empower.

Infrastructure

Interface Relevancy

Hands on Part 1: Make your dataset Linked Open Data

• What data do you have or would you like to have? – Describe your dataset in terms of content, size, origin, copyright

or privacy issues and how often it is expected to be updated.– Global, local

• Linked Open Data – What datasets could you link your data to (GeoNames,

WorldBank, CIA factbook, Open govt data)– How could you re-use linked datasets in an application or for

(scientific) analysis– How could your data be re-used beyond its original use

http://datahub.io/

Think about three aspects regarding re-use of your data

• Relevancy– List potential stakeholders that can benefit from your Open Data set (end

users, data admins, data journalists, activists, scientists, policy makers…)– For one or more stakeholders: describe a good value proposition for this

data (possibly exploiting links to other datasets)

• Infrastructure– For one or more stakeholders: how does the context restrict data access? – What solutions would be available (low infrastructure, internet

connectivity, etc.)

• Interfaces– For one or more stakeholders/value propositions: what would be an

appropriate interface technology (Web, Mobile phone, SMS, Voice, Radio, …)

Timing

• 15 mins: this introduction• 20 mins: fill out part 1• 20 mins: discuss the results• 20 mins: fill out part 2• 20 mins: discuss the results

Hands-on part 2

• Interface description– Describe an interface for one value proposition and stakeholder

in more detail. – What technology does it use? – What design considerations do you make, based on the context

of the user?

• Interface mockup or sketch– Sketch a mockup of the interface described above. For example,

for a Voice-interface, draw a Call Flow diagram; for a Web application, Icon-based phone interface or Sugar activity, draw one or more screens.

Voice User InterfaceGreeting

Identify caller

Advertisement

Find out team name

Example, sports scores

Provide scores

Does caller want another score?yes

no

goodbye

System User Actions Next

For the Harambee Stars, press 1, for the AFC Leopards, press 2, for Mathare United, press 3, for all other teams press 4

1 Team= “Harambee Stars”

Goto “provide score”

2 Team=“AFC Leopards”

4 Goto “other teams”

5 Throw error, “not a choice”

catch error, play Error message

Hidden choice 6 Transfer to operator

Voice browser Tel: +31208080855 Skype: +990009369996162208

Welcome

Choose application and language

dtmf

About which product (EN)

About which product (NL)

List all products (EN)

dtmf

List product offerings

dtmf

List product offerings

1

2

3

1..n

1..n

Evolution.voxeo.com

Icon-based interaction

Sugar activity

Web interface

Crowdsourcing voice fragment gathering

Part 3: Discussion

• What links could be made between the different datasets

• More re-use• Issues with privacy etc.

Publishing Linked Data

http://wifo5-03.informatik.uni-mannheim.de/bizer/pub/LinkedDataTutorial/

Serving Linked Data from RDF Triple Stores

SesameVirtuosoApache Jena

Fuseki

OWLIM

4Store

ClioPatria

Triple store

HTTP server

SPARQL endpoint Linked Data Interface

Triple Logic

More information?

http://worldwidesemanticweb.org

http://w4ra.org

http://victordeboer.comv.de.boer@vu.nl