[ID3 Dev] ID3v1 Genre URI Recommendation

[Daniel Rabus]

Well, maybe my initial posting was a little bit unclear...

The Problem: There is still a need for some standardized mapping from a
genre ID to an URI.

Background: In RDF it's essential to refer to a resource using a URI. So
if I create a RDF description of a MP3 file, like

<rdf:Description>
	<dc:creator>Briskeby</dc:creator>
	<dc:title>Propaganda</dc:title>
	<dc:coverage rdf:resource="xxx"/>
</rdf:Description>

then 'xxx' should point to a URI referring the genre "Pop". If the URI
is resolvable, i.e. an URL, additional human readable information (maybe
a definition) may be accessible. Also additional statements like "Pop is
related to PopRock" will be possible. Let's think about search
engines... :-)

Summary: The ID3 genre ID is a great concept to define the "kind of"
music. Providing an semantically equivalent URI would raise additional
benefits -- and allows proper integration into RDF.

Anyone sharing my thoughts? Comments or suggestions?

Daniel


Mixmaster Slake schrieb:
> Why not use the comment field?
> 
> 
> 

>> ----- Original message -----
>> From: "Daniel Rabus" <drabus at gmx.de>
>> To: id3v2 at id3.org
>> Date: Fri, 09 Dec 2005 16:08:01 +0100
>> Subject: [ID3 Dev] ID3v1 Genre URI Recommendation
>> 
>> Hi,
>> 
>> are there any recommendations to map the existing ID3v1 genres to an 
>> URI? For any upcoming RDF applications this would be very useful. If 
>> there isn't such a standard yet, one way might be to refer to a genre 
>> listing and use the URL fragment as identifier.
>> 
>> For example:
>> http://www.id3.org/id3v1/genres#<genre ID>
>> 
>> Any suggestions or existing solutions?
>> 
>> Thanks,
>> Daniel






---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org