diff musicweb.tex @ 56:483df26a74d8 tip

minor corrections and changes to rebuttal

--- a/musicweb.tex	Thu Jun 16 00:18:12 2016 +0100
+++ b/musicweb.tex	Thu Jun 16 00:40:54 2016 +0100
@@ -229,6 +229,13 @@
 	\label{fig:layers}
 \end{figure}
 
+\begin{figure}[!ht]
+	\centering
+	\includegraphics[scale=0.5]{graphics/mw_flow.pdf}%\vspace{-5pt}
+	\caption{MusicWeb architecture}\vspace{-10pt}
+	\label{fig:layers}
+\end{figure}
+
 The global MusicBrainz identifiers enable convenient and concise means to disambiguate between potential duplicates or irregularities in metadata across resources, a problem which is all too common in systems relying on named entities. Besides identifiers, the MusicBrainz infrastructure is also used for the search functionality of MusicWeb. However, in order to query any information in DBpedia, the MusicBrainz identifiers need to be associated with a DBpedia resource, which is a different kind of identifier. This mapping is achieved by querying the Sameas.org co-reference service to retrieve the corresponding DBpedia URIs. The caveat in this process is that Sameas does not actually keep track of MusicBrainz artist URIs, however, by substituting the domain for the same artist's URI in the BBC domain\footnote{\url{http://www.bbc.co.uk/music/artists/}}, the service can get around this obstacle. Once the DBpedia artist identity is determined, the service proceeds to construct the majority of the profile, including the biography and most of the linking categories to other artists. The standard categories available include associated artists and artists from the same hometown, while music group membership and artist collaboration links are queried from MusicBrainz. The core of the Semantic Web linking functionality is provided by categories from YAGO. The Spotify\footnote{historically the Echonest} and Last.fm APIs are used for recommendations that are based on different similarity calculations, thus providing recommendations that do not necessarily overlap.
 
 \section{Artist similarity}