Endpoint names for Metrics

[schnuerle]

Currently we have the two endpoint names under the Metrics API called 'activities' and 'aggregates'.

https://github.com/openmobilityfoundation/curb-data-specification/tree/feature-release-work-1/metrics#endpoints

Are there better names for these? We want to avoid using 'metric' or 'metrics' since these are under the Metrics API already.

These are defined as follows:

Activities

/metrics/activities

Information about an activity that occurs near, at, or within a pre-defined curb area. Activities is a subset of items from the Events API.

Activities are a historic subset of curb events, with some rows combined, some columns removed for clarity and privacy, and for some curb event types. Activities are meant to provide a granular view of activity happening around the curb places, so consumers can do their own analysis and aggregation.

Aggregates

/metrics/aggregates

Aggregated counts and methodology of curb events.

Aggregates are historic pre-computed counts and metrics of Events occuring in curb places, aggregated to the hour.

[schnuerle]

FYI, these endpoints now use the singular noun forms of Activity and Aggregate for consistency across CDS and MDS.

[schnuerle]

I think Activity is good, and Aggregate can work.

Some other options for 'aggregates' could be statistics, measures, counts?