One day workshop Linked Data and Semantic Web

Linked Data and Semantic Web Workshop
UNIMAS, Sarawak, Malaysia
1-7-2019
Victor de Boer
With slides from Knud Hinnerk Moeller

Today’s program
Principles of Linked Data
Building Blocks of Linked Data
Handson: graph thinking
Writing triples in Turtle
Handson: Turtle
Triple stores
Handson: Exploring triples
Querying Linked Data
Handson Sparql
I am super-flexible, stop me at any time!

Img:www.doaks.org, www.dkrz.de
The Digital Turn

More and more structured data available online
• Governments
• Social web data
• Medical data
• Museums
• Research data
?
Moverum.com

CC-by-nc-nd https://www.flickr.com/photos/joinash/
Moving away from silos

Acoustic Coupler
Source: “Games Aktuell Blog”,
http://www.gamesaktuell.de/Community/MySite/GenX36019
66-2605282/Blogs/Cyberpunks-beim-Mauerfall-694794/

The Internet (of machines)
Source: Tim Berners-Lee, “Levels of Abstraction”,
http://www.w3.org/DesignIssues/Abstractions.html

The World Wide Web (of Documents)
URIs, HTTP, and HTML

The World Wide Web (of Documents)

The World Wide Web (of Data)
the Semantic Web
Linked Data
the Web of Data

http://info.cern.ch/Proposal.html
Tim Berners-Lee
(The inventor of the Web)
(and the Semantic Web)

The World Wide Web (of Data)
• the Semantic Web
• Linked Data
• the Web of Data

Examples of Linked Data
• Academia, Research
• Community
• Libraries, Museums, Cultural Heritage
• Government and public institutions
(Open Data)
• Media
• Business

...TO CONTEXT: MUTUALLY CONNECTED
COLLECTIONS...
8-7-2019
Connecting collections:
topics, people, genres, etc
Catalogue
Photos
B&GWiki
Programmeguides
Internal: Video hyperlinking

Linked Data
Machine readable format
Standardized
Flexibility to connect heterogeneous data
Link what can be linked
re-use and re-usability
OBJECT EVENT
PLACE
TIME
PERSON
CONCEPT
PROVENANCE

Open Data
is about licenses
to allow reuse
Linked Data
is about
technology for
interoperability
Linked Open Data?
www.w3.org/designissues/linkeddata.html

Web of Documents (WWW)
Linked Documents

How does all this work?
• Structured data not documents
• Graph (networked) data!
• W3C Web standards stack
– URIs, HTTP, RDF, RDFa, RDFS, OWL, SKOS, SPARQL,
etc.

Resource Description Framework
W3C standard
RDF extends the linking structure of the Web to use URIs to name
the relationship between things as well as the two ends of the link
(this is usually referred to as a “triple”). Using this simple model, it
allows structured and semi-structured data to be mixed, exposed,
and shared across different applications.
https://www.w3.org/RDF/

Rules of Linked Data
1. Use HTTP IRI (Internationalized Resource Identifiers)
as names for things
2. When someone looks up a URI, provide useful
information, using the standards (RDF)
3. Include links to other URIs. so that they can discover
more things.
From http://www.w3.org/DesignIssues/LinkedData.html

Use HTTP IRIs for Things
Internationalised Resource Identifier (IRI)
is a string of characters used to identify a
name of a resource
http://rijksmuseum.nl/data/painting001
I can go there (dereference) and then I
get information about it
• HTML page for humans
• RDF data for machines

Semantic Web standard for writing down data, information
(Subject, Relation, Object)
<Painting001, has_location, Amsterdam>
Resource Description Framework (RDF)
Painting001 Amsterdam
has_location

Resource Description Format (RDF)
Triples form Graphs
rijks:Painting001
geo:Haarlem
rijks:Frans_Hals
147590
52.38084, 4.63683
geo:Noord-Holland
geo:Netherlands
rijks:Painting002

BIG DATA
LINKED DATA
OPEN DATA

Four V’s of Big Data
http://www.ey.com/GL/en/Services/Advisory/EY-big-data-big-opportunities-big-challenges

