user warning: Unknown column 'captcha_type' in 'field list' query: SELECT module, captcha_type FROM captcha_points WHERE form_id = 'user_login_block' in /var/www/drupal/sites/all/modules/captcha/ on line 64.

Project Plan Post 4 of 7: IPR (Creative Commons Use & Open Source Software License)

The MusicBrainz database contains two types of information. The core data, consisting of factual data such as the names of albums, tracks and artists, is in the public domain. The remaining data, such as annotations, tags, opinions and ratings are protected by the Creative Commons Attribution-NonCommercial-ShareAlike 2.0 licence, which allows non-commercial use of the data under the conditions that MusicBrainz is given credit and that any derivative works are also made available under the same licence. Thus the linked data published by this project will follow the same licence arrangement. In particular, this allows the outputs of the project to be used freely in teaching and research.

Project Plan Post 3 of 7: Risk Analysis and Success Plan

The success of the project can be measured in immediate terms by semantic web traffic: the number of web site hits with an "Accept RDF" header, or the number of distinct users connecting to the SPARQL endpoint. In the longer term, the use of MusicBrainz URIs in third party tools and services,
and eventually new studies (enabled by being able to query the linked data) will also indicate the success of the project.

We have identified a number of risks, which are listed with mitigation actions:

1) The MusicBrainz user community votes against the proposed changes
(Likelihood: Low; Impact: Medium)

Project Plan Post 2 of 7: Wider Benefits to Sector & Achievements for Host Institution

In making music metadata available on the semantic web, we are addressing the needs of two primary types of user in the HE sector: (i) those working in the Music Informatics (or Music Information Retrieval) community, primarily in computing and engineering departments; and (ii) musicologists and musicians working in music departments. This is in addition to the (sizable) international MusicBrainz user community, who also stand to benefit from the linking of their data to other semantic web resources, as well as software developers working with on-line music services, and their users, who will indirectly benefit from this project.

Project Plan Post 1 of 7: Aims, Objectives and Final Output(s) of the project

The MusicBrainz user community has created a metadatabase describing over 9 million musical recordings, which is used by media players and web services such as the BBC's /music. The data is structured but not linked. Part of this data has been made available on the semantic web in the past, but it lacks recent extensions and updates, as it was not based on a sustainable model. With the release of MusicBrainz' Next Generation Schema (June 2010, beta 2), it is an appropriate time to map the new metadata to RDF and publish the Linked Data directly from the MusicBrainz website. This data will be linked to music metadata on the semantic web (e.g. DBpedia, BBC), and exposed via a SPARQL endpoint. We will engage with end users in the Music and Music Informatics fields, providing tutorial materials and workshops to encourage uptake of project outputs. We will investigate and report on major issues arising in the project, such as scalability, provenance and sustainability.

NGS to RDF mappings proposals page

We are starting a wiki page to collect proposals for mappings of NGS to RDF. A set of proposed entity mappings is already there. Comments and other ideas are most welcome!

Syndicate content