Summary
Following the discussion in TSC, the understanding is that each Sub Project can decide whether and when to pick up possible whitepaper-related topics, with the current priority remaining Sync26.
Based on that, I am opening this issue to check whether the involved repositories see value in a future API-consumer-facing whitepaper explaining the functional differences between aggregated area-level insight APIs.
Possible scope:
- Population Density Data
- Region Device Count
The goal would be to help API consumers understand what questions each API answers and how they differ functionally. You can see an example here from a recent CAMARA whitepaper: CAMARA APIs: Functional Differences
Request
This issue is only intended to confirm whether the topic and scope make sense from the perspective of the involved technical repositories. No immediate drafting, review, API change, semantic change, or Sync26-related action is expected from maintainers. If the involved groups see value in the topic, it can be picked up after the current release priorities, at the pace decided by the relevant repositories.
Initial positioning
These APIs focus on aggregated, area-level insights and should be considered separately from device-specific Location APIs. In summary:
- Population Density Data provides estimated population density for a given area and time interval.
- Region Device Count provides the number of devices present in a given area during a specified time interval, potentially with filtering criteria.
The proposed scope is limited to explaining the functional differences between these aggregated APIs. Device-specific Location APIs (such as Location Retrieval, Location Verification, Geofencing Subscriptions, or Most Frequent Location) are not part of the initial scope. Predictive Connectivity Data may be referenced as a related API but is not currently proposed for inclusion.
Questions
- Do the involved repositories see value in this topic from an API-consumer perspective?
- Is the proposed scope correct?
- Should any API be added or explicitly excluded?
- Are there key semantic, privacy, aggregation, or granularity considerations that should be captured if this topic is eventually drafted?
- Should Population Density Data and Region Device Count be treated together, or would it be clearer to keep them separate?
- Which repository should be used as the main coordination point, if the topic moves forward?
CC: @camaraproject/population-density-data_codeowners, @camaraproject/population-density-data_maintainers, @camaraproject/region-device-count_codeowners, @camaraproject/region-device-count_maintainers, @camaraproject/marketing_codeowners, @camaraproject/marketing_maintainers
Summary
Following the discussion in TSC, the understanding is that each Sub Project can decide whether and when to pick up possible whitepaper-related topics, with the current priority remaining Sync26.
Based on that, I am opening this issue to check whether the involved repositories see value in a future API-consumer-facing whitepaper explaining the functional differences between aggregated area-level insight APIs.
Possible scope:
The goal would be to help API consumers understand what questions each API answers and how they differ functionally. You can see an example here from a recent CAMARA whitepaper: CAMARA APIs: Functional Differences
Request
This issue is only intended to confirm whether the topic and scope make sense from the perspective of the involved technical repositories. No immediate drafting, review, API change, semantic change, or Sync26-related action is expected from maintainers. If the involved groups see value in the topic, it can be picked up after the current release priorities, at the pace decided by the relevant repositories.
Initial positioning
These APIs focus on aggregated, area-level insights and should be considered separately from device-specific Location APIs. In summary:
The proposed scope is limited to explaining the functional differences between these aggregated APIs. Device-specific Location APIs (such as Location Retrieval, Location Verification, Geofencing Subscriptions, or Most Frequent Location) are not part of the initial scope. Predictive Connectivity Data may be referenced as a related API but is not currently proposed for inclusion.
Questions
CC: @camaraproject/population-density-data_codeowners, @camaraproject/population-density-data_maintainers, @camaraproject/region-device-count_codeowners, @camaraproject/region-device-count_maintainers, @camaraproject/marketing_codeowners, @camaraproject/marketing_maintainers