BIG DATA
LINKED DATA
VARIANCE as one of the V’s of
Big Data
VOLUME, VELOCITY are
challenges for LD

LINKED DATA
OPEN DATA
LINKED OPEN DATA
as the way to publish and reuse
datasets across the Web

www.w3.org/designissues/linkeddata.html

OpenPhacts explorer
http://www.openphacts.org/

Google knowledge graph
www.huffingtonpost.com

http://www.bbc.co.uk/music/artists/63aa26c3-d59b-4da4-84ac-716b54f1ef4d

Hands-on Session 1
• Introduce yourselves to each other!
• Draw a social graph of your group
• Represent each member of the group
• Give everyone a name
• You know each other now, so you can connect to
each other in the graph
• Maybe add other data about yourselves:
– Hometown
– University
– Things you like (e.g., music, films, …)

Building Blocks of Linked Data
RDF, Triples,
N-Triples, Turtle,
Reusing Vocabularies

• Technological foundations
– Identifiers: URIs
– Data Model: RDF
– Terminology and Semantics: RDFS, OWL

name
located in
located in
located in
population
population
capital
People’s
Republic of
China
Beijing
SJTU
23,019,148
20,693,000
Shanghai Jiao Tong
University
name
Shanghai
上海
SJTU name "Shanghai Jiao Tong University"
SJTU located in Shanghai
Shanghai name "上海"
Shanghai population "23,019,148"
Shanghai located in People’s Republic of China
People’s Republic of China capital Beijing
Beijing located in People’s Republic of China
Beijing population "20,693,000"
• Graph
• Triple

SJTU located in Shanghai
Shanghai name "上海"
Shanghai population "23,019,148"
Beijing population "20,693,000"
RDF*
*Resource Description Framework
Subject Predicate Object

<sjtu> <located_in> <shanghai> .
<shanghai> <name> "u4E0Au6D77" .
<shanghai> <population> "23019148" .
<beijing> <population> "20693000" .
RDF – N-Triples Syntax
http://www.w3.org/TR/rdf-testcases/#ntriples

RDF – Resources and Literals
Resource Resource Resource
Resource Resource Literal

name
located in
located in
located in
population
population
capital
peoples_
republic_of
_china
beijing
sjtu
23,019,148
20,693,000
Shanghai Jiao Tong
University
name
shanghai
上海

Resources – URIs
URI URI URI
URI URI

Use HTTP-URIs!
• sjtu, name, located_in: valid URIs, but no
scheme, no host, just a path
• any URI valid: ftp://files.nasa.gov, sjtu, urn:isbn:0451450523,
etc.
• but:
– RDF is datamodel for the Web
– Web is based on HTTP
– HTTP-URIs can be resolved, looked up
use HTTP-URIs: http://data.example.org/sjtu

<http://data.example.org/sjtu> <http://voc.example.org/located_in>
<http://data.example.org/shanghai> .
<http://data.example.org/shanghai> <http://voc.example.org/name>
"u4E0Au6D77" .
<http://data.example.org/shanghai> <http://voc.example.org/population>
"23019148" .
<http://data.example.org/beijing> <http://voc.example.org/population>
"20693000" .
Use HTTP-URIs!

Qualifying Literals
<shanghai> <name> "u4E0Au6D77”@zh .
<shanghai> <name> "Shanghai"@en .
<shanghai> <name> "Shang-hai”@ga .
<shanghai> <population>
"23019148"^^<http://www.w3.org/2001/XMLSchema#int> .
<beijing> <population>
"20693000"^^<http://www.w3.org/2001/XMLSchema#int> .
<knud> <birthdate>
"1974-07-06"^^<http://www.w3.org/2001/XMLSchema#date> .
language
datatype

Named Graphs
• divide RDF graph in a
dataset into several
subgraphs
• each subgraph labelled
with a URI
• useful for keeping track of
provenance, timestamps,
versioning, etc.

RDF – Summary
• Graph data model for the Web
• Triples (or “statements”):
– <subject> <predicate> <object>
– (or <thing> <relationship> <thing>)
• Resources
– Things about which we want to make statements
– URIs (ideally HTTP URIs)
• Literals:
– Values like strings, numbers, dates, booleans, …
– Either language tag (zh, en, …) or XML Schema datatype
• Subjects and predicates are always resources
• Objects can be resources or literals
• Named Graphs (not standard): divide graph into subgraphs

RDF – Summary
• N-Triples Syntax:
– most basic RDF syntax; very verbose
– one triple per line
– line terminated with .
– resources (URIs) enclosed in < >
– literals enclosed in " "
– qualify literals with language tag: @zh
– or with datatype:
^^<http://www.w3.org/2001/XMLSchema#int>
http://www.w3.org/TR/rdf-testcases/#ntriples

Turtle Syntax
@prefix data: <http://data.example.org/> .
@prefix vocab: <http://voc.example.org/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
data:shanghai
vocab:located_in data:peoples_republic_of_china ;
vocab:name "Shang-hai"@ga, "Shanghai"@en, "上海"@zh ;
vocab:population "23019148"^^xsd:int .
data:sjtu
vocab:located_in data:shanghai ;
vocab:name "Shanghai Jiao Tong University"@en .
define prefixes
http://www.w3.org/TR/turtle/
abbreviate URIs as CURIEs
group triples with
same subject,predicate
group triples with
same subject
Unicode

CURIEs
• Compact URIs
• replace URI up to last element with prefix
• define prefix in Turtle:
http://www.w3.org/TR/curie/
http://www.w3.org/2001/XMLSchema#date
xsd
xsd:date
“namespace”

Turtle: Group Triples
• use ; to group triples with same subject
data:shanghai vocab:located_in data:peoples_republic_of_china .
data:shanghai vocab:name "Shang-hai"@ga .
data:shanghai vocab:name "Shanghai"@en .
data:shanghai vocab:name "上海"@zh .
data:shanghai vocab:population "23019148"^^xsd:int .
data:shanghai
vocab:located_in data:peoples_republic_of_china ;
vocab:name "Shang-hai"@ga ;
vocab:name "Shanghai"@en ;
vocab:name "上海"@zh ;
vocab:population "23019148"^^xsd:int .

Turtle: Group Triples
• use , to group triples with same
subject,predicate
data:shanghai vocab:name "Shang-hai"@ga .
data:shanghai vocab:name "Shanghai"@en .
data:shanghai vocab:name "上海"@zh .
data:shanghai vocab:name "Shang-hai"@ga, "Shanghai"@en, "上海"@zh .

Turtle - Summary
• human-readable, less verbose syntax
• Turtle is based on N-Triples
(N-Triples ⊆ Turtle)
• Unicode
• shorten URIs with CURIEs
• group triples with common elements

Other Syntaxes
• RDF/XML
– XML-based syntax
– still widely used, but less readable than Turtle
• RDFa
– RDF embedded in HTML, using element attributes
• JSON-LD
– JSON serialisation
• Named Graph Support: Trig (Turtle), Trix
(RDF/XML), N-Quads (N-Triples)

Reuse things: Vocabularies
(Ontologies, Schemata)
• URIs are globally unique, so we can use globally valid
terminology
• necessary for
– data integration
– Inferencing
• Vocabularies define
– properties to use as predicates
– classes to assign types to resources
• just like software libraries, vocabularies are data libraries

Vocabularies: Examples
• RDF and RDFS: basic definitions of objects,
properties, class-relations
• OWL: Description logics
• FOAF (Friend of a Friend): People,
Organisations, Social Networks
• schema.org (Google, Yahoo!, Bing, Yandex):
cross-domain, what search engines are
interested in (people, events, products,
locations)
• Dbpedia (Wikipedia as LOD): cross-domain
• Dublin Core (Bibliographic): publications,
authors, media, etc.
• Good Relations: business, products, etc.
https://lov.linkeddata.es/

FOAF Examples: Some Data
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix people: <http://data.example.org/people/> .
people:knud
a foaf:Person ;
foaf:name "Knud Möller"@de ;
foaf:knows people:victor .
people:victor
a foaf:Person ;
foaf:name "Victor de Boer"@nl ;
foaf:knows people:knud .

