...
December 18th, 2024
Attendees
Name | Company |
|---|---|
Orange | |
Ericsson | |
DT | |
Telefonica | |
Telefonica |
Population Density Data API minutes: https://lf-camaraproject.atlassian.net/wiki/display/CAM/Population+Density+Data+API+Minutes
...
Approval of previous meeting minutes & documentation (1)
→ Approved
API proposal review (2)
...
Status: Commonalities closed , to alignfor circle and polygon, enough for PDD.
AP: Check if format in commonalities is aligned with current PDD and align if needed
Propose new scope for next release.
...
Issue#40 on area type formar
(new) Issue#50on async response mechanismIssue#51historical information
Issue#61request ID in async response
Issue#62error for async processing
Status: Alpha release of commonalities getting ready, we’ll adapt API accordingly
...
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
Support time window for past time frames, historical data.
...
Include ID in notification to track request-response
Status: move to integer formatcreate PR with this new parameter, aligned with QoD sessionID mechanism
Include error status for callback response if area cannot be processed
Status: move to integer formatAlign with geofencing when processing the are (in that case area subscription), in case this is covered there in the callback (and not only in the post response)
AP: check with geofencing, also around the 400/422 in the sync mechanism
Solving 56 & 58
Status: to be merged by the end of the day
Solving 51
Status: to be reviewed and merged, leaving historical age restriction open for the moment
AoB (4)
Next steps:
Close current PRs to freeze API content
Align commonalities as expected
Release tracker created for 0.2.0, RC to be created before 15/01 (next meeting)
Discussion Summary
# | Summary | Status/conclusion |
|---|---|---|
Area Data-type | ALL to provide feedback into commonalities issueAlign wth commonalities, if changes are required | |
New Release Scope | ALL to provide more proposals | |
Aling with guidelines for async responses | ||
Support time Windows in the past | Review and merge PR60 | |
Easing code parameters and polymorphic formats | Review and merge PR59 | |
Value format (double/integer) for density data | Review and merge PR59 | |
Include ID in notification to track request-response | Align with QoD sessionID and create PR | |
Include error status for callback response if area cannot be processed | Align error with geofencing (if applies) and align 422/400 error as well |
Next steps
Scope for next release → #17
...