2026-07-15 Population Density Data - Meeting Minutes

@Alberto Ramos Monaga

TEF

#105

TEF

Issue (Release Management) - Align asynchronous response with CloudEvents format to ensure compliance with Commonalities r3.3

The asynchronous response in PredictiveConnectivityData and Population Density Data does not comply with Commonalities r3.3 (uses application/json instead of CloudEvents).

Status: An issue (#533) has been created in the commonalities group to address this issue. Once a decision has been made, it will be applied to this issue

Feb 17, 2026: The fix has been uploaded to commonalities: #575. It explains that an asynchronous response is not really an event. And that although it is recommended to use `sink` and `sinkCredential`, the cloudevents model should not be used.

• Status: changes in PR#123 - Review by the group.

#110

Orange

Provide a list of GeoHashes in the API request: Add support for GEOHASHLIST as a new areaType, allowing developers to send a list of geohashes (precision 7) in the request.

Goal: Improve request precision and predict response volume.

Note: This would complement, not replace, the current area definition method.

• Status: changes in PR#123 - Review by the group.

#121

Marketing WG

API Description review finding: a new version of the API description has been generated (Population Density Data API description v2 ) review by the group.

#125

Release Management

This issue is for preparing the release content.

• Pending action: Review with the group next steps

  • PR#128 test(population-density-data): add GEOHASHLIST support and rework time/error model - Review by the group

  • PR#123 New changes in yaml for Sync26 (Geohashlist+Commonalities&ICM) - Review by the group.

#126

Release Management

v0 validation callers disabled in favor of CAMARA Validation

Following the merge of #122 which installed the CAMARA Validation workflow (.github/workflows/camara-validation.yml, pinned to camaraproject/tooling@v1-rc), the legacy v0 validation callers have been disabled by the admin team to avoid duplicate validation runs on every PR. No codeowner action required. The disabled workflow files will be removed as part of a dedicated cleanup campaign at v1 GA.

#127

Marketing WG

Proposal: CAMARA Mobility Analytics APIs Whitepaper: The CAMARA Marketing Working Group has discussed the strong external impact generated by the recently published whitepaper “CAMARA APIs: Functional Differences”, which compared SIM Swap, Device Swap, Tenure, and Number Recycling. Based on that experience, the Marketing Working Group is exploring whether similar whitepapers should be created for other mature areas of the CAMARA API portfolio.

• Decision: [decision]

M1 (Commonalities & ICM)

nov 30

from Spring26

M0

jan 15

kick-off preparation

M2 (Commonalities & ICM)

jan 31 feb 15 feb 19

from Spring26

M4 (Commonalities & ICM)

mar 15 mar 22 apr 15 apr 30 may 19 may 21

from Spring26

M1 (API Sub Projects)

apr 30 may 31

Passed

M3 (API Sub Projects)

jun 15 jun 30 jul 31

impact from Spring26 delay. Release candidates should be prepared as soon as possible. Waiting till jul 31 risks slow processing in august.

M4 (API Sub Projects)

sep 30

M5

oct 15

M6

oct 31

N/A