FOAF Examples: Classes
foaf:Person
a rdfs:Class, owl:Class ;
rdfs:label "Person" ;
rdfs:comment "A person." ;
owl:disjointWith foaf:Organization, foaf:Project ;
rdfs:subClassOf <http://www.w3.org/2000/10/swap/pim/contact#Person>,
<http://www.w3.org/2003/01/geo/wgs84_pos#SpatialThing>,
foaf:Agent ;
rdfs:isDefinedBy <http://xmlns.com/foaf/0.1/> .

FOAF Examples: Properties
foaf:name
a rdf:Property, owl:DatatypeProperty ;
rdfs:label "name" ;
rdfs:comment "A name for some thing." ;
rdfs:domain owl:Thing ;
rdfs:range rdfs:Literal ;
rdfs:subPropertyOf rdfs:label ;
rdfs:isDefinedBy <http://xmlns.com/foaf/0.1/> .

Some Terms to Define Terms
• rdf:type (or just a in Turtle)
– special property to say what kind of a thing ("class") a
resource is
• rdfs:label, rdfs:comment
– documentation for humans
• rdfs:Class, owl:Class
– this term is a class
• rdfs:Property, owl:DatatypeProperty,
owl:ObjectProperty
– this term is a property, special kind of property

Some Terms to Define Terms
• rdfs:subClassOf
– defining class
hierarchies
• rdfs:subPropertyOf
– defining property
hierarchies
• rdfs:definedBy
– where is this term
defined, where can I get
the specification?

Reuse things: Datasets
• GeoNames: Geographical data
• DBPedia: RDF version of Wikipedia (also in
Dutch)
• GTAA: (Gemeenschappelijke Thesaurus
Audiovisuele Archieven): Persons, topics, AV-
terms
• VIAF: Persons
rijks:Painting001 http: //sws.geonames.org/2759794/
http://purl.org/dc/terms/spatial

Write down your graph from hands on
session 1 in RDF Turtle
@prefix example: <http://purl.org/collections/example/> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
example:knud
a foaf:Person ;
foaf:name “Knud Möller”^^xsd:string ;
foaf:knows example:victor ;
foaf:topic_interest example:linked_data .
example:victor
a foaf:Person ;
foaf:name “Victor de Boer”^^xsd:string ;
foaf:knows example:knud ;
foaf:topic_interest example:linked_data ;
foaf:knows example:truffel .

Rules of Linked Data
1. Use HTTP URIs so that these things can be referred to
and looked up ("dereference") by people and user
agents
2. Provide useful information (i.e., a structured
description - metadata) about the thing when its URI
is dereferenced.
3. Include links to other, related URIs in the exposed
data to improve discovery of other related
information on the Web.
www.w3.org/DesignIssues/LinkedData.html

So that means that
When I ask for a URI
dbpedia:Kuching
I want some data back, describing that resource
Let’s see: http://dbpedia.org/resource/Kuching

Content negotiation
Reply based on preference expressed in HTTP request
response header (Accept:)
GET /resource/Amsterdam HTTP/1.1
Host: dbpedia.org
Accept: text/html;q=0.5, application/rdf+xml
I’m ok with HTML… …but I really prefer RDF

text/html
body onload="init();" about="dbpedia:Amsterdam">
<div id="header">
<div id="hd_l">
<h1 id="title">About: <a href="dbpedia:Amsterdam">Amsterdam</a></h1>
<div id="homelink">

</div>
<div class="page-resource-uri">
An Entity of Type : <a href="http://dbpedia.org/ontology/City">city</a>,
from Named Graph : <a href="http://dbpedia.org">http://dbpedia.org</a>,
within Data Space : <a href="http://dbpedia.org">dbpedia.org</a>
</div>
</div> 
<div id="hd_r">
<a href="http://wiki.dbpedia.org/Imprint" title="About DBpedia">
<img src="/statics/dbpedia_logo.png" height="64" alt="About DBpedia"/>
</a>
</div> 
</div> 
<div id="content">
<p>Amsterdam is de hoofdstad en grootste gemeente van Nederland. De stad, in het Amsterdams ook Mokum genoemd, ligt
in de provincie Noord-Holland, aan de monding van de Amstel en aan het IJ. De naam van de stad komt van de ligging bij een
in de 13e eeuw aangelegde dam in de Amstel. De plaats kreeg stadsrechten rond 1300 en groeide tot één van de grootste
handelssteden ter wereld in de Gouden Eeuw.</p>

application/rdf+xml
<rdf:Description rdf:about="dbpedia:Amsterdam"> <rdf:type
rdf:resource="http://schema.org/City" />
<rdf:type rdf:resource="http://dbpedia.org/ontology/City" />
<rdf:type rdf:resource=
"http://dbpedia.org/class/yago/GeoclassCapitalOfAPoliticalEntity" />
<rdf:type rdf:resource="http://dbpedia.org/ontology/Place" /> <rdf:type
rdf:resource="http://dbpedia.org/class/yago/CitiesInTheNetherlands" />
<rdf:type
rdf:resource="http://dbpedia.org/class/yago/PortCitiesAndTownsInTheNet
herlands" />
"http://dbpedia.org/class/yago/PortCitiesAndTownsOfTheNorthSea" />
"http://umbel.org/umbel/rc/Location_Underspecified" />
<rdf:type rdf:resource="http://dbpedia.org/ontology/Settlement" />
…

application/x-turtle
<dbpedia:Amsterdam> <dbprop:/subdivisionName> "Amsterdam"@en .
<dbprop:/aprSun> "183"^^<http://www.w3.org/2001/XMLSchema#int> .
<http://www.w3.org/2000/01/rdf-schema#comment> "Amsterdam u2013 najwiu0119ksze miasto Holandii i jej
stolica konstytucyjna. Wszystkie instytucje rzu0105dowe …."@pl .
<http://dbpedia.org/ontology/timeZone> <dbpedia:Central_European_Summer_Time> .
<http://xmlns.com/foaf/0.1/name> "Amsterdam"@en .
<http://www.georss.org/georss/point> "52.37305555555555 4.892222222222222"@en .
<dbprop:/yearSun> "1662"^^<http://www.w3.org/2001/XMLSchema#int> .
<http://dbpedia.org/ontology/leaderTitle> "Secretary"@en .
….

Test with CURL
> curl -L -H “Accept: application/rdf+xml” http://dbpedia.org/resource/Kuching
> curl -L -H “Accept: application/x-turtle” http://dbpedia.org/resource/Kuching

Recipes for publishing Linked Data
1. Serving Linked Data as Static RDF/XML Files
2. Serving Linked Data as RDF Embedded in HTML Files
3. Serving RDF and HTML with Custom Server-Side Scripts
4. Serving Linked Data from Relational Databases
5. Serving Linked Data by Wrapping Existing Application or Web APIs
6. Serving Linked Data from RDF Triple Stores w/ deferencing
Tom Heath, Chris Bizer http://linkeddatabook.com/

1. Serving Linked Data as Static RDF/XML Files
• “Just” host a .rdf file on your server, describing
all of your RDF
– Include correct MIME type

2. Serving Linked Data as RDF
Embedded in HTML Files (RDFa)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
version="XHTML+RDFa 1.0" xml:lang="en">
<head>
<title>John's Home Page</title>
<base href="http://example.org/john-d/" />
<meta property="dc:creator" content="Jonathan Doe" />
<link rel="foaf:primaryTopic" href="http://example.org/john-d/#me" />
</head>
<body about="http://example.org/john-d/#me">
<h1>John's Home Page</h1>
<p>My name is <span property="foaf:nick">John D</span> and I like
<a href="http://www.neubauten.org/" rel="foaf:interest"
xml:lang="de">Einstürzende Neubauten</a>.
</p>
</body>
</html>

3. Serving RDF and HTML with Custom
Server-Side Scripts
Data
Scripts serving
RDF
Scripts serving
html web pages
Client request
Content negotiation script
• PHP (ARC)
• Any other server-
side scripting
language

4. Serving Linked Data from Relational Databases
Some software mapping
relational database
tables to triples
D2R, Triplify, Virtuoso
Tom Heath, Chris Bizer http://linkeddatabook.com/
D2R

5. Serving Linked Data by Wrapping Existing
Application or Web APIs

6. Serving Linked Data from RDF Triple Stores
Sesame
Virtuoso
Apache Jena
Fuseki
OWLIM
4Store
ClioPatria
Triple store
HTTP server
SPARQL endpoint
Linked Data
Interface
Triple Logic
Client request
Pubby

Next few slides by Jan Wielemaker

CPACKs
• Amalgame for vocabulary alignment
• XMLRDF for converting XML to RDF
• Prepackaged data and metadata sets
– Provenance, SKOS, etc.
• UI packages
– For specific web applications

More predicates
rdf_load(FileOrURI).
rdf_assert(Subject, Predicate, Object).
rdf_retractall(S,P,O).

Handson: Install Cliopatria
1. Download Swi-prolog (http://swi-prolog.org) -> dev.release
2. Install Swi-prolog
3. Install GIT
4. Install Cliopatria using GIT -> https://cliopatria.swi-
prolog.org/help/Download.html
1. In your target dir: (C:/myStuff) do
2. > git clone https://github.com/ClioPatria/ClioPatria.git
5. Create a project
1. Create a project dir (can be where you want) (C:/myStuff/myTripleStore)
2. For windows, in your Cliopatria dir: run setup.pl
3. Make new project in your new dir (C:/myStuff/myTripleStore)
6. Open your project C:/myStuff/myTripleStore/run.pl
7. direct your browser to http://localhost:3020
1. First time: make an admin passwd

• In the UI, use Resource->Load local file, select
your file and choose a Named Graph URI
(default=filename)
• If no errors, view basic statistics in Places->
Graphs
– Add more graphs if needed
• Alternatively, you can use ‘ load_rdf(“file”). ‘ in
the prolog prompt
Handson: load your files
http://victordeboer.com/foaf.rdf

• Load remote vocabularies using LOD dereferencing (!)
– View your predicates in Places->graphs->predicates
– The blue resources are known (they have triples about
them
– Red resources are unknown resources
– Query the Linked Data Cloud for that resource. Look at the
results in Places-> Graphs
Handson: load remote files

Three main ways of accessing remote
Linked Data
1. Through HTTP request on the resource URI
2. Through SPARQL queries
3. Through Linked Data Fragments
4. Get a copy of a dataset

1. Through HTTP request on the
resource URI
• HTTP GET on resource, parse, follow links
– Simple HTTP requests and RDF parsing
– Requires dereferencable URIs
– One request per resource: may require many
requests
• Local caching can be done
• Crawling GET /resource/Amsterdam HTTP/1.1
Host: dbpedia.org
Accept: text/html;q=0.5, application/rdf+xml
I’m ok with HTML… …but I really prefer RDF

• With CURL
– curl -L -H "Accept: application/rdf+xml"
http://dbpedia.org/resource/Madrid
– curl -L -H "Accept: text/turtle"
http://dbpedia.org/resource/Madrid
– curl -L -H "Accept: text/turtle"
http://purl.org/collections/nl/dss/das/voyage-5580_1
• With Sindice inspector (or other tool)
• http://inspector.sindice.com/inspect?url=
• http://inspector.sindice.com/inspect?url=http://dbpedia.or
g/resource/Madrid

2. Get a local copy of a dataset
• through SPARQL CONSTRUCT,
• crawling or
• direct file download
• Save in triple store
– or convert to something else

RDF Libraries
Redland: http://www.librdf.org/ Perl, Python,
PHP, Ruby, C#, Objective-C
Jena: http://jena.sourceforge.net/ Java
RDFLib: http://www.rdﬂib.net/ Python
ARC2: http://arc2.semsol.net/ PHP
ActiveRDF: http://www.activerdf.org/ Ruby

3. Through SPARQL queries
• Full-blown query language
• Needs SPARQL endpoint
$query =
"SELECT distinct ?title ?description WHERE {
?x <http://data.open.ac.uk/podcast/ontology/relatesToCourse>
<http://data.open.ac.uk/course/t209>.
?x <http://purl.org/dc/terms/title> ?title.
?x <http://www.w3.org/TR/2010/WD-mediaont-10-20100608/description> ?description }
LIMIT 10
";
$requestURL = 'http://data.open.ac.uk/query?query='.urlencode($query);
$response = request($requestURL);
SPARQL in PHP example
http://www.greenhughes.com/content/approach-consuming-linked-data-php

SPARQL
A Query-language for the Web of
Data

SPARQL – Querying the Web of Data
• query language for RDF graphs (i.e., linked
data)
• extract specific information out of a dataset
(or several datasets)
• "The SQL for the Web of Data"

PREFIX mo: <http://purl.org/ontology/mo/>
PREFIX dce: <http://purl.org/dc/elements/1.1/>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
SELECT DISTINCT ?album ?title ?release_date
WHERE {
?album a mo:Record ;
dce:date ?release_date ;
dce:title ?title .
FILTER (year(?release_date) = 2007 &&
month(?release_date) = 7)
}
ORDER BY ?release_date

PREFIX mo: <http://purl.org/ontology/mo/>
PREFIX dce: <http://purl.org/dc/elements/1.1/>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
SELECT DISTINCT ?album ?title ?release_date
WHERE {
dce:title ?title .
FILTER (year(?release_date) = 2007 &&
}
ORDER BY ?release_date
graph pattern

<artist/3908> a mo:MusicArtist .
<artist/3908> foaf:based_near <http://sws.geonames.org/3019599/> .
<artist/3908> foaf:homepage <http://www.petithomme.org> .
<artist/3908> foaf:img <http://img.jamendo.com/artists/p/petit.homme.gif> .
<artist/3908> foaf:made <record/3604> .
<artist/3908> foaf:name "Petit Homme"^^xsd:string .
<artist/3732> a mo:MusicArtist .
<artist/3732> foaf:based_near <http://sws.geonames.org/3019599/> .
<artist/3732> foaf:homepage <http://blackshoulders.hautetfort.com/> .
<artist/3732> foaf:img <http://img.jamendo.com/artists/w/white-shoulders.jpg> .
<artist/3732> foaf:name "Whiteshoulders"^^xsd:string .
<record/8836> dce:date "2007-10-09T15:58:17"^^xsd:dateTime .
<record/8836> dce:title "W (EP)"^^xsd:string .
<record/8836> mo:track <track/90496> .
<record/8836> hg:taggedWithTag tags:electro .
<record/8836> hg:taggedWithTag tags:experimental .
<record/8836> hg:taggedWithTag tags:noise .
<record/8836> hg:taggedWithTag tags:noisy .
<record/8836> a mo:Record .
<record/8836> foaf:maker <artist/3732> .

Triple and Graph Patterns
WHERE {
dce:title ?title .
FILTER (year(?release_date) = 2007
&&
}

One Variable
<artist/3732> foaf:made ?record .

Two Variables
?artist foaf:made ?record .

Three Variables
?subject ?predicate ?object .

A full Graph Pattern
?artist a mo:MusicArtist ;
foaf:name ?artist_name ;
foaf:homepage ?homepage .

ACCESS IT AT
HTTP://DUTCHSHIPSANDSAILORS.NL/DATA
OR
HTTP://SEMANTICWEB.CS.VU.NL/DSS
SELECT * WHERE {
?record dss:hasOriginalScan ?scan.
?record dss:has_kb_link ?kblink.
?record mdb:schip ?schip.
?schip mdb:scheepstype ?shiptype.
?shiptype skos:exactMatch ?em.
?em skos:broader* aat:kustvaarders.
}

http://www.victordeboer.com/dss_sparql_handson/
OR do sparql on your own triple store!!
In UI -> Query -> Simple form

One day workshop Linked Data and Semantic Web

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to One day workshop Linked Data and Semantic Web

Similar to One day workshop Linked Data and Semantic Web (20)

More from Victor de Boer

More from Victor de Boer (20)

Recently uploaded

Recently uploaded (20)

One day workshop Linked Data and Semantic Web