29. SELECT ?person ?name WHERE {
?person a dbo:Scientist.
?person rdfs:label ?name.
?person dbo:birthPlace dbp:Denver.
}
AVERAGE
HUMAN
You can use only Wikipedia.
31. AVERAGE
HUMAN
1. visit the page about Denver
2. make a list of people born there
3. read their pages to see if they’re a scientist
You can use only Wikipedia.
33. AVERAGE
HUMAN
1. visit the page about Denver
2. make a list of people born there
3. read their pages to see if they’re a scientist
You can use only Wikipedia.
34. AVERAGE
HUMAN
We need to empower the
but please not with a SPARQL endpoint
because they’re so expensive to keep up.
44. AVERAGE
HUMAN
1. “?people birthPlace Denver.”
2. “?person type Scientist.”
3. “?person fullName ?name.”
You can only use a TPF interface of DBpedia.
46. SELECT ?person ?name WHERE {
?person a dbo:Scientist.
?person rdfs:label ?name.
?person dbo:birthPlace dbp:Denver.
}
AVERAGE
MACHINE
You can only use a TPF interface of DBpedia.
49. If 1 endpoint is down
for 1.5 days each month,
then 2 endpoints might be
for 3 days each month.
Federated queries with
SPARQL endpoints
pose a problem.
50. Just ask each of the questions
to different TPF servers.
Federated queries are
native to TPF clients.
51. But in federated scenarios,
performance can be on par
with SPARQL endpoints!
TPF trades server cost
for query performance.
52. TPF is not the final solution
—no API will ever be—
but an excellent starting point.
Lightweight interfaces
are easy to extend
and combine with others.
