DRAFT AGENDA
Date
...
- Are we happy with security scope for geofencing
- Scope name should reflect the date data provided by the notification (not
geofencing:subscriptions:write
but more precise likegeofencing:subscriptions:read-location
) - Discussion on this topic in progress in Commonalities (camaraproject/Commonalities#163) Any update?
- 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.
- Scope name should reflect the date data provided by the notification (not
Geofencing - Adding a value in Termination Reason value enum
- Discussion in progress in CommnonalitiesCommonalities: camaraproject/Commonalities#153
- Related issues in DeviceStatus and QoD Any update?
- 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
- Geofencing API - Defining a standard behavior for first event
- Issue in Commonalities Issue 140
Any update? - 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)
Geofencing API - Add "format: uri" to notificationUrl
- Issue in commonalities Any update?
- No progress in commonalities
On hold discussions
Administrative Code Area
...