Resuming the interesting discussion of cross tabs here: A new opportunity for cross-tabulations within Tinderbox
Question: We could imagine wanting crosstabs for many kinds of attributes. Strings and numbers, certainly, but also sets. Perhaps for dates, too. Each of these requires different infrastructure. Which have the greatest priority? For which do people have immediate need?
Question: Consider a numeric attribute, $OvenWidth, which specifies the external width of various ovens. Ovens come in discrete widths — 24", 36", 48" and 60" — and so even a large collection will have only a few values. We’d want a cross tabs row for each value.
On the other hand, $Latitude varies continuously; we’d want to sort our latitudes into ranges. How many “bins” do we want? (Yes, we could make it a preference, but it’s good to know how to decide!)