Linked Data: What is just flannel - what skills are required

736 views
683 views

Published on

Presentation to the BCS & UK Location Group. London 24th November 2011

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
736
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • \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
  • Literal attributes - name, mass, creation date\nother thing attributes - web page, launch vehicle, launch site\n
  • Literal attributes - name, mass, creation date\nother thing attributes - web page, launch vehicle, launch site\n
  • Literal attributes - name, mass, creation date\nother thing attributes - web page, launch vehicle, launch site\n
  • Literal attributes - name, mass, creation date\nother thing attributes - web page, launch vehicle, launch site\n
  • Literal attributes - name, mass, creation date\nother thing attributes - web page, launch vehicle, launch site\n
  • Literal attributes - name, mass, creation date\nother thing attributes - web page, launch vehicle, launch site\n
  • Literal attributes - name, mass, creation date\nother thing attributes - web page, launch vehicle, launch site\n
  • Literal attributes - name, mass, creation date\nother thing attributes - web page, launch vehicle, launch site\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
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • thing - prop - thing\n - prop - thing\n - prop - name\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\n
  • Data to feed those student Apps\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
  • \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
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Linked Data: What is just flannel - what skills are required

    1. 1. Linked Data What is just flannelWhat skill sets are required? Richard Wallis @rjw
    2. 2. Leading Semantic Web Technology
    3. 3. 40 Year Rich Metadata HeritageLeading Semantic Web Technology
    4. 4. Shared Innovation Ethos 40 Year Rich Metadata HeritageLeading Semantic Web Technology
    5. 5. kasabi.com
    6. 6. Lin ked Da taA Silver Bullet?
    7. 7. Linked Data
    8. 8. Linked Data... about using the Web to connect related datathat wasnt previously linked...
    9. 9. Linked Data... about using the Web to connect related datathat wasnt previously linked...... Linked Data as "a term used to describe arecommended best practice for exposing, sharing, andconnecting pieces of data, information, and knowledge...... on the Semantic Web
    10. 10. Linked Data... about using the Web to connect related datathat wasnt previously linked...... Linked Data as "a term used to describe arecommended best practice for exposing, sharing, andconnecting pieces of data, information, and knowledge...... on the Semantic Web recommended best practice
    11. 11. Semantic Web
    12. 12. Semantic Web
    13. 13. Semantic WebA i e s s p r a d a b o t G Flying Cars Technology
    14. 14. Linked Data
    15. 15. Linked DataBuilt on Semantic Web Standards
    16. 16. Linked Data Built on Semantic Web StandardsAll about identifying and linking things Thi ng
    17. 17. Identifying things
    18. 18. Identifying things
    19. 19. Identifying things 1969-059A
    20. 20. Identifying things 1969-059A spacecraft/1969-059A
    21. 21. Identifying things 1969-059A spacecraft/1969-059Anasa.dataincubator.org/spacecraft/1969-059A
    22. 22. Identifying things with URIs 1969-059A spacecraft/1969-059A nasa.dataincubator.org/spacecraft/1969-059Ahttp://nasa.dataincubator.org/spacecraft/1969-059A
    23. 23. Things have attributeshttp://nasa.dataincubator.org/spacecraft/1969-059A
    24. 24. Things have attributeshttp://nasa.dataincubator.org/spacecraft/1969-059A28801.0kg
    25. 25. Things have attributeshttp://nasa.dataincubator.org/spacecraft/1969-059A28801.0kgColumbia
    26. 26. Things have attributeshttp://nasa.dataincubator.org/spacecraft/1969-059A28801.0kgColumbiaApollo 11 CSMCSM-107United StatesCape CanaveralSaturn 5
    27. 27. http://nasa.dataincubator.org/spacecraft/1969-059A
    28. 28. http://nasa.dataincubator.org/spacecraft/1969-059A .../spacecraft/ 1969-059A
    29. 29. .../spacecraft/http://nasa.dataincubator.org/spacecraft/1969-059A 1969-059A
    30. 30. 28801.0 mass .../spacecraft/http://nasa.dataincubator.org/spacecraft/1969-059A 1969-059A
    31. 31. Apollo 11 CSM 28801.0 name mass .../spacecraft/http://nasa.dataincubator.org/spacecraft/1969-059A 1969-059A
    32. 32. Apollo 11 CSM Columbia name 28801.0 name mass .../spacecraft/http://nasa.dataincubator.org/spacecraft/1969-059A 1969-059A
    33. 33. Apollo 11 CSM Columbia name 28801.0 name mass .../spacecraft/http://nasa.dataincubator.org/spacecraft/1969-059A 1969-059A launch ../launch/1969-059
    34. 34. Apollo 11 CSM Columbia name 28801.0 name mass .../spacecraft/ 16 July 1969http://nasa.dataincubator.org/spacecraft/1969-059A 1969-059A launch date ../launch/1969-059
    35. 35. Apollo 11 CSM Columbia name 28801.0 name mass .../spacecraft/ 16 July 1969http://nasa.dataincubator.org/spacecraft/1969-059A 1969-059A launch date ../launch/1969-059 site ../cape canaveral
    36. 36. Apollo 11 CSM Columbia name 28801.0 name mass .../spacecraft/ 16 July 1969http://nasa.dataincubator.org/spacecraft/1969-059A 1969-059A launch date ../launch/1969-059 site ../cape canaveral lat N 28° 27 31
    37. 37. Apollo 11 CSM Columbia name 28801.0 name mass .../spacecraft/ 16 July 1969http://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
    38. 38. Apollo 11 CSM Columbia name 28801.0 name mass .../spacecraft/ 16 July 1969http://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
    39. 39. RDF Apollo 11 CSM Columbia name 28801.0 name mass .../spacecraft/ 16 July 1969http://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
    40. 40. RDF Triple
    41. 41. RDF TripleThing attribute value
    42. 42. RDF TripleThing property value
    43. 43. RDF TripleThing property valueThing property Thing
    44. 44. RDF Triple Thing property value Thing property Thing../person/A
    45. 45. RDF Triple Thing property value Thing property Thing../person/A hasParent
    46. 46. RDF Triple Thing property value Thing property Thing../person/A hasParent ../person/B
    47. 47. RDF Triple Thing property value Thing property Thing../person/A hasParent ../person/B../person/B
    48. 48. RDF Triple Thing property value Thing property Thing../person/A hasParent ../person/B../person/B name
    49. 49. RDF Triple Thing property value Thing property Thing../person/A hasParent ../person/B../person/B name “Eric”
    50. 50. RDF Triple Merging Thing property value Thing property Thing../person/A hasParent ../person/B ../person/B name “Eric”
    51. 51. RDF Triple Merging Thing property value Thing property Thing../person/A hasParent ../person/B name “Eric”
    52. 52. RDF Triple Merging
    53. 53. RDF Triple MergingThe same identifier in a different place is still identifying the same thing
    54. 54. Linked Data Principles
    55. 55. Linked Data Principles1. Use URIs as names for things
    56. 56. Linked Data Principles1. Use URIs as names for things2. Use HTTP URIs so people can look up those names
    57. 57. Linked Data Principles1. Use URIs as names for things2. Use HTTP URIs so people can look up those names3. When someone looks up a URI, provide useful information, using the standards RDF, SPARQL
    58. 58. 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 moreTim Berners-Lee - 2006
    59. 59. Linked Data Principles
    60. 60. Linked Data Principles1. Identify your things with URIs
    61. 61. Linked Data Principles1. Identify your things with URIs2. When someone looks up your identifier give them information in a [Web] standard form
    62. 62. Linked Data Principles1. Identify your things with URIs2. When someone looks up your identifier give them information in a [Web] standard form3. Include links to other things (URIs), so that they can discover more
    63. 63. Linked Data Principles1. Identify your things with URIs2. When someone looks up your identifier give them information in a [Web] standard form3. Include links to other things (URIs), so that they can discover more4. Enable follow-your-nose discovery/navigation RJW - 2011
    64. 64. 80% of data contains location!
    65. 65. lo ✗ ts 80% of data contains location!
    66. 66. lo ✗ ts 80% of data contains location! http://mydomain.com/location/London
    67. 67. lo ✗ ts 80% of data contains location! http://mydomain.com/location/London sameAs
    68. 68. lo ✗ ts 80% of data contains location! http://mydomain.com/location/London sameAs http://dbpedia.org/resource/London
    69. 69. lo ✗ ts 80% of data contains location! http://mydomain.com/location/London sameAs http://dbpedia.org/resource/London
    70. 70. lo ✗ ts 80% of data contains location! http://mydomain.com/location/London sameAs http://dbpedia.org/resource/London http://dbpedia.org/resource/London
    71. 71. lo ✗ ts 80% of data contains location! http://mydomain.com/location/London sameAs http://dbpedia.org/resource/London http://dbpedia.org/resource/London sameAs
    72. 72. 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/
    73. 73. 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/
    74. 74. 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
    75. 75. Data Open and/or Linked
    76. 76. Data Open and/or Linked 1. Data can be open, while not being linked
    77. 77. Data Open and/or Linked 1. Data can be open, while not being linked 2. Data can be linked, while not being open
    78. 78. 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
    79. 79. 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 linkedPaul Walk - UKLON
    80. 80. Putting the theory in to practice http://www.flickr.com/photos/stuartpilbrow/3449993951
    81. 81. Putting the theory in to practice What do I need to know? http://www.flickr.com/photos/stuartpilbrow/3449993951
    82. 82. Putting the theory in to practice What do I need to know? What skills are needed? http://www.flickr.com/photos/stuartpilbrow/3449993951
    83. 83. Linked DataWhat do I need to know?
    84. 84. Linked Data What do I need to know?• Globally distributed / adopted
    85. 85. Linked Data What do I need to know?• Globally distributed / adopted• Still evolving
    86. 86. Linked Data What do I need to know?• Globally distributed / adopted• Still evolving• Built on Web standards
    87. 87. Linked Data What do I need to know?• Globally distributed / adopted• Still evolving• Built on Web standards• Recommended best practice
    88. 88. Linked Data What do I need to know?• Globally distributed / adopted• Still evolving• Built on Web standards• Recommended best practice• Low barrier to data
    89. 89. 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
    90. 90. 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
    91. 91. 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
    92. 92. Linked Data
    93. 93. Linked DataWhat skills are needed?
    94. 94. Linked Data What skills are needed?• Domain experience/understanding
    95. 95. Linked Data What skills are needed?• Domain experience/understanding• Appreciation of Linked Data principles
    96. 96. Linked Data What skills are needed?• Domain experience/understanding• Appreciation of Linked Data principles• Guidance from experience
    97. 97. Linked Data What skills are needed?• Domain experience/understanding• Appreciation of Linked Data principles• Guidance from experience• Open world thinking
    98. 98. 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
    99. 99. 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
    100. 100. Lin ked Da ta
    101. 101. Lin ked Da ta Hyped?
    102. 102. Lin ked Da ta Hyped? – of course
    103. 103. Lin ked Da ta Hyped? – of coursePotential to deliver better use of data
    104. 104. Lin ked Da ta Hyped? – of coursePotential to deliver better use of data – yes
    105. 105. Lin ked Da ta Hyped? – of coursePotential to deliver better use of data – yesPotential to deliver wider use of data
    106. 106. Lin ked Da ta Hyped? – of coursePotential to deliver better use of data – yesPotential to deliver wider use of data – yes
    107. 107. Lin ked Da ta Hyped? – of coursePotential to deliver better use of data – yesPotential to deliver wider use of data – yes Successful examples
    108. 108. Lin ked Da ta Hyped? – of coursePotential to deliver better use of data – yesPotential to deliver wider use of data – yes Successful examples – many
    109. 109. Lin ked Da ta Hyped? – of coursePotential to deliver better use of data – yesPotential to deliver wider use of data – yes Successful examples – many ROI
    110. 110. Lin ked Da ta Hyped? – of coursePotential to deliver better use of data – yesPotential to deliver wider use of data – yes Successful examples – many ROI – yes
    111. 111. Lin ked Da ta Hyped? – of coursePotential to deliver better use of data – yesPotential to deliver wider use of data – yes Successful examples – many ROI – yes New business model opportunities
    112. 112. Lin ked Da ta Hyped? – of coursePotential to deliver better use of data – yesPotential to deliver wider use of data – yes Successful examples – many ROI – yes New business model opportunities – yes
    113. 113. Lin ked Da ta Hyped? – of coursePotential to deliver better use of data – yesPotential to deliver wider use of data – yes Successful examples – many ROI – yes New business model opportunities – yes Enterprise application
    114. 114. Lin ked Da ta Hyped? – of coursePotential to deliver better use of data – yesPotential to deliver wider use of data – yes Successful examples – many ROI – yes New business model opportunities – yes Enterprise application – yes
    115. 115. Lin ked Da ta Hyped? – of coursePotential to deliver better use of data – yesPotential to deliver wider use of data – yes Successful examples – many ROI – yes New business model opportunities – yes Enterprise application – yes Difficult
    116. 116. Lin ked Da ta Hyped? – of coursePotential to deliver better use of data – yesPotential to deliver wider use of data – yes Successful examples – many ROI – yes New business model opportunities – yes Enterprise application – yes Difficult – no
    117. 117. Lin ked Da ta Hyped? – of coursePotential to deliver better use of data – yesPotential 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
    118. 118. Lin ked Da ta Hyped? – of coursePotential to deliver better use of data – yesPotential 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
    119. 119. Linked Data What is just flannelWhat skill sets are required? Richard Wallis @rjw

    ×