Meeting minutes
Minutes
approved
Cancellation?
Daniel: basically, next week will be the PlugFest
… however, our slot is not overlapped
… shall we have a call?
(some discussion)
Daniel: let's cancel the Scripting call next Monday, on March 14
Issues
Issue 335
Issue 335 - New op values (queryaction and cancelaction)
Daniel: we need resolution for this
Zoltan: related to "sync" vs "async"
Kaz: we need to clarify the minimum set of cancellable session and the minimum set of expected synchronous/asynchronous actions based on concrete use cases
… so I suggested before for the TD discussion and also would still suggest we defer this feature to the next version
8. The ConsumedThing interface
Daniel: (shoes section "8. The ConsumedThing interface" of Scripting API)
Promise<InteractionOutput> invokeAction(DOMString actionName,
optional InteractionInput params = null,
optional InteractionOptions options = null);
Zoltan: we can have this kind of pattern for Scripting API itself without any conflicts
Daniel: the question is the possibility of another possible action to be defined other than some simple actions
… only specifying the name of action might not be sufficient
… we can't tell whether the target action is a single one or a set of multiple ones
Kaz: for example, ECHONET defines history and grouping
… if we think about sync/async and cancellation of actions, probably we should consider those capabilities as well
… ECHONET doesn't ask us, WoT WG, to extend TD with those capabilities at the moment
… but there is a possibility they will give us some more use cases for that direction
… anyway, we (Scripting TF) should collaboratively work with the TD TF for further extensions
… based on concrete use cases
… but that should be done for the next version
Jan: maybe this approach of querying actions for cancellation would be related to subscription of events
Daniel: what if I invoked the same action twice and would cancel only one of them?
Zoltan: we have to have a notation to distinguish it
… technically, we can add an ID to distinguish it for the API
Kaz: again, this topics is a bigger issue to be handled by a TF, e.g., the Scripting TF or the TD TF
… if we really want to think about this direction, we should once clarify a dedicated use case description which requires this direction
… and then think about how to deal with the requirements based on the use case for Architecture, TD, Scripting API, etc.
… because we need to define an ID to identify an action from others, manage the history of actions, a session to be rolled back at once, etc.
Zoltan: right
Issue 354
Issue 354 - Conformance section necessity
Daniel: need discussion during the Editors call
Next call
Daniel: as confirmed at the beginning, there will no Scripting call next Monday, March 14, due to the PlugFest
… we'll have the next Scripting Call on March 21
[adjourned]