Publishing and interlinking music-related data on the web  Yves Raimond, BBC Audio&Music interactive
Linked data
The Web <ul><li>Names (URIs)
Documents (HTML, XML, JSON, ...)
Interactions with names (HTTP) </li></ul>Names Documents HTTP GET
Web of documents <ul><li>Names identify documents, e.g. HTML, XML, etc.
Documents are interlinked: </li></ul><a href=” http://moustaki.org/ ” />
Web of documents
We understand...
We understand...
Machines don't...
Shortcomings <ul><li>Opacity of documents </li><ul><li>“In 1883,  Fauré  married Marie Fremiet”
Who? Gabriel? Edgar? Félix? </li></ul><li>Untyped links </li><ul><li>“Edgar Faur e  was born in  Béziers ”
Interpreting the surrounding context is hard for a machine </li></ul><li>We're unable to use the Web as a big database </l...
Silos and views
Linked data <ul>Let's expose and interlink the actual data, not only the documents! </ul>
Linked data <ul><li>The 4 Linked Data principles (TimBL 06) </li></ul><ul><ul><li>Use URIs as names for things
Use HTTP URIs so that people can look up those names
When someone looks up a URI, provide useful structured data
Include links to other URIs, so that they can discover more things </li></ul></ul>
RDF <ul><li>RDF is the web standard for such structured data
RDF data model: </li><ul><li>Subject (URI)
Property (URI)
Object (URI or literal) </li></ul><li>“Fauré” “born in” “London”
“I” “work near” “Broadcasting House” </li></ul>
RDF And that's all! (yes, really...)
Web of data A web of things
Linking Open Data project <ul><li>Use these technologies to create a “web of data”
Publish and interlink various open datasets, across various domain and disciplines </li><ul><li>Music,
Bio-informatics,
Scientific publications,
Libraries,
Geography
Census data... </li></ul></ul>
 
Linking Open Data
How are they related? ? (No, not the moustache)
Gabriel Fauré <ul>http://dbpedia.org/resource/Gabriel_Fauré </ul>
Is the same as <ul>http://rdf.freebase.com/ns/guid.9202a8c04000641f80000000000850fd </ul>
Was born in <ul>http://rdf.freebase.com/ns/en.pamiers </ul>
Is the same as <ul>http://dbpedia.org/resource/Pamiers </ul>
Is located within <ul>http://dbpedia.org/resource/Ariège </ul>
Is located within <ul>http://dbpedia.org/resource/Midi-Pyrénées </ul>
Is the birth place of <ul>http://dbpedia.org/resource/Charles_Boyer </ul>
Is part of <ul>http://dbpedia.org/resource/Category:Drug-related_deaths_in_Arizona </ul>
Has member <ul>http://dbpedia.org/resource/Mattie_Blaylock </ul>
Is spouse of <ul>http://dbpedia.org/resource/Wyatt_Earp </ul>
Why is that important? <ul><li>Data without context is almost useless
Make your data accessible for other researchers
Make your data linkable
Upcoming SlideShare
Loading in...5
×

Publishing and interlinking music-related data on the Web

1,315

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,315
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
17
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Publishing and interlinking music-related data on the Web

  1. 1. Publishing and interlinking music-related data on the web Yves Raimond, BBC Audio&Music interactive
  2. 2. Linked data
  3. 3. The Web <ul><li>Names (URIs)
  4. 4. Documents (HTML, XML, JSON, ...)
  5. 5. Interactions with names (HTTP) </li></ul>Names Documents HTTP GET
  6. 6. Web of documents <ul><li>Names identify documents, e.g. HTML, XML, etc.
  7. 7. Documents are interlinked: </li></ul><a href=” http://moustaki.org/ ” />
  8. 8. Web of documents
  9. 9. We understand...
  10. 10. We understand...
  11. 11. Machines don't...
  12. 12. Shortcomings <ul><li>Opacity of documents </li><ul><li>“In 1883, Fauré married Marie Fremiet”
  13. 13. Who? Gabriel? Edgar? Félix? </li></ul><li>Untyped links </li><ul><li>“Edgar Faur e was born in Béziers ”
  14. 14. Interpreting the surrounding context is hard for a machine </li></ul><li>We're unable to use the Web as a big database </li></ul>
  15. 15. Silos and views
  16. 16. Linked data <ul>Let's expose and interlink the actual data, not only the documents! </ul>
  17. 17. Linked data <ul><li>The 4 Linked Data principles (TimBL 06) </li></ul><ul><ul><li>Use URIs as names for things
  18. 18. Use HTTP URIs so that people can look up those names
  19. 19. When someone looks up a URI, provide useful structured data
  20. 20. Include links to other URIs, so that they can discover more things </li></ul></ul>
  21. 21. RDF <ul><li>RDF is the web standard for such structured data
  22. 22. RDF data model: </li><ul><li>Subject (URI)
  23. 23. Property (URI)
  24. 24. Object (URI or literal) </li></ul><li>“Fauré” “born in” “London”
  25. 25. “I” “work near” “Broadcasting House” </li></ul>
  26. 26. RDF And that's all! (yes, really...)
  27. 27. Web of data A web of things
  28. 28. Linking Open Data project <ul><li>Use these technologies to create a “web of data”
  29. 29. Publish and interlink various open datasets, across various domain and disciplines </li><ul><li>Music,
  30. 30. Bio-informatics,
  31. 31. Scientific publications,
  32. 32. Libraries,
  33. 33. Geography
  34. 34. Census data... </li></ul></ul>
  35. 36. Linking Open Data
  36. 37. How are they related? ? (No, not the moustache)
  37. 38. Gabriel Fauré <ul>http://dbpedia.org/resource/Gabriel_Fauré </ul>
  38. 39. Is the same as <ul>http://rdf.freebase.com/ns/guid.9202a8c04000641f80000000000850fd </ul>
  39. 40. Was born in <ul>http://rdf.freebase.com/ns/en.pamiers </ul>
  40. 41. Is the same as <ul>http://dbpedia.org/resource/Pamiers </ul>
  41. 42. Is located within <ul>http://dbpedia.org/resource/Ariège </ul>
  42. 43. Is located within <ul>http://dbpedia.org/resource/Midi-Pyrénées </ul>
  43. 44. Is the birth place of <ul>http://dbpedia.org/resource/Charles_Boyer </ul>
  44. 45. Is part of <ul>http://dbpedia.org/resource/Category:Drug-related_deaths_in_Arizona </ul>
  45. 46. Has member <ul>http://dbpedia.org/resource/Mattie_Blaylock </ul>
  46. 47. Is spouse of <ul>http://dbpedia.org/resource/Wyatt_Earp </ul>
  47. 48. Why is that important? <ul><li>Data without context is almost useless
  48. 49. Make your data accessible for other researchers
  49. 50. Make your data linkable
  50. 51. Publish and maintain only your data, and leave the burden of ancillary descriptions to other communities of interest
  51. 52. … who link to other communities of interest …
  52. 53. Enable cross-domain queries to be formulated
  53. 54. “ The whole is greater than the sum of the parts” </li></ul>
  54. 55. The Music Ontology
  55. 56. The Music Ontology <ul><li>A framework to deal with music-related information on the web of data
  56. 57. Based on other ontologies </li><ul><li>Timeline
  57. 58. Event
  58. 59. FOAF
  59. 60. FRBR </li></ul></ul>
  60. 61. The Timeline ontology <ul><li>Expressing temporal information on multiple timelines </li><ul><li>This performance happened on the 31 st of August, 2008
  61. 62. There is a beat occurring around sample 32480
  62. 63. The second verse is just before the second chorus </li></ul><li>Timelines for e.g. </li><ul><li>Scores
  63. 64. Performances
  64. 65. Audio signals </li></ul></ul>
  65. 66. The Timeline ontology
  66. 67. The Event ontology <ul><li>Classifying space–time regions </li><ul><li>This performance involved Glenn Gould playing the Piano
  67. 68. This signal was recorded using a Shure microphone located on the top–left of the guitar amplifier
  68. 69. On this particular recording of that performance, that particular part starts at 12 minutes and 53 seconds and lasts 9 minutes 12 </li></ul></ul>
  69. 70. The Event ontology
  70. 71. FRBR <ul><li>Functional Requirements for Bibliographic records
  71. 72. Layering in abstraction </li><ul><li>Work
  72. 73. Expression
  73. 74. Manifestation
  74. 75. Item </li></ul></ul>
  75. 76. The Music Ontology... ...subsumes these ontologies to deal with music-related information
  76. 77. The Music Ontology <ul><li>Editorial </li><ul><li>Record, Track, Playlist, Vynil, CD, Artist, Band </li></ul><li>Production workflow </li><ul><li>Musical work, Arrangement, Score, Performance, Sound, Recording, Audio Signal </li></ul><li>Roles </li><ul><li>Engineer, Performer, Composer, Listener </li></ul><li>Anchor points for taxonomies </li><ul><li>Instrument, Genre, Form </li></ul></ul>
  77. 78. The Music Ontology
  78. 79. But also... <ul><li>Extensions to deal with: </li><ul><li>Chords and keys
  79. 80. Audio features, e.g. Key changes
  80. 81. Instrument taxonomies
  81. 82. Symbolic information
  82. 83. Visualisation tools </li><ul><li>http://www.sonicvisualiser.org </li></ul><li>LOTS of available linked data!! </li><ul><li>http://dbtune.org/ (>14 billion statements)
  83. 84. http://www.bbc.co.uk/music ( ~500 million) </li></ul></ul></ul>
  84. 85. Linked Data at the BBC
  85. 86. Not so long ago... <ul><li>Static web pages uploaded via FTP
  86. 87. Strictly hierarchical navigation </li></ul>
  87. 88. Things are changing... <ul><li>It's all about the resource and its relationship to other things, within the BBC or outside </li><ul><li>Artists
  88. 89. Programmes
  89. 90. Events
  90. 91. Places
  91. 92. Reviews
  92. 93. Food
  93. 94. News
  94. 95. ... </li></ul></ul>
  95. 96. What we're doing <ul><li>One URI for everything
  96. 97. Different representations for a single thing </li><ul><li>HTML
  97. 98. RDF
  98. 99. JSON
  99. 100. Mobile
  100. 101. Etc. </li></ul><li>Links to other things within these representations
  101. 102. From a tree to a graph... </li></ul>
  102. 103. Ontologies at the BBC <ul><li>http://www.bbc.co.uk/ontologies
  103. 104. Define the things we publish a page for </li><ul><li>Programmes
  104. 105. Categories
  105. 106. Artists
  106. 107. Etc. </li></ul><li>Define the links between those things </li><ul><li>Programme -> Artist
  107. 108. Artist -> Programme
  108. 109. Programme -> Category... </li></ul></ul>
  109. 110. Demo
  110. 111. Demo
  111. 112. Demo Re-purposing our data: http://api.talis.com/stores/bbc-backstage/services/sparql http://blog.dbtune.org/ http://api.talis.com/stores/ldodds-dev1/items/subject-relations.html http://api.talis.com/stores/ldodds-dev1/items/reviewers.html
  112. 113. Questions?
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×