/
Copy of 2025-02-19 Population Density Data - Meeting Minutes

Copy of 2025-02-19 Population Density Data - Meeting Minutes

CAMARA Population Density Dataย APIย - Follow-up meeting #20 - 2025-02-19

February 19th, 2025

Attendees

Name

Company

Name

Company

@Ludovic Robert

Orange

@Rafal Artych

DT

@Sachin kumar

VDF

@Surajj Jaggernath

VDF

@violeta.gonzalezfernandez@telefonica.com

Telefonica

@Jorge Garcia Hospital

Telefonica

ย 

Population Density Dataย APIย minutes:ย https://lf-camaraproject.atlassian.net/wiki/display/CAM/Population+Density+Data+API+Minutes

Agenda

  • Approval of previous meeting minutes #19 and meeting agenda

  • Open issues and PRs

    • Issues: #50 #77

  • Timeline and next steps

  • AoB

Open Issues & PRs

#

Company

Summary

#

Company

Summary

Issue#50

Telefonica

Align with guidelines for async responses

Issue#77

Telefonica

Prepare public release of the API

Approval of previous meeting minutes & documentation (1)

Meeting Minutes #19

โ†’ Approved

APIย proposal review (2)

Issue#50

Include alignment with commonalities for the async response mechanism (and any)

Status: Commonalities closed Analysis+of+Commonalities+0.5.0-alpha.1+changes#Analysis. To start with current alpha1 version and wait for any additional change if needed

AP:

Check callback errors
Check callback async mechanism (as done in 0.1.1 jointly with QoD)
Any other

Issue#77

Prepare public release confirming that:

  • Update support of Commonalities r2.3 and ICM r2.3 (pending commonalities publication)

  • Analize error 429 aligned with other APIs, TBD

  • Maintain 410 as relevant for the callback endpoint

  • Clarify in API test plan that callback endpoint is "an accessible HTTPs endpoint"

  • Validate alignement with Analysis of Commonalities 0.5.0

AoB (4)

Next steps:

Discussion Summary

#

Summary

Status/conclusion

#

Summary

Status/conclusion

Issue#50

Aling with guidelines for async responses

ย 

Issue#77

Prepare public release of the API

Close scope with commonalities alignment

Next steps

  1. Scope for next release โ†’ #21

  • Next call will be TBD

Related content