-
Notifications
You must be signed in to change notification settings - Fork 65
Open
Labels
EditorialIssues with no technical impact on implementationsIssues with no technical impact on implementations
Description
In EventAffordance section, we describe the different fields in table 7. During today's Scripting API call, we reviewed them and found out that the descriptions for subscription and cancellation could be improved.
In particular, both of them speak about a "Subscription", but it is not clear how they are related to the underlying WoT operation. I suggest the following:
- Subscription: Defines data that needs to be passed upon subscription with
subscribeeventoperation, e.g., filters or message format for setting up Webhooks. - Cancellation: Defines any data that needs to be passed to unsubscribe to a subscription with
unsubscribeeventoperation, e.g., a specific message
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
EditorialIssues with no technical impact on implementationsIssues with no technical impact on implementations