Mercurial > hg > dbtune-site

diff onto/talks/mo-ismir-2007/index.html @ 0:1e44d666ced1

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import site from parrot
author Chris Cannam
date Fri, 13 Oct 2017 09:23:49 +0100
parents
children
line wrap: on
line diff
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/onto/talks/mo-ismir-2007/index.html	Fri Oct 13 09:23:49 2017 +0100
@@ -0,0 +1,392 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+
+
+<head>
+<title>The Music Ontology</title>
+<!-- metadata -->
+<meta name="generator" content="S5" />
+<meta name="version" content="S5 1.1" />
+<meta name="author" content="Yves Raimond" />
+<meta name="company" content="C4DM, Queen Mary, University of London" />
+<!-- configuration parameters -->
+<meta name="defaultView" content="slideshow" />
+<meta name="controlVis" content="hidden" />
+<!-- style sheet links -->
+<link rel="stylesheet" href="ui/mo/slides.css" type="text/css" media="projection" id="slideProj" />
+<link rel="stylesheet" href="ui/mo/outline.css" type="text/css" media="screen" id="outlineStyle" />
+<link rel="stylesheet" href="ui/mo/print.css" type="text/css" media="print" id="slidePrint" />
+<link rel="stylesheet" href="ui/mo/opera.css" type="text/css" media="projection" id="operaFix" />
+<!-- embedded styles -->
+<style type="text/css" media="all">
+.imgcon {width: 525px; margin: 0 auto; padding: 0; text-align: center;}
+#anim {width: 270px; height: 320px; position: relative; margin-top: 0.5em;}
+#anim img {position: absolute; top: 42px; left: 24px;}
+img#me01 {top: 0; left: 0;}
+img#me02 {left: 23px;}
+img#me04 {top: 44px;}
+img#me05 {top: 43px;left: 36px;}
+</style>
+<!-- S5 JS -->
+<script src="ui/mo/slides.js" type="text/javascript"></script>
+</head>
+
+<body>
+
+<div class="layout"/>
+<div id="controls"><!-- DO NOT EDIT --></div>
+<div id="currentSlide"><!-- DO NOT EDIT --></div>
+<div id="header"></div>
+<div id="footer">
+<h1>Yves Raimond, Music Ontology Specification Group</h1>
+<h2>yves@dbtune.org &#8226; 26/09/2007</h2>
+</div>
+
+<div class="presentation">
+
+
+
+<div class="slide">
+<h1>The Music Ontology</h1>
+<h3>Yves Raimond, Samer Abdallah, Mark Sandler, Frederick Giasson</h3>
+<h4><a href="http://www.elec.qmul.ac.uk/digitalmusic/">Centre for Digital Music, Queen Mary, University of London</a></h4>
+</div>
+
+<div class="slide">
+<h1>  Overview</h1>
+<ul>
+	<li>Introduction</li>
+	<!--<ul>
+		<li>Music-related datasets on the web</li>
+		<li>Current issues</li>
+	</ul>-->
+	<li>Towards a web of data</li>
+	<!--<ul>
+		<li>Dereferencable identifiers + RDF = Linked data</li>
+		<li>Vocabularies</li>
+		<li>Emerging applications</li>
+	</ul>-->
+	<li>The Music Ontology</li>
+	<!--<ul>
+		<li>The Timeline Ontology</li>
+		<li>The Event Ontology</li>
+		<li>FRBR and FOAF</li>
+		<li>Music production concepts</li>
+		<li>The Music production workflow</li>
+		<li>Current and planned extensions</li>
+	</ul>-->
+	<li>A music-related web of data</li>
+	<!--<ul>
+		<li>Linking Open Data on the Semantic Web</li>
+		<li>Current map</li>
+	</ul>-->
+	<li>Conclusion and Future Work</li>
+</ul>
+</div>
+
+<div class="slide">
+<h1>  Introduction</h1>
+<h2>Music-related datasets on the web</h2>
+<br/><br/>
+<center><img src="current_state.png" height="60%" width="60%"/></center>
+</div>
+
+
+<!--<div class="slide">
+<h1>  Introduction</h1>
+<h2>Music-related datasets on the web</h2>
+<font size="5">
+<ul>
+<li>Lots of structured information under-the-hood (MusicMoz, Jamendo, Magnatune, Musicbrainz, Wikipedia, etc.)</li>
+<li>This data is just used to create human-readable <strong>documents</strong>
+<li>Interlinking, when it exists, is just done at this level (<strong>&lt;a href=...&gt;</strong>), you need to understand the <i>context</i> of the
+link to figure out what it <i>means</i></li>
+</ul>
+</font>
+<br/>
+<font size="5">
+<strong>How can we relate a particular artist described in one dataset (Musicbrainz...) to a track available in another one (Jamendo...)?</strong>
+<br/><br/>
+<strong>How can we write this link (<strong>artist made track</strong>) in a machine-processable way (for access purpose)?</strong>
+</font>
+</div>-->
+
+<div class="slide">
+<!--<h1>  Towards a Web of Data</h1>-->
+<h1>Linked data</h1>
+<h4><li>Resources on the Web can be far more than web pages!</li></h4>
+<ul>
+<li><strong><a href="http://moustaki.org/foaf.rdf#moustaki">http://moustaki.org/foaf.rdf#moustaki</a></strong> is identifying <i>me</i></li>
+<li><strong><a href="http://dbtune.org/jamendo/band/lonah">http://dbtune.org/jamendo/artist/5</a></strong> is identifying the French band <i>Both</i></li>
+<li><strong><a href="http://zitgist.com/music/artist/a15e2d0a-efcb-4f4f-ad54-22a4879bbcf9">http://zitgist.com/music/track/a15e2d0a-efcb-4f4f-ad54-22a4879bbcf9</a></strong> is identifying <i>Iron Man</i>, by <i>Black Sabbath</i></li>
+</ul>
+</div>
+
+<div class="slide">
+<!--<h1>Dereferencable identifiers + RDF = Linked data</h1>-->
+<h1>Linked data</h1>
+<ul>
+<li>Resources have associated <i>representations</i>, accessed through a <i>dereferencing</i> process, which can be:</li>
+<ul>
+<li>Human-friendly (HTML, Flash, plain text, audio, video, etc.)</li>
+<li>Machine-friendly (RDF, Microformats, RSS, etc.)</li>
+</ul>
+<li>Representations may hold <i>links</i>, allowing an agent (a program or a person) to discover more things</li>
+<!--<ul>
+<li>The &lt;a href="<strong>http://musicbrainz.org/</strong>"&gt;<a href="http://musicbrainz.org/">Musicbrainz</a>&lt;/a&gt; community database</li>
+<li><strong>&lt;http://dbtune.org/jamendo/artist/5&gt;</strong> <strong>&lt;http://xmlns.com/foaf/0.1/based_near&gt;</strong> <strong>&lt;http://sws.geonames.org/2991627/&gt;</strong>.</li> 
+</ul>-->
+</ul>
+</div>
+
+<div class="slide">
+<h1>Linked data</h1>
+<center><img src="contentneg.png" height="70%" width="70%"/></center>
+</div>
+
+<div class="slide">
+<h1>Linked data</h1>
+<!--<h2>Dereferencable identifiers + RDF = Linked data</h2>-->
+<center><img src="both.png" height="90%" width="90%"/></center>
+</div>
+
+
+<div class="slide">
+<h1>Vocabularies / Ontologies</h1>
+<h2>Such data is also linked to a particular model of its domain: an <i>ontology</i></h2>
+<font size="5">
+<ul>
+<li> <strong>&lt;http://dbtune.org/jamendo/artist/5&gt;</strong> <strong>rdf:type</strong> <strong>foaf:Person</strong> specifies that this resource
+is a person, as defined in the FOAF ontology</li>
+<li>A <strong>performance</strong> involves some <strong>performer</strong>, a <strong>place</strong>, a <strong>time</strong></li>
+<li>Ontologies are linked together: <strong>mo:Performance</strong> <strong>rdfs:subClassOf</strong> <strong>event:Event</strong>...</li>
+<li>... And therefore part of the data web</li>
+</ul>
+</font>
+</div>
+
+
+<div class="slide">
+<h1>  The Data Web</h1>
+<strong>Turning the Web into a huge democratic, decentralized, database that can be directly consumed by applications</strong><br/>
+<center><img src="mfmslinked.png" height="70%" width="70%"/></center>
+</div>
+
+<div class="slide">
+<h1> The Music Ontology</h1>
+<center><img src="Mo-logo-big.jpg"/></center>
+<h2>A framework for dealing with music-related information on the Semantic Web</h2>
+<font size="5">
+<ul>
+<li>Complex editorial information (worflow-based)</li>
+<li>Temporal annotations</li>
+<li>Cultural information (folksonomies, social networks, etc.)</li>
+<li>Modular, adaptable, and designed to fit the needs of the community</li>
+<li>Mesh nicely with Creative Commons RDF license information</li>
+</ul>
+</font>
+</div>
+
+<div class="slide">
+<h1>  The Timeline Ontology</h1>
+<h2>Expressing temporal information, eg.</h2>
+<font size="5">
+<ul>
+<li>This performance happened the 9th of March, 1984</li>
+<li>This beat is occurring around sample 32480</li>
+<li>The second verse is just before the second chorus</li>
+</ul>
+</font><br/>
+<h2>This ontology defines: </h2>
+<font size="5">
+<ul>
+<li><strong>Interval</strong> (origin: OWL-Time)</li>
+<li><strong>Instant</strong> (origin: OWL-Time)</li>
+<li><strong>TimeLine</strong> &mdash; A backbone for addressing temporal information</li>
+<li><strong>TimeLineMap</strong> &mdash; Relationship between two timelines</li>
+</ul>
+</font>
+</div>
+
+<div class="slide">
+<h1>  The Timeline Ontology</h1>
+<center><img src="timeline.png" width="70%" height="70%"/></center>
+</div>
+
+<div class="slide">
+<h1>  The Event Ontology</h1>
+<!--<font size="5">Performance, recordings, structural segments, beats, etc.</font>-->
+<br/><strong>Event</strong> &mdash; An arbitrary classification of a space/time region<br/>
+<ul>
+<li>This performance involved Glenn Gould playing the piano</li>
+<li>This signal was recorded using a XXX microphone located at that particular place</li>
+<li>This beat is occurring around sample 32480</li>
+</ul>
+</div>
+
+<div class="slide">
+<h1>  The Event Ontology</h1>
+<center><img src="event.png" width="50%" height="50%"/></center>
+</div>
+
+<div class="slide">
+<h1>  FRBR and FOAF</h1>
+<h2> Functional Requirements for Bibliographic Records:</h2>
+<font size="5">
+<ul>
+<li><strong>Work</strong> &mdash; eg. <i>Franz Schubert's Trout Quintet</i></li>
+<li><strong>Manifestation</strong> &mdash; eg. <i>the "Nevermind" album</i></li>
+<li><strong>Item</strong> &mdash; eg. <i>my "Nevermind" copy</i></li>
+<!--<li>(We leave Expression behind for now...)</li>-->
+</ul>
+</font><br/>
+<h2> Friend of a Friend:</h2>
+<font size="5">
+<ul>
+<li><strong>Person</strong></li>
+<li><strong>Group</strong></li>
+<li><strong>Organization</strong></li>
+<li>Social networking information (ask Oscar :-) )</li>
+</ul>
+</font>
+
+</div>
+
+<div class="slide">
+<h1>  Music Production concepts</h1>
+<ul>
+<li> On top of FRBR:</li>
+<font size="5">
+<strong>MusicalWork, MusicalManifestation (Record, Track, Playlist, etc.), MusicalItem (Stream, AudioFile, Vynil, etc.)</strong>
+</font>
+<li> On top of FOAF:</li>
+<font size="5">
+<strong>MusicArtist, MusicGroup, Arranger, Engineer, Performer, Composer, etc.</strong> &mdash; all these are <i>defined classes</i>: 
+every person involved in a performance is a a performer...
+</font>
+<li> On top of the Event Ontology:</li>
+<font size="5">
+<strong>Composition, Arrangement, Performance, Recording</strong>
+</font>
+<li> Others : <!--(several FRBR <i>expressions</i> among them):--></li>
+<font size="5">
+<strong>Signal, Score, Genre, Instrument, ReleaseStatus, Lyrics, Libretto, etc.</strong>
+</font>
+</ul>
+</div>
+
+<div class="slide">
+<h1>  The Music production workflow</h1>
+<!--<br/><br/>-->
+<center>
+<img src="mo-workflow.jpg" width="99%"/>
+</center>
+</div>
+
+<!--<div class="slide">
+<h1>  The Music Ontology layers</h1>
+<h2>Different communities have different needs</h2><br/>
+<ul>
+<li><strong>1st level:</strong> purely editorial<br/><font size="5"><i>This track is on that particular album and that 
+compilation and was created by that artist</i></font></li>
+<li><strong>2nd level:</strong> introducing events<br/><font size="5"><i>This is a recording of this particular musician playing that 
+jazz-rock arrangement of that particular piece</i></font></li>
+<li><strong>3rd level:</strong> introducing event decomposition<br/><font size="5"><i>In this performance, this key was played at this particular 
+time by this person, who was playing the piano</i></font></li>
+</ul>
+</div>-->
+
+<div class="slide">
+<h1>  Current and planned extensions</h1>
+<h2>Available extensions:</h2>
+<font size="3">
+<ul>
+<li>Audio feature ontology (<strong>Onset, Beat, Structural segment</strong>, etc.)
+<a href="http://purl.org/ontology/af/">http://purl.org/ontology/af/</a></li>
+<li>Instrument taxonomy <a href="http://purl.org/ontology/mo/mit/">http://purl.org/ontology/mo/mit/</a></li>
+<li>Genre taxonomy <a href="http://dbpedia.org/">http://dbpedia.org/</a></li>
+<li>Chord ontology <a href="http://purl.org/ontology/chord/">http://purl.org/ontology/chord/</a></li>
+</ul>
+</font><br/>
+<h2>Possible extensions:</h2>
+<font size="3">
+<ul>
+<li>Recording devices under <strong>Recording</strong></li>
+<li><strong>Mixing</strong> events dealing with <strong>Signal</strong> objects</li>
+<li>Symbolic notation under <strong>Score</strong> and <strong>AbstractTimeLine</strong></li>
+<li>Taxonomy of music processing predicates</li>
+</ul>
+</font>
+</div>
+
+<div class="slide">
+<h1>  Linking Open Data</h1>
+<font size="5">
+<ul>
+<li>A <a href="http://www.w3.org/2001/sw/sweo/">W3C Semantic Web Education and Outreach</a> community project.</li>
+<li>Lots of <i>open data</i> available: Wikipedia, Geonames, Eurostat, Musicbrainz, Magnatune, etc.</li>
+<li><strong>Let's interlink them using Semantic Web technologies &mdash; <i>data mashups</i></strong></li>
+<li>A subset of this project is the <a href="http://blog.dbtune.org">dbtune</a> project, aiming at interlinking lots of music-related datasets using <a href="http://musicbrainz.org/">Musicbrainz</a> as a <i>data hub</i></li>
+</ul>
+</font>
+</div>
+
+
+<div class="slide">
+<h1>  Current Map</h1>
+<center>
+<img src="lod-datasets_2007-09-04.png" width="60%" height="60%"/>
+</center>
+</div>
+
+<div class="slide">
+<h1>  Conclusion and Future work</h1>
+<h2>Conclusion</h2>
+<font size="5">
+<ul>
+<li>RDF and HTTP provides a way to create a <i>Web of data</i></li>
+<li>Vocabulary (Music Ontology) and <i>data hub</i> (<i>Linking Open Data</i>) for further interlinking of music-related datasets</li>
+<!--<li>The <a href="http://blog.dbtune.org/post/2007/08/30/GNAT-01-released">GNAT</a> software allows you to link a music collection to this Web (shameless plug)</li>-->
+<li>The <a href="http://motools.svn.sourceforge.net/viewvc/motools/mopy/">MOPY</a> Python library (Chris Sutton) allows you to manipulate Music Ontology documents without having to write one line of RDF!</li>
+<li>The <a href="http://motools.svn.sourceforge.net/viewvc/motools/gnat/">GNAT</a> software allows you to find dereferencable identifiers
+for items in your audio collection</li>
+</ul>
+</font>
+</div>
+
+<div class="slide">
+<h1>  Conclusion and Future work</h1>
+<h2>Further Work</h2>
+<font size="5">
+<ul>
+<li>Well, more interlinking!</li>
+<!--<li>Extending the GNAT software to use a wide range of geographical, editorial, cultural, encyclopedical information to manage music collections<br/>-->
+<li>Semantic-Web-enabled music collection handler:<br/>
+<i>Give me all musical works composed in a city with more than 500 000 inhabitants</i><br/>
+<i>Is there someone nearby really liking this band and the same beer as me, so that we can have a drink tomorrow?</i><br/>
+<i>Place my collection on a timeline and make me listen something composed in the UK in 1560, followed by a rock song recorded in the 60s</i><br/>
+<i>Are there any other performances of this work? Give me one with a small part at 120 bpm</i></li>
+<li>Publishing features using Semantic Web technologies! (+interpretation rules)</li>
+<!--<li>Tracking accuracy of information through its provenance (reasoner? Musicbrainz? etc.)</li>-->
+</ul>
+</font>
+</div>
+
+<div class="slide">
+<h1>  Epilogue</h1>
+<h2>And well, what would be a Semantic Web talk without a google map?</h2>
+<center>
+<img src="screenshot5.png" width="70%" height="70%"/>
+</center>
+</div>
+
+<div class="slide">
+<h1>Questions ?</h1>
+</div>
+
+</div>
+</body>
+
+</html>
+