2026-03-25 Population Density Data - Meeting Minutes

@Alberto Ramos Monaga

TEF

@Rafal Artych

DT

PR#104

TEF

Draft until next meta-release: Delete additional text for RFC date time format

• Pending action: Draft → Open issue (we've two approved and a WIP version--> proceed with merging)

#105 & PR#106

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.

• Pending action: Telefónica will propose a PR with the new changes.

#109

Population Density Data Group

Scope for Fall26 (new Sync26) release (in preparation): Please add your proposals in the comments and open issues if needed.

Review or propose a deadline for finalizing the scope:

• Pending action: close the scope for apr 30 M1 (API Sub Projects)

#116

TEF

Add new PopoulationDensityData User Story: Add the Population Density Data user story based on the latest API changes and to follow the stable requirements phasing.

• Pending action: 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.

• Pending action: TEF will implement the changes in the next PR agreed with the discussion

#117

Release Management WG

[bulk] Add release-plan.yaml (2026-02-23-001): This PR adds release-plan.yaml for automated release tracking (replacing manual API Release Tracker pages on wiki).

• Pending action: Review by the group and include the Sync26 fields

#118 & PR#119

TEF

Fix incorrect ATP time-range assertions: This PR fixes incorrect ATP validation steps for time interval coverage in Population Density Data.

• Pending action: Review by the group

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

from Spring26

M1 (API Sub Projects)

apr 30

M3 (API Sub Projects)

jun 15

M4 (API Sub Projects)

sep 30

M5

oct 15

M6

oct 31

 #115

Stable readiness prerequisites — test coverage sufficiency and evidence (tests ↔ behaviours mapping + test result statement)

Proposed outcomes

• Decision: “Current coverage is sufficient” vs “Coverage uplift required”.

• Definition of Done for:

  • Tests ↔ behaviours mapping documentation

  • Test Result Statement (where it lives, what it includes, and who signs it)

Context
These items are intended to unblock the Stable (v1.0) track. This discussion is about test adequacy and documentation/evidence, not about changing the API scope.

• Pending action: Review by the group