The Specification Tracker should have the notion of "Tracks"

this ofcourse applies only to listing all specs enlisted under a specific "Sprint"

So, the tracks are only related to sprints? Or do you want to preserve that information from sprint to sprint? If you consider a sprint to be a conference, then a "track" is a common terminology for a group of related presentations / topics / bofs.

The idea is, that if you go over the registered spec list for a sprint, you should be able to quickly and easily view those that belong to tracks you're more interested in then others. So for instance, going over https://launchpad.net/sprints/uds-paris/+specs I'd like to be able to see (without checking each spec individually) which specs are for Launchpad, Edubuntu, Kubuntu, the Live CD infrastructure (in which case they span more then one ubuntu derivative) , localization, MOTU or even Accessibility. This way it would be easier for people to check out and find specs they want to subscribe. Also, would be easier to locate new specs being registered on the fly while already in a sprint or shortly before (I envisage sub'ing to a track would send me notification about any spec work/changes going on in any of the specs grouped under that track).

It might be that some of this can be handled by being able to sort and group specs by product/distro , still I can think of groups of related presentations / topics / bofs that will be better sorted having both product and track relationship , or groups that will never fall under a product/distro category. (For instance, a "Community Track" grouping all bofs / presentations related to adovcay and recruiting more community people in a conference)

Does that sound sane?

So, in view of my previous post, yes, is seems worthwhile to preserve this information between sprints.