CAMARA Population Density Data API - Follow-up meeting #8 - 2024-05-22
May 22th, 2024
Attendees
Name | Company |
|---|---|
| Sachin Kumar | Vodafone |
| Gregory Liokumovich | Ericsson |
| Violeta Gonzalez Fernandez | Telefonica |
| Jorge Garcia | Telefonica |
Population Density Data API minutes: https://wiki.camaraproject.org/display/CAM/Population+Density+Data+API+Minutes
Agenda
- Approval of previous meeting minutes #6 #7 and meeting agenda
- Open issues and PRs
- Issues: #12 #14 #23 #24
- PR #25 #26
- Initial algorithm proposal review
- Timeline and next steps
- AoB
Open Issues & PRs
| Issue#12 | Telefonica | Discussion on API algorithm - Initial proposal |
| Issue#14 | Ericsson | Exposed data - Population vs density |
| Issue#23 | Telefonica | API exposed parameters (MAX-MIN-AVG) |
| Issue#24 | Telefonica | API access mechanism |
| PR#25 | Telefonica | Documentation of API Algorithm |
| PR#26 | Telefonica | Solving #14 |
Approval of previous meeting minutes & documentation (1)
→ Approved
API proposal review (2)
...
Ericsson: Response content should follow the expected as in the API name, it is, density instead of population count
...
- Or to change the API name to count
- Or to change the response unit from people/cell to people/km2
Issue to be closed , including proper density value (people/km2) (PR #26). To continue in #23 and discussion for the definitions of the parameters.when PR #14 is merged
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 when new PR is merged
Authentication/security discussion opened around the usage of 2-3 legged access tokens for this API(s).
Solving Issue#15
PR closed
Solves #6 #7 #10 #13 & #15. #20 still open about details, also to be aligned with async/subscription mechanism in commonalities
- 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
SolvingIssue#12
Fixing Issue#14To be merged when closing Issue#20
Initial algorithm proposal (3)
Population Density API - Algorithm.pdf
→ To provide feedback
Question: how to proceed?
PR to be opened for further discussion on documentation.
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.
Clarify the step of removing non-personal devices from the device count, not using M2M reference
AoB (4)
RC to be created as stable issues are closed.
- Meta-release alignment with commonalities to be integrated as soon as they are published.
Scope for a second version to be discussed.
Discussion Summary
| Issue#12 | Discussion on API algorithm - Initial proposal | To clarify it's a reference steps for an algorithm, just as additional documentation in the repo |
| Issue#14 | Exposed data - Population vs density | To be closed when PR #14 is merged |
| Issue#23 | Including redoc and swagger editor link in readme | Issue#24 | Area format alignement
| API response parameters | Proposal to be included in the specification by PR | |
| Issue#24 | Authentication/security | 2-legged auth to be used in this API, to review if it's required to document it in the API |
| PR#25 | Documentation of API Algorithm | To be reviewed offline |
| PR#26 | Solving #14 | To be merged |
| AoB | Discussion on authentication management | (NEW) to be treated offline → Issue#24|
| RC version to be proposed | To propose RC version as soon as issues and current PRs are closed. |
Next steps
- Feedback on algorithm proposal→ Follow-up meeting #
- Close async mechanism #
- Parameter definitions #
- RC API spec agreement → Follow-up meeting #
- Next call will be May 22thJune 05th, 2024