tag:blogger.com,1999:blog-11697838.post2005157622975356256..comments2009-03-06T13:10:30.233-05:00Jason Herskowitzhttps://profiles.google.com/102843030102775879058noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-11697838.post-3357105018771010572009-03-06T13:10:00.000-05:002009-03-06T13:10:00.000-05:00Granted, I'm still not as knowledgeable about MusicBrainz as I should be. But it seems that it could be a piece of the solution (in terms of having common identifiers), but that requires that every service support MusicBrainz IDs (or mapping to their IDs). I'm not sure that you can't get "good enough" in the near terms just by writing plugins for each service that bounces keywords off of their existing APIs? <BR/><BR/>Then there is also the client-side logic and user preferences that handles "when I click on a song link take me to the resource in X's catalog". For example, I'd love to a consumer of the content be able to specify their priority order of where it tries to get fulfilled from. E.g....<BR/><BR/>1. Local<BR/>2. Remote Access to other machine<BR/>3. Imeem<BR/>4. Rhapsody<BR/>5. 30 sec sample from iTunes, AMG, Muze<BR/>etc...<BR/><BR/>Also, it could be interesting to include an idea of cascading logic for "buy" links as well. Personally, I'd love it if I could<BR/>hit a "buy/get" action and have it first...<BR/><BR/>1. Check eMusic<BR/>2. Check Amazon<BR/>3. Check Amie Street<BR/>4. Check iTunes<BR/><BR/>Perhaps at some point there is even a price comparison feature in<BR/>there.... "just give me the cheapest MP3 provided that it is at least 256kbps".jherskowitzhttp://www.blogger.com/profile/15797190582674008000noreply@blogger.comtag:blogger.com,1999:blog-11697838.post-40032253380027118222009-03-06T13:00:00.000-05:002009-03-06T13:00:00.000-05:00What about MusicBrainz?Dan Kantorhttp://www.blogger.com/profile/18126548834365544408noreply@blogger.com