CAMARA Population Density Data API - Follow-up meeting #11 - 2024-07-17
July 17th, 2024
Attendees
Name | Company |
|---|---|
| Gregory Lindner | Ericsson |
| Rafal Artych | DT |
| Sachin Kumar | Vodafone |
| Jorge Garcia | Telefonica |
Population Density Data API minutes: https://wikilf-camaraproject.camaraprojectatlassian.orgnet/wiki/display/CAM/Population+Density+Data+API+Minutes
Agenda
- Approval of previous meeting minutes #9 and meeting agenda
- Open issues and PRs
- Issues: #12 #24
- PR #25 #30 #32
- Initial algorithm proposal review
- Timeline and next steps
- AoB
Open Issues & PRs
| Issue#12 | Telefonica | Discussion on API algorithm - Initial proposal |
| Issue#35 | Telefonica | Readiness checklist |
| Issue#37 | Telefonica | Basic API Test Cases |
| Issue#38 | Telefonica | API Code commonalities validation |
| Issue#39 | Telefonica | API documentation |
| Issue#40 | Ericsson | Area Data-type |
| PR#25 | Telefonica | Documentation of API Algorithm |
| PR#36 | Telefonica |
| Create API readiness checklist |
Approval of previous meeting minutes & documentation (1)
→ Approved
API proposal review (2)
Include the checklist for meta-release Fall24, including documentation, ATPs and alignment with commonalities (0.4.0)
Item splitted into the following issues to track each item. To include proper scope for meta-relase.
AP: define properly the exact scope referencing the different issues.
Include basic ATP for the population-density-data API, including base test-plan and related documentation
AP: Telefonica to provide first proposal
- Confirm API definition → Current version confirmed
- Design guidelines from Commonalities applied (TBC)
- Guidelines from ICM applied (TBC)
AP: Rafal to validate the compliance of current code with the commonalities and I&CM v0.4.0
- API versioning convention applied → done
- API documentation → validate current documentation and (optionally) finalize the review of the algorithm description
AP: Gregory to review and validare current documentation.
Issue opened in commonalities for the alignment on how to define the area types along all the APIs in CAMARA.
AP: provide direct feedback on the commonalities issue Issue #242. Groups is ok to create a homogeneous definition of the area types, as long as each API can later select granularly which types apply (and not getting obligation to support all the types, or getting involved in a complex data model).
Initial algorithm proposal (3)
K-anonimization to be clarified (in which step it is implemented)
When and how the prediction of persons/users is done, based on the input (devices)
Continue offline reviewTelefonica to provide feedback on these two topics to move on.
AoB (4)
Next steps:
- Group Break → maintain meeting on 31st July, cancel meeting on 14th August, coming back on 28th of August.
Discussion Summary
...
| Issue#12 | Discussion on API algorithm - Initial proposal | To continue offline, Telefonica to provide feedback |
| Issue#35 | Readiness checklist | To include proper scope for meta-release |
| Issue#37 | Basic API Test Cases | Telefonica to provide first proposal |
| Issue#38 | API Code commonalities validation | Rafal (DT) to validate the compliance of current code with the commonalities and I&CM v0.4.0 |
| Issue#39 | API documentation | Gregory (E//) to review and validate current documentation. |
| Issue#40 | Area Data-type | ALL to provide feedback into commonalities issue |
Next steps
- Feedback on algorithm proposal→ Follow-up meeting #
- Close async mechanism #
- Parameter definitions #
- RC API spec agreement → Follow-up meeting ##12
- Align Meta-release items → #12
- Next call will be TBD31st July