W3C home > Mailing lists > Public > public-lod@w3.org > September 2009

Re: What about music-related URIs???

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Sun, 06 Sep 2009 15:44:53 -0400
Message-ID: <4AA41135.6030902@openlinksw.com>
To: music-ontology-specification-group@googlegroups.com
CC: Linking Open Data <public-lod@w3.org>
Dan Brickley wrote:
> On Sun, Sep 6, 2009 at 6:01 PM, Yves Raimond<yves.raimond@gmail.com> wrote:
>> I guess it will be as soon as we actually send them a  patch :-) I did
>> some work on that last year (just rdf/xml) but as nick said, the
>> codebase has been changing very fast since then... We should gather
>> efforts  once the big scary release is out and make it happen!
> It would be great to have the core music-brainz derrived music URIs
> hosted on a *.musicbrainz.org domain, even if initially it served as a
> redirector / mirror / cache for materials elsewhere. MB deserves to be
> the hub here I think, and changing all those URIs in a couple of years
> will be quite tricky... maybe some DNS based delegation is the way to
> go in the short term?
> cheers,
> Dan
> ps. i am just running MusicBrainz Picard tagger over all my mp3s
> (includes all the CDs I ever bought...). ... Is there a tool /
> workflow people here can recommend to turn all that into RDF locally?
> does picard keep a db somewhere, or all metadata is just within the
> files?
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups "Music Ontology Specification Group" group.
> To post to this group, send email to music-ontology-specification-group@googlegroups.com
> To unsubscribe from this group, send email to music-ontology-specification-group+unsubscribe@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/music-ontology-specification-group?hl=en
> -~----------~----~----~----~------~----~------~--~---

Using the native MBZ URIs within the MBZ domain is the way forward. 
Naturally, the pages should also include RDFa and then they won't need 
to redirect anything. Basically, stick with HTML+RDFa as the default 
metadata representation served up from data space: musicbrainz.org . It 
is going to be much easier for User Agents to become RDFa aware than it 
would ever be for Web publishers to globally implement Content 
Negotiation based Identity dissambiguation.  Of course, this doesn't 
invalidate the deep utility of Content Negotiation -- in general --  it 
simply means that its relationship to Linked Data Web boostrap 
(activation threshold reduction) is inverse in nature :-)

You must be able to publish rich metadata in text form without 
possessing Web Server admin privileges, bottom line.

MBZ could be another powerful boostrap point for the Web of Linked Data.



Kingsley Idehen	      Weblog: http://www.openlinksw.com/blog/~kidehen
President & CEO 
OpenLink Software     Web: http://www.openlinksw.com
Received on Sunday, 6 September 2009 19:45:29 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:15:59 UTC