Skip to content

Better description for EventAffordance subscription and cancellation #2084

@relu91

Description

@relu91

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 subscribeevent operation, 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 unsubscribeevent operation, e.g., a specific message

Metadata

Metadata

Assignees

No one assigned

    Labels

    EditorialIssues with no technical impact on implementations

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions