DRAFT AGENDA
...
- 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?
- Jose from TEF will upload an example of Location Verification ATP once the commonalities guidelines are approved
- Dedicated workshop in Commonalities scheduled for May 16th
- Issue in Commonalities to discuss Enhancement of the Testing Guidelines by TEF
@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
...
- 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
- 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
inconfig
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)
...