12. Linked Data
... about using the Web to connect related data
that wasn't previously linked...
13. Linked Data
... about using the Web to connect related data
that wasn't previously linked...
... Linked Data as "a term used to describe a
recommended best practice for exposing, sharing, and
connecting pieces of data, information, and knowledge...
... on the Semantic Web
14. Linked Data
... about using the Web to connect related data
that wasn't previously linked...
... Linked Data as "a term used to describe a
recommended best practice for exposing, sharing, and
connecting pieces of data, information, and knowledge...
... on the Semantic Web
recommended best practice
25. Identifying things
1969-059A
spacecraft/1969-059A
nasa.dataincubator.org/spacecraft/1969-059A
26. Identifying things
with URIs
1969-059A
spacecraft/1969-059A
nasa.dataincubator.org/spacecraft/1969-059A
http://nasa.dataincubator.org/spacecraft/1969-059A
34. 28801.0
mass .../spacecraft/
http://nasa.dataincubator.org/spacecraft/1969-059A
1969-059A
35. Apollo 11 CSM
28801.0
name
mass .../spacecraft/
http://nasa.dataincubator.org/spacecraft/1969-059A
1969-059A
36. Apollo 11 CSM Columbia
name
28801.0 name
mass .../spacecraft/
http://nasa.dataincubator.org/spacecraft/1969-059A
1969-059A
37. Apollo 11 CSM Columbia
name
28801.0 name
mass .../spacecraft/
http://nasa.dataincubator.org/spacecraft/1969-059A
1969-059A
launch
../launch/1969-059
38. Apollo 11 CSM Columbia
name
28801.0 name
mass .../spacecraft/ 16 July 1969
http://nasa.dataincubator.org/spacecraft/1969-059A
1969-059A
launch
date
../launch/1969-059
39. Apollo 11 CSM Columbia
name
28801.0 name
mass .../spacecraft/ 16 July 1969
http://nasa.dataincubator.org/spacecraft/1969-059A
1969-059A
launch
date
../launch/1969-059
site
../cape
canaveral
40. Apollo 11 CSM Columbia
name
28801.0 name
mass .../spacecraft/ 16 July 1969
http://nasa.dataincubator.org/spacecraft/1969-059A
1969-059A
launch
date
../launch/1969-059
site
../cape
canaveral lat
N 28° 27' 31''
41. Apollo 11 CSM Columbia
name
28801.0 name
mass .../spacecraft/ 16 July 1969
http://nasa.dataincubator.org/spacecraft/1969-059A
1969-059A
launch
date
../launch/1969-059
site
../cape
canaveral lat
N 28° 27' 31''
long
W 80° 31' 59''
42. Apollo 11 CSM Columbia
name
28801.0 name
mass .../spacecraft/ 16 July 1969
http://nasa.dataincubator.org/spacecraft/1969-059A
1969-059A
launch
date
../launch/1969-059
<../1969-059A> mass 28801.0 . site
<../1969-059A> name “Apollo 11 CSM” .
<../1969-059A> name “Columbia” .
../cape
<../1969-059A> launch <../launch/1969-059> . canaveral lat
<../launch/1969-059> date 1969-07-16 .
<../launch/1969-059> site <..site/capecanaveral> . N 28° 27' 31''
long
<..site/capecanaveral> lat “N 28° 27' 31''” .
<..site/capecanaveral> long “W 80° 31' 59''” . W 80° 31' 59''
43. RDF
Apollo 11 CSM Columbia
name
28801.0 name
mass .../spacecraft/ 16 July 1969
http://nasa.dataincubator.org/spacecraft/1969-059A
1969-059A
launch
date
../launch/1969-059
<../1969-059A> mass 28801.0 . site
<../1969-059A> name “Apollo 11 CSM” .
<../1969-059A> name “Columbia” .
../cape
<../1969-059A> launch <../launch/1969-059> . canaveral lat
<../launch/1969-059> date 1969-07-16 .
<../launch/1969-059> site <..site/capecanaveral> . N 28° 27' 31''
long
<..site/capecanaveral> lat “N 28° 27' 31''” .
<..site/capecanaveral> long “W 80° 31' 59''” . W 80° 31' 59''
60. Linked Data Principles
1. Use URIs as names for things
2. Use HTTP URIs so people can look up those
names
61. Linked Data Principles
1. Use URIs as names for things
2. Use HTTP URIs so people can look up those
names
3. When someone looks up a URI, provide useful
information, using the standards RDF, SPARQL
62. Linked Data Principles
1. Use URIs as names for things
2. Use HTTP URIs so people can look up those
names
3. When someone looks up a URI, provide useful
information, using the standards RDF, SPARQL
4. Include links to other URIs, so that they can
discover more
Tim Berners-Lee - 2006
65. Linked Data Principles
1. Identify your things with URIs
2. When someone looks up your identifier give
them information in a [Web] standard form
66. Linked Data Principles
1. Identify your things with URIs
2. When someone looks up your identifier give
them information in a [Web] standard form
3. Include links to other things (URIs), so that they
can discover more
67. Linked Data Principles
1. Identify your things with URIs
2. When someone looks up your identifier give
them information in a [Web] standard form
3. Include links to other things (URIs), so that they
can discover more
4. Enable follow-your-nose discovery/navigation
RJW - 2011
83. lo ✗
ts 80% of data contains location!
http://mydomain.com/location/London
84. lo ✗
ts 80% of data contains location!
http://mydomain.com/location/London
sameAs
85. lo ✗
ts 80% of data contains location!
http://mydomain.com/location/London sameAs
http://dbpedia.org/resource/London
86. lo ✗
ts 80% of data contains location!
http://mydomain.com/location/London sameAs http://dbpedia.org/resource/London
87. lo ✗
ts 80% of data contains location!
http://mydomain.com/location/London sameAs http://dbpedia.org/resource/London
http://dbpedia.org/resource/London
88. lo ✗
ts 80% of data contains location!
http://mydomain.com/location/London sameAs http://dbpedia.org/resource/London
http://dbpedia.org/resource/London
sameAs
89. lo ✗
ts 80% of data contains location!
http://mydomain.com/location/London sameAs http://dbpedia.org/resource/London
http://dbpedia.org/resource/London sameAs
http://sws.geonames.org/2643743/
90. lo ✗
ts 80% of data contains location!
http://mydomain.com/location/London sameAs http://dbpedia.org/resource/London
http://dbpedia.org/resource/London sameAs http://sws.geonames.org/2643743/
91. lo ✗
ts 80% of data contains location!
http://mydomain.com/location/London sameAs http://dbpedia.org/resource/London
http://dbpedia.org/resource/London sameAs http://sws.geonames.org/2643743/
Sales
Location: London
98. Data Open and/or Linked
1. Data can be open, while not being linked
99. Data Open and/or Linked
1. Data can be open, while not being linked
2. Data can be linked, while not being open
100. Data Open and/or Linked
1. Data can be open, while not being linked
2. Data can be linked, while not being open
3. Data which is both open and linked is
increasingly viable
101. Data Open and/or Linked
1. Data can be open, while not being linked
2. Data can be linked, while not being open
3. Data which is both open and linked is
increasingly viable
4. The Semantic Web can only function with data
which is both open and linked
Paul Walk - UKLON
102. Putting the theory in to practice
http://www.flickr.com/photos/stuartpilbrow/3449993951
103. Putting the theory in to practice
What do I need to know?
http://www.flickr.com/photos/stuartpilbrow/3449993951
104. Putting the theory in to practice
What do I need to know?
What skills are needed?
http://www.flickr.com/photos/stuartpilbrow/3449993951
106. Linked Data
What do I need to know?
• Globally distributed / adopted
107. Linked Data
What do I need to know?
• Globally distributed / adopted
• Still evolving
108. Linked Data
What do I need to know?
• Globally distributed / adopted
• Still evolving
• Built on Web standards
109. Linked Data
What do I need to know?
• Globally distributed / adopted
• Still evolving
• Built on Web standards
• Recommended best practice
110. Linked Data
What do I need to know?
• Globally distributed / adopted
• Still evolving
• Built on Web standards
• Recommended best practice
• Low barrier to data
111. Linked Data
What do I need to know?
• Globally distributed / adopted
• Still evolving
• Built on Web standards
• Recommended best practice
• Low barrier to [other people’s] data
112. Linked Data
What do I need to know?
• Globally distributed / adopted
• Still evolving
• Built on Web standards
• Recommended best practice
• Low barrier to [other people’s] data
• Integration without ‘need’ for coordination
113. Linked Data
What do I need to know?
• Globally distributed / adopted
• Still evolving
• Built on Web standards
• Recommended best practice
• Low barrier to [other people’s] data
• Integration without ‘need’ for coordination
• Follow-your-nose discovery/navigation
116. Linked Data
What skills are needed?
• Domain experience/understanding
117. Linked Data
What skills are needed?
• Domain experience/understanding
• Appreciation of Linked Data principles
118. Linked Data
What skills are needed?
• Domain experience/understanding
• Appreciation of Linked Data principles
• Guidance from experience
119. Linked Data
What skills are needed?
• Domain experience/understanding
• Appreciation of Linked Data principles
• Guidance from experience
• Open world thinking
120. Linked Data
What skills are needed?
• Domain experience/understanding
• Appreciation of Linked Data principles
• Guidance from experience
• Open world thinking
• Not constrained by siloed thinking
121. Linked Data
What skills are needed?
• Domain experience/understanding
• Appreciation of Linked Data principles
• Guidance from experience
• Open world thinking
• Not constrained by siloed thinking
• Not difficult, but different
http://www.flickr.com/photos/katclay/3778830795
125. Lin
ked
Da
ta Hyped? – of course
Potential to deliver better use of data
126. Lin
ked
Da
ta Hyped? – of course
Potential to deliver better use of data – yes
127. Lin
ked
Da
ta Hyped? – of course
Potential to deliver better use of data – yes
Potential to deliver wider use of data
128. Lin
ked
Da
ta Hyped? – of course
Potential to deliver better use of data – yes
Potential to deliver wider use of data – yes
129. Lin
ked
Da
ta Hyped? – of course
Potential to deliver better use of data – yes
Potential to deliver wider use of data – yes
Successful examples
130. Lin
ked
Da
ta Hyped? – of course
Potential to deliver better use of data – yes
Potential to deliver wider use of data – yes
Successful examples – many
131. Lin
ked
Da
ta Hyped? – of course
Potential to deliver better use of data – yes
Potential to deliver wider use of data – yes
Successful examples – many
ROI
132. Lin
ked
Da
ta Hyped? – of course
Potential to deliver better use of data – yes
Potential to deliver wider use of data – yes
Successful examples – many
ROI – yes
133. Lin
ked
Da
ta Hyped? – of course
Potential to deliver better use of data – yes
Potential to deliver wider use of data – yes
Successful examples – many
ROI – yes
New business model opportunities
134. Lin
ked
Da
ta Hyped? – of course
Potential to deliver better use of data – yes
Potential to deliver wider use of data – yes
Successful examples – many
ROI – yes
New business model opportunities – yes
135. Lin
ked
Da
ta Hyped? – of course
Potential to deliver better use of data – yes
Potential to deliver wider use of data – yes
Successful examples – many
ROI – yes
New business model opportunities – yes
Enterprise application
136. Lin
ked
Da
ta Hyped? – of course
Potential to deliver better use of data – yes
Potential to deliver wider use of data – yes
Successful examples – many
ROI – yes
New business model opportunities – yes
Enterprise application – yes
137. Lin
ked
Da
ta Hyped? – of course
Potential to deliver better use of data – yes
Potential to deliver wider use of data – yes
Successful examples – many
ROI – yes
New business model opportunities – yes
Enterprise application – yes
Difficult
138. Lin
ked
Da
ta Hyped? – of course
Potential to deliver better use of data – yes
Potential to deliver wider use of data – yes
Successful examples – many
ROI – yes
New business model opportunities – yes
Enterprise application – yes
Difficult – no
139. Lin
ked
Da
ta Hyped? – of course
Potential to deliver better use of data – yes
Potential to deliver wider use of data – yes
Successful examples – many
ROI – yes
New business model opportunities – yes
Enterprise application – yes
Difficult – no
Will I need help
140. Lin
ked
Da
ta Hyped? – of course
Potential to deliver better use of data – yes
Potential to deliver wider use of data – yes
Successful examples – many
ROI – yes
New business model opportunities – yes
Enterprise application – yes
Difficult – no
Will I need help – initially
141. Linked Data
What is just flannel
What skill sets are required?
Richard Wallis
@rjw
Notes de l'éditeur
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
build up the URI from an identifier and make it [globally] unique\nApollo 11?\n
build up the URI from an identifier and make it [globally] unique\nApollo 11?\n
build up the URI from an identifier and make it [globally] unique\nApollo 11?\n
build up the URI from an identifier and make it [globally] unique\nApollo 11?\n
build up the URI from an identifier and make it [globally] unique\nApollo 11?\n
build up the URI from an identifier and make it [globally] unique\nApollo 11?\n