Page Comparison

...

...

...

...

...

...

...

...

...

...

...

Date

07 May 2024

Attendees & Representation

...

• Meta-release Fall-24 - timeplan updated
  • https://wikilf-camaraproject.camaraprojectatlassian.orgnet/wiki/display/CAM/Meta-release+Fall24
  • Expected Deliverables 
    • M0 - approved, but communication delayed (expected begin of next week)
    • M1 - 30/04
      • Scope of Commonalities finalised: 
      • Scope of ICM in work, focus on OIDC profile
      • The release process definition expects here already an alpha release of Comm & ICM, but they will come only later, at latest 2 weeks before the release candidates (for review by API Sub Projects)
    • M2 - 15/06
      • (Release candidate of Commonalities + ICM)
    • M3 - 15/06
      • First release candidate of DeviceLocation, starting of test implementations
    • M4 - 31/08
      • Last (stable) release candidate of target release from DeviceLocation
      • Release Criteria fulfilled (incl validation of the release candidate by two independent implementation of the API)
    • M5 - 15/09
      • public release done

...

• • Issue in Commonalities to discuss Enhancement of the Testing Guidelines by TEF
    •  Jose from TEF will upload an example of Location Verification ATP once the commonalities guidelines are approved 
      • May be updated as discussions progress
    •  Toyeeb to check with GSMA conformance → Update?
    •  Orange is working on the testing too and will provide feedback soon. → Update? 
  • Dedicated workshop in Commonalities scheduled for May 16th

• @joAPIs APIs error alignment

  • Rafal Artych has prepared a confluence page with Http Errors in different APIs and a comparision with the CAMARA_common.yaml to check differences and misalignments so we can adapt the guidelines: Error response guidelines
  • Regarding this topic Fernando Prado Cabrillo created a PR to fix some of this misalignments: https://github.com/camaraproject/Commonalities/pull/174
  • (Meeting Action) : Chapter 6 of the Commonalities design document need to be review. Jose Luis Urien Pinedo will check with Pedro Diez Garcia for that.

Waiting for Commonalities outcome, still open there

...

• Are we happy with security scope for geofencing
  • Scope name should reflect the data provided by the notification (not geofencing:subscriptions:write but more precise like geofencing:subscriptions:read-location )
  • Discussion on this topic in progress in Commonalities (camaraproject/Commonalities#163)
  • Open pull request in Commonalities update-design-doc-with-explicit-sub-scope-changes by shilpa-padgaonkar · Pull Request #177 · camaraproject/Commonalities (github.com)
    • Proposal is to add scope per even-type additionally to scope managing the right to create a subscription.
  • (Meeting Action): Ludovic Robert will create an issue.

• Geofencing - Adding a value in Termination Reason value enum

  • Discussion in progress in Commonalities: camaraproject/Commonalities#153
  • Related issues in DeviceStatus and QoD
  • Still open

• Subscription related issues → Proposal in TSC to setup a dedicated workshop

  • Geofencing API - Add Subscription type 'area-left-or-entered' to subscribe to both event in one time

    • Issue in Commonalities Subscription-Issue2: Allow event consumers to subscribe to more than one event types with a single subscription
  • Geofencing API - Defining a standard behavior for first event
    • Issue in Commonalities Issue 140
  • Proposal to tackle open subscription issues Common proposal to tackle subscription-based open issues. · Issue #185 · camaraproject/Commonalities (github.com) - mains points:
    • Align our subscription model with CloudsEvents subscriptions one
    • Introduce a status attribute in the template as we have fair UCs that can leverage this (Retrieve expired subscriptions for monitoring, deactivate a subscription if an user revoked her/his consent, etc...). API subproject could decide to use it or not.
    • Improve the model to allow consumers to subscribe to more than one event types with a single subscription but at least for the first meta-release we enforce to have only event type per subscription. After this first meta release decision to handle several event types in one subscription request should be discussed at API sub projet level
    • Add filters and it's up to API Project to use it. We recommend to be very cautious as it add complexity so it should be keep for very relevant UC.
    • Add initialEvent in config as well to manage request to get event when current situation of a device corresponds to the subscriptions type. .
  • A template yaml is available for review here: Create subscription-notification-template.yaml by bigludo7 · Pull Request #189 · camaraproject/Commonalities (github.com)

...

• Issue #83, with formal requirements from GSMA Product track
  • Document uploaded by TEF with a proposal.
  • Review priority and next steps → Clarify this:
    • More generally probably we need to have feedback loop with GSMA team about API work (and review the priority as focus could change)
      • Done during last TSC - see here: https://wikilf-camaraproject.camaraprojectatlassian.orgnet/wiki/display/CAM/2024-03-21+TSC+Minutes

Implementation

Define guidelines for geofencing implementation

• We need more comments from the team
• Connected with Issue #85. A document with implementation guideline should cover this also.
  • As requested by Joachim, issue #85 will remain open until TEF uploads the document with more detail or the information is added to an API_documentation file to keep in the repo for future references.
    • Joachim: Should be also aligned/synchronized with Geofencing
• On issue #133 we probably need to have a base agreement for Geofencing guidelines
  • Akos & José proposed some suggestion - in particular to improve the subscription to allow consumer to indicate the 'reliability' expected.
  • Ludovic also raised the point above UC where we are not able to send any notification.... and we need to inform the consumer.

AOB

Action items