[Eric: This is from a list discussing how to add classification to the Comprehensive Perl Archive Network] On Thu, Jul 27, 2000 at 01:28:26AM -0400, Adam Turoff wrote: > On Thu, Jul 27, 2000 at 12:46:13PM +0900, Simon Cozens wrote: > > > People looking at OSD should probably also look at what metadata other > > > packaging systems (rpm, deb, pkgadd, ...) define and use. > > > > While we're at it, I'll throw in Trove: > > http://www.tuxedo.org/~esr/trove/ > > I don't think Trove was ever implemented, or ever will be. The ideas > discussed in Trove have manifest themselves in sourceforge though. I think it's a little stronger than that: trove-dev doesn't tell me much but I believe that Sourceforge is using trove itself. I registered a project on Sourceforge today, and that wants me to provide a trove classification, so it looks like they're certainly keeping a trove database of some sort. Trove *is* alive. The trick is how to ensure that we don't end up with a bunch of separate databases, and I'm not sure how we're supposed to avoid that. If we go the trove route (and, yes, I acknowledge completely this is totally undecided, but I'd like to very strongly suggest it) I don't know whether we'd be adding things from our database to Sourceforge's, or if there's a metaindex. Trove does certainly contain all the metadata elements we're likely to need, by design, and when apps.perlhacker (http://perlhacker.org/perlhacker.html) actually happens, I'm planning to use trove classification in that. It's an option for CPAN, but not one that I'm prepared to pretend I fully understand right now. Simon -- Also note that i knew _far_ more about the people that call address mungers names like 'lusers', 'egoists' or try to make luser giraffes. -- Megahal (trained on asr), 1998-11-06
