History:Linking FAQ
From MusicBrainz Wiki
[edit] Linking FAQ
This page NeedsEditing and will eventually become a CandidateForDeletion. -- WolfSong 15:03, 11 June 2006 (UTC)
Q. What URI should I use to link to a MusicBrainz resource?
A. (as of 2003-12-17) URI such as http://www.musicbrainz.org/artist/eeb1195b-f213-4ce1-b28c-8565211f8e43
Q. How do I link to MusicBrainz HTML data?
A. (as of 2003-12-17) URI such as http://www.musicbrainz.org/artist/eeb1195b-f213-4ce1-b28c-8565211f8e43
(as of 2004-01-05) URI such as http://www.musicbrainz.org/artist/eeb1195b-f213-4ce1-b28c-8565211f8e43.html
Q. How do I link to MusicBrainz RDF data?
A. (as of 2003-12-17) URI such as http://mm.musicbrainz.org/mm-2.1/artist/eeb1195b-f213-4ce1-b28c-8565211f8e43
(as of 2004-01-05) URI such as http://musicbrainz.org/artist/eeb1195b-f213-4ce1-b28c-8565211f8e43 will also work. This does content negotiation so may return HTML depending on your user agent. You can also add a depth parameter such as /4 to the URI to get back more RDF details.
[edit] Comments
The RDF linking method looks fragile with respect to the mm-2.1 part changing in the future. This may be good for getting the RDF in a specific schema format though. Other possibilities for long term permanent URIs include:
- http://mm.musicbrainz.org/artist/GUID
- would require mirrors to have multiple hosts for content types
- http://*.musicbrainz.org/artist/GUID.rdf
- explicit type by extension or path component
- hostname independent
- could auto-negotiate HTML (.html), XML (.xml), PDF (.pdf), etc when extension not present (see http://norman.walsh.name/ as an example)
- explicity request /artist/GUID.rdf? auto-neg perhaps not entirely appropriate when getting the RDF metadata about that resource?
- ???
Added feature request for fuzzy linking / RDF. See NewFeatureSuggestions -- DanielOconnor
