Page Comparison

DRAFT AGENDA

Date

10 Dec 2024

Attendees & Representation

...

• Scope for Spring25 release (in preparation)

  • Place holder to be linked to the API trackers, it must be completed. We may open one issue per API instead

  • Created API trackers for the current 3 APIs, but next versions tbd

• Define guidelines for geofencing implementation

  • New comment by Maximilian Laue

  • From previous meeting: Should be part of the discussion for next version. → Added label “Spring 25”

  • Ludovic Robert is working on this topic within Orange.

• Error Alignement with Commonalities

  • To be discussed:
    Error code 500 & 503 could be removed but we need a decision for all 3 APIs for consistency
    Error code 429 could be removed for GET & DELETE subscriptions in Geofencing

• Update info.description with commonalities

  • Is the update required for Geofencing?

Previous topics

• Update location-retrieval with add maxSurface management

  • Ready but we will wait before to merge to avoid collision with Meta release patch

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

  • No further interaction

  • Close?

• Discuss data minimization for geofencing event

  • Following issue camaraproject/Commonalities#295

  • Review status

• Location subscription API

  • discussed:

    • Should be proposed first to API Backlog Working Group

    • Any supporters? As of now no.

  • Move to backlog? on hold?

• Support of Multi-SIM lines in DeviceLocation APIs

  • Derived from camaraproject/Commonalities#302

    • Some new comments but no conclusions 

  • Discussion during previous 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

  • QoD has decided to add a mention in description: https://github.com/camaraproject/QualityOnDemand/pull/378

...

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

...

• API enhancement - Support of landlines

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

  • We keep for feature for future consideration

AOB

Action items

Next meeting