Categories

Paul Quinn (paul nospam at quinnware.com)
Tue, 9 Mar 1999 19:30:29 -0500

This is a multi-part message in MIME format.

------=_NextPart_000_00BE_01BE6A63.4A21FAC0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On the current topic of Categories and category granularity, CDDB =
has it all wrong. It's current 'official' categories are horribly =
unrepresentative of what is in its database. 50% of the entries are =
under 'Rock' alone. A new category system would have to either more =
granular or much more dynamic. Here's an idea just from the top of my =
head. Each entry has two categories, the main category from the official =
list, and a secondary category that is set by submitters indicating a =
more appropriate category if need be. The database would over time tally =
these secondary categories and determine whether a new official category =
should be generated. Bien?

-Paul=20
=20

------=_NextPart_000_00BE_01BE6A63.4A21FAC0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">

    On the current topic of = Categories and=20 category granularity, CDDB has it all wrong. It's current 'official' = categories=20 are horribly unrepresentative of what is in its database. 50% of the = entries are=20 under 'Rock' alone. A new category system would have to either more = granular or=20 much more dynamic. Here's an idea just from the top of my head. Each = entry has=20 two categories, the main category from the official list, and a = secondary=20 category that is set by submitters indicating a more appropriate = category if=20 need be. The database would over time tally these secondary categories = and=20 determine whether a new official category should be generated.=20 Bien?
 
-Paul
   
------=_NextPart_000_00BE_01BE6A63.4A21FAC0--