/
[draft] 2024-06-05 Population Density Data - Meeting Minutes

[draft] 2024-06-05 Population Density Data - Meeting Minutes

Jun 05, 2024

CAMARA Population Density Data API - Follow-up meeting #9 - 2024-06-05

June 05th, 2024

Attendees

Name

Company

Name

Company

 

 

 

 

 

 

 

 

 

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

Agenda

  • Approval of previous meeting minutes #8 and meeting agenda

  • Open issues and PRs

    • Issues: #12 #23 #24

    • PR #25 #27

  • Initial algorithm proposal review

  • Timeline and next steps

  • AoB

Open Issues & PRs

 

 

 

 

 

 

Issue#12

Telefonica

Discussion on API algorithm - Initial proposal

Issue#23

Telefonica

API exposed parameters (MAX-MIN-AVG)

Issue#24

Telefonica

API access mechanism

PR#25

Telefonica

Documentation of API Algorithm

PR#27

Telefonica

RC version proposal

Approval of previous meeting minutes & documentation (1)

Meeting Minutes #8

→ 

API proposal review (2)

Issue#23

Definition of API response parameters, to be reviewed

To include definitions proposed by Gregory: 

  • use "pplDensity" - for predicted population density in a grid cell

  • use "minPplDensity" - for minimal predicted population density in a grid cell

  • use "maxPplDensity" - for maximal predicted population density in a grid cell

Issue to be closed

Issue#24

Authentication/security discussion opened around the usage of 2-3 legged access tokens for this API(s).

  • API, as not including personal data (anonymized), is to be considered as a 2-legged access token.

  • To review if API specification needs to be modified accordingly @Ludovic Robert 

Issue to be closed when clarified

PR#25

Solving Issue#12

 

PR#27

Proposing Release Candidate version (scope freezed).

Only dependant on issue #24 discussions to become stable, any other topic to be fixed before?

Initial algorithm proposal (3)

Issue#12

→ To provide feedback

Question: how to proceed?

To document that this is just a proposal of algorithm steps that can be considered as reference. It is included in API supporting documents, not binding. → done

Clarify the step of removing non-personal devices from the device count, not using M2M reference → done

AoB (4)

Scope for second version to be discussed, including also meta-release alignment.

ATPs, user stories...

Discussion Summary

 

 

 

 

 

 

Issue#12

Discussion on API algorithm - Initial proposal

 

Issue#23

API response parameters

 

Issue#24

Authentication/security

 

PR#25

Documentation of API Algorithm

 

PR#27

RC version proposal

 

AoB

 

 

Next steps

  1. Feedback on algorithm proposal→ Follow-up meeting #

  2. Close async mechanism #

  3. Parameter definitions #

  4. RC API spec agreement → Follow-up meeting #

  • Next call will be June 19th, 2024