DRAFT AGENDA

Date

08 Oct 2024

Attendees & Representation

Community: Jose Luis Urien Pinedo Ludovic Robert Akos Hunyadi Cetin Alpaycetin Huub Appelboom Joachim Dahlgren Rafal Artych Maximilian Laue

Agenda

Antitrust Policy

• Approve previous meeting minutes

  • Approved ? Yes - no comment.

• Open issues and PRs

Minutes

...

• To be considered. Candidate fixes:

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

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

  • Decision: We can wait to have something more relevant to create a new patch as it is cosmetic. Jose Luis Urien Pinedo will create an issue to have a tracking.

New

• Issue [Retrieval] What is the expected behavior when maxAge value is above threshold supported by the operator?

  • Answered by Cetin Alpaycetin

• 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

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

Old

• Support of Multi-SIM lines in DeviceLocation APIs

  • Derived from camaraproject/Commonalities#302

  • 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

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

  • No new comments, discuss during meeting.

• 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.

...

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

  • No new comments

  • From previous meeting: 

    • Some new comments in related issue in Commonalities

    • Not urgent but let's keep an eye on itz

• 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.

AOB

Action items