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

Re: What about music-related URIs???

From: David Peterson <david@squishyfish.com>
Date: Mon, 07 Sep 2009 14:32:16 +1000
Message-ID: <4AA48CD0.3000708@squishyfish.com>
To: Kingsley Idehen <kidehen@openlinksw.com>
CC: music-ontology-specification-group@googlegroups.com, Linking Open Data <public-lod@w3.org>


On 7/09/2009 5:44 AM, Kingsley Idehen wrote:
> 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.
+1

Now if the HTML 5 mob just saw it that way... ;)  Now that really is the 
topic for another conversation!

I am oh so happy to be hearing this more and more. Embedding RDFa into 
HTML is the way forward for the vast majority of websites. It removes 
the whole complexity of server configs, content negotiation, what is and 
isn't a thing, blah, blah blah.

I worked with the ABC (Australian Broadcasting Corporation) to launch a 
digital radio site built with Drupal. We were faced with what URI to use 
and this conversation will indeed help. I will update the code 
accordingly to musicbrainz.


Cheers,

David
Received on Monday, 7 September 2009 04:33:05 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:23 UTC