Tracking Core Component use

[David RR Webber - XMLGlobal <Gnosis_@compuserve.com>]

Team,

I'd like some help and thoughts here.

In the course of the core component work I'm doing 
someone said 'of course the Registry can tell us which
core components and varients are most often used,
and that will help people choose the right ones when
starting something new'.

This is an intriguing idea.  Sorta like those download
counts from shareware.com - but in our case it 
needs to be probably when a machine API requests
the definition of a core component, and then given
the vaguaries of the internet - coupled to something
like the capabilities of a tool like Webalizer to show
some demographics.  Otherwise Ford accessing
just one core component a million times could 
distort the numbers.

I'm not sure we have anything in the current design 
of Registry that would allow us to support this 
'most popular core components' need?

Could we hook some of the existing pieces - like
audit trail, and the API, and a Webalizer tracking 
thru the webserver - together to deliver here?  Also - we
need to drilldown into the goals and requirement 
a bit more.  So long as we can offer up a selection 
of statistical data points - we can allow solution 
providers to tee these up to answer questions 
as needed.   That saves us having to get into 
the reporting side of this - we can leave that
open-ended.

Thanks, DW.