You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

CAMARA Population Density Data API - Follow-up meeting #10 - 2024-06-19

June 19th, 2024

Attendees

Name

Company












Population Density Data API minutes: https://wiki.camaraproject.org/display/CAM/Population+Density+Data+API+Minutes

Agenda

  • Approval of previous meeting minutes #9 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#12TelefonicaDiscussion on API algorithm - Initial proposal
Issue#24TelefonicaAPI access mechanism
PR#25TelefonicaDocumentation of API Algorithm
PR#30TelefonicaRC2 version proposal
PR#32TelefonicaRC2 additional merge

Approval of previous meeting minutes & documentation (1)

Meeting Minutes #9

 Approved

API proposal review (2)

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 

After offline and online discussion, decision is taken on:

  • Not modify security schema in the API code, as no different guidance in I&CM group is determined apart from OIDC
  • Include clarification text in API documentation, establishing that the usage of this API is determined by CAMARA rules, in this case 2-leggged as no personal data is treated.

Text to be included as RC2

Issue to be closed when PR30 merged

PR#30 & PR#32

RC2 proposal and additional commits.

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


Continue offline review

AoB (4)

Meta-release process to be started as soon as version is released. Commonalities adoption may be required. 

Process will be started to include 0.1.0 in Meta-release.

Discussion Summary

Issue/PRSummaryAction/Decision
Issue#12Discussion on API algorithm - Initial proposal
Issue#24API access mechanism
PR#25Documentation of API Algorithm
PR#30RC2 version proposal
PR#32RC2 additional merge
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 July 03rd, 2024
  • No labels