Date

Nov 19, 2024

Attendees & Representation

Community: @Cetin Alpaycetin @Ludovic Robert @Javier Carro @Joachim Dahlgren @Rafal Artych @Akos Hunyadi @Ola Ajibola @Jose Luis Urien Pinedo

Agenda

Antitrust Policy

• Approve previous meeting minutes

  • Approved ? Yes approved

• Open issues and PRs

Minutes

Release patch r1.3

• Issue created to have a tracking: Scope for potential patch r1.3

  • Issue:Update errormessage for unsupported device identifieres Small typo in GENERIC_422_UNSUPPORTED_DEVICE_IDENTIFIERS - example, PR: Update errormessage for unsupported device identifieres

    • Still needed: Update servers URL to /vwip

  • Fix links for geofencing-subscriptions in README, add links also to Changelog

  • [geofencing-subscriptions]: MultieventSubscriptionNotSupported instead of PermissionDenied.

    • PR: Correct the example for sub - initialEvent and error MULTIEVENT_SUBSCRIPTION_NOT_SUPPORTED and some typos.

    • Comment by @Cetin Alpaycetin in issue: Instead of "not managed", we could say "not supported"

      • In commonalities we use "not managed" in the event-subscription-template.yaml

    • Still needed: Update servers URL to /vwip

  • Discussed: We can wait a couple of weeks more before to close this patch r.3 (end of this month for example) and then we start with the new release.

New topics

• [Retrieval] Unable to build Location object for /retrieve response

  • Problem with code generator

  • Recently answered

• Discuss data minimization for geofencing event

  • Following issue camaraproject/Commonalities#295

  • Review status

• API enhancement - Support of landlines

  • To be discussed during meeting

    • This is not a short/medium term requirement for Telefonica - no prioritized for other company.

    • We keep for feature for future consideration

      • add a new ‘backlog’ label

• Location subscription API

  • discussed:

    • Should be proposed first to API Backlog Working Group

    • Any supporters? As of now no.

Old

• Update location-retrieval with add maxSurface management

  • After issue How to understand the response parameter area in the device retrieval API

  • Review and comment

    • Add a note in the yaml for the minimum → Pending @Ludovic Robert ?

      • Note has been added in the yaml

    • We will wait before to merge to avoid collision with Meta release patch

• Support of Multi-SIM lines in DeviceLocation APIs

  • Derived from camaraproject/Commonalities#302

    • Some new comments but no conclusions

  • Device Location APIs are specially problematic as location is linked to a physical device, not to a phone number 

  • Discussion during last meeting:

    • The issue has a technical aspect  but it is more important for Product Management.

    • For Location-verification probably we can consider that if any device is in 'the zone' then the result will be true. Perhaps same for geofencing.

    • For location-retrieval the issue is more critical as sending back an array of location is probably not a good solution

    • We need to think about UC in particular as location retrieval is probably used for non-personal device (for sensitive reason) so is there really a requirement for multi-sim for this API?

    • Action for each company to work with product team to refine the requirement

• The issue to improve Geofencing with LOOSE, MODERATE, STRICT 'flavor' is still open #133

  • From previous meeting: Should be part of the discussion for next version.

  • @Ludovic Robert is working on this topic within Orange.

  • Issue still relevant

  • No progress

Waiting for commonalities

• Add an “Area” data-type into CAMARA_common.yaml

  • No new comments

  • From previous meeting: 

    • related issue in Commonalities

    • New PR in Commonalities: https://github.com/camaraproject/Commonalities/pull/315

      • Pending to be merged

• Evolution of subscription guidelines that may affect geofencing-subscriptions:

  • Resource-based subscription – GET /subscriptions using a 3-legged access token

  • Resource-based subscription – guidelines for expiration time set by API operator policy

  • @Ludovic Robert is working on a global PR for commonalities.

    • Any update?

      • Action: @Ludovic Robert will create an issue to discuss data minimization for the geofencing

      • Request to the team to track progress & comment here (WIP) Subscription & events for Commonalities 0.5.0 by bigludo7 · Pull Request #313 · camaraproject/Commonalities (github.com)

AOB

• No meeting Dec 3, 2024 but we add an additional meeting Dec 10, 2024

  • We will decide if we have a meeting Dec 17, 2024

Action items

Next meeting