I've put together a page of possible key/encoded-value pairs that would be useful for OpenURL linking to music. The items are taken from those elements in the MusicBrainz metadata namespace, ID3 frames, XSPF playlists and the OpenURL KEVs for books that are useful for identifying a particular piece of music.
Any comments/suggestions?
Comments
All fields are optional, email address will not be shown; no HTML, URLs are automatically hyperlinked.
This looks good so far. What were you planning on using for the rft_val_fmt? I'll try to start working on the implementation that Todd Holbrook and I had proposed to have a working implementation to beat around with.
Although it would never, ever get used, I can see how the other OpenURL Entities would be used, too: ReferringEntity could either be the cover tune ("You are always on my mind" by the Pet Shop Boys being the ReferringEntity for Willie Nelson or Elvis) or something like how Elliott Smith's "Waltz #2 (XO)" refers to "Kathy's Clown" by the Everley Brothers and "You're No Good" by Linda Ronstadt.
Of course, maybe that's getting a little complicated and pointless.
Still, good work! This begins to make OpenURL more useful for the mainstream!
Hi there:
Searching for music is a topic I have been interested in for a while, and it seems like OpenURL 1.0 provides a potentially good soultion to certain issues that arise, especially with classical music. For example, consider the following list of titles:
Mozart's Piano Concerto no. 23
Mozart: Piano Concerto KV488
Mozart - Piano Concert in A major
Konzert fur Klavier A-dur nr. 23
All of these titles refer to the same piece of music, and all are common ways for the title to be written. I have always been a bit frustrated by this situation when searching for classical music, because one has to perform all of these searches in order to find all potential copies of the piece. I would be intereted in seeing some KEV's like the following:
composer=mozart
compositonform=concerto
instrument=piano
key=AM
koeschel=488
number=23
A query of this form submitted to a resolver could locate all possible titles that represent this piece, regarless of their form or language.
Music is in interesting field in which to exercise 1.0's extensibility, just because of the sheer number of metadata that could be important to users. Users may be interested in specific composers, conductors, or performers. They may be searching for sheet music, MP3s, CDs, or video recordings.
What specifically are you trying to develop with your OpenURL music standard? What are the targets that a music resolver could potentially to link to? I think even a front-end to a single resource (like WorldCat) would be very useful if it could make all of the fine-tuned distinctions that music fans would want to make.
At its most basic, I'm trying to make it so that someone could link from a web page to "the version of Daydream Believer performed by The Monkees that's found on the album Greatest Hits, released in 1995" or to "the version of That Man Will Not Hang performed live by Mclusky at ULU, London on 2004-11-26".
Targets include any service that can output either track or playlist downloads, so (at the other end of a possible bridge resolver) this would include sites like iTMS and Mobster.
I have a feeling this will have to be extended to cover any kind of audio, not just 'music', because the boundaries are so vague (field recordings, for example).
Popular music would be a great application for OpenURL. I'm not immediately sure of what the local services would be (perhaps some would emerge), but it would be a handy way of aggregating all the legitimate links for one's favorite band.