(1) Approach 1:
Only admin can have global telemetry definitions. I assume no one wants to make "testtelemetryuser" admin. I can change telemetry implementation so that everyone can define global definitions, but is that a good thing?
Thanks, I forgot about that constraint on 'global'. I don't think it's a good thing to let everyone create global definitions. Looks like Approach 2 might be better in this respect.
(2) Approach 2:
Reducers come from different modules. Different configurations may have different set of (or even 0) reducers available. How can we guarantee that the downloadable definition file always uses reducers available? Do we assume that people always download Hackystat-UH configuration, or a superset of it?
Another excellent point, and fortunately I think this is easier to deal with. The goal of course is to simply provide some examples to get new people started and so they're not presented with a blank screen, telemetry-wise. We could, for example, provide some documentation with the XML file that says, "This set of telemetry definitions requires the reduction functions defined in modules X, Y, and Z." It might be reasonable to restrict our example telemetry definition file to providing definitions based upon just the reduction functions in hackyStdExt and hackyTelemetry, since those are fairly basic modules that would be in most configurations with telemetry.
Cheers, Philip
