Subscription stop misses InteractionInput ?

[danielpeintner]

At the moment, the Subscription interface looks like this

It seems the stop() method seems to miss InteractionInput as used elsewhere?

Note: the EventAffordance has cancellation information to be used..

Note2: the problem might arise from the fact that Subscription is used for events and (un)observing properties. The unobserveproperty has no way to indicate cancellation information.

[danielpeintner]

See also w3c/wot-thing-description#2085

[relu91]

Call 14/05/2025,

• To cover the current features of TD, we should have a new function parameter of type InteractionInput
• @danielpeintner, the problem is that if we want to keep backward compatibility, we should add it as a last parameter, which is inconsistent with the other operations.