Meeting minutes
Previous minutes
<kaz> Mar-5
Cristiano: Found minor typo
Kaz: fixed
Cristiano: I think we can approve the minutes
… minutes are approved
PRs
PR 561
PR 561 - Extended return type of invokeAction()
Cristiano: I think the interface looks good
… and can start changing the prose
… new shape
… ActionInteractionOutput
… 2 new functions
… cancel and query
… we cannot do everything right now.. need to wait for TD to improrve
… async vs sync actions
Cristiano: What should we do if not async
Daniel: we can have two options: throw or no-op
Daniel: 2 options
… throwing or no-op
… I tend to throw
Cristiano: cancel is easy.. void function
… query more difficult.. need to decide what to return
… opened issue on TD side... issue 2068
<kaz> related TD Issue 2068 - Specify the result of queryaction operation
Daniel: wonder the pros and cons?
Cristiano: No async term in TD possible
Daniel: sync could return the previously reported value and cancel a no-op
Cristiano: requires buffering
… plus it could be a different value for query
<Cristiano noting down the discussion in the PR>
Daniel: Could also check whether in the Web space there are such cases already...
Kaz: Technically, we can summarize our questions in more details
… and ask TAG for feedback
Cristiano: Makes sense, thanks!
Zoltan: Up to the underlying platform...
… we should avoid giving no details
… we should be transparent
… failing is the better approach
Cristiano: Corner cases in TD not specifying terms
Zoltan: I can get errors in Promise if there are problems anyway
Daniel: Can try to integrate the discussions..
Issues
Issue 571 - Sync schemas is now outdated
Issue 571 - Sync schemas is now outdated
Cristiano: At the moment sync is not working anymore
… moreover GitHub stops action after some time
… I will update the action
… plan to just update the reference, w3c/
Kaz: I am okay with the resolution
… should use a specific label
… like "logistics", "GitHub problem" or so
Daniel: wot-resources is the final TD .. while we used the "live" version of the JSON schema
Cristiano: Correct
… should try to use the final version
… and align it as much as we can
… in the TD 2.0 work we might need to update the resources
Issue 570 - Looking into Deno
Cristiano: Reminder from main call
… what do we want to do?
Daniel: Recalling Luca mentioning it was not working at that time
Cristiano: Yes, tried together with Luca
… we should give it a try with node-wot
… closing the issue in Scripting?
… BTW we have Bun as runtime also
Issue 569 - Subscription stop misses InteractionInput
Issue 569 - Subscription stop misses InteractionInput ?
Cristiano: TD misses the payload information
Cristiano: Do we need optional InteractionInput ?
Daniel: second optional parameter?
Cristiano: Yes, but the pattern is used often enough
Daniel: issue with existing parameter... creates issue with backwards compatibility .. if we put it as first parameter
Cristiano: Yes...
… or break compatibility since we are still in the explorative version
Cristiano: let's wait for feedback from others
Issue 539 - ObserveProperty with uri vars
Issue 539 - ObserveProperty with uri vars
Cristiano: This is a plain bug
… same event with parameter
… instead of 1 listener per event we should have 1 listener per event&uriParameter
Zoltan: Should be an option
… why the constraint to have at most one listener at all
Cristiano: Good point
… map to allow multiple subscriptions?
Zoltan: Instead of single slot we would (should?) have a list or map
Daniel: should do an analysis why we made this decision at that time
Cristiano: Need to look into more closely
[adjourned]