[ID3 Dev] ID3v1 Genre URI Recommendation

[Daniel Rabus]

Hi Mitchell,

I think you're right: By maintaining a controlled vocabulary it's almost
impossible to cover all genres. On the other side, if everyone creates
new (sub) genres this new values are in danger to become meaningless.
Especially if they are not related to the base genres (including the
winamp extensions).

>> From the Content Type (TCON) frame description in the standards...
>
> "You may use one or several of the types as ID3v1.1 did or, since the
> category list would be impossible to maintain with accurate and up to
> date categories, define your own."

So, according to my understanding, wouldn't it be better to suggest
something like

"You should use at least one of the ID3v1.1 types best matching your
intended genre. Additionally, you may add your own definition. ..."

This way there is no need to change the base values, new genres are in
relation to the existing definitions and therefore providing a kind of
"safe fallback" mechanism: If a user defined genre is somewhat strange
and exotic there is still a way to get a clue by looking on the related
values. (Rating the relations might be another improvement)

Just my thoughts.

Daniel


Mitchell S. Honnert wrote:
> Daniel, as far as I understand it, the ID3 standard is getting away from 
> a predefined set of genres values.  There is an appendix of the v1 
> standard genre values in the v2.3 standard, but the v2.3 standard allows 
> for a free-form genre value, so the "support" for defined genres seems 
> to be tangential at best.
> 
>> From the Content Type (TCON) frame description in the standards...
> 
> "You may use one or several of the types as ID3v1.1 did or, since the 
> category list would be impossible to maintain with accurate and up to 
> date categories, define your own."
> 
> My take on this is that genres are so subjective and ever-changing, that 
> maintaining a master list be a fruitless and never-ending effort.  
> Because of this, I think your idea of adding Genre support is going to 
> be a tough sell.  I can only speak for myself, but it just seems to run 
> in the opposite direction of the ID3 standard.
> 
> - Mitchell S. Honnert
> 
> 
> ----- Original Message ----- From: "Daniel Rabus" <drabus at gmx.de>
> To: <id3v2 at id3.org>
> Sent: Tuesday, December 13, 2005 8:11 AM
> Subject: Re: [ID3 Dev] ID3v1 Genre URI Recommendation
> 
> 
>> 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
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
> For additional commands, e-mail: id3v2-help at id3.org
> 
> 



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