Meeting minutes
Previous minutes
Cristiano: Minutes look good -> approved
Calendar
Daniel: 2 points
Calendar invite
Daniel: it shows we didn't send update
… wonder whether everyone has it in calendar?
Cristiano: I think we did a minor update and didn't want to bother everyone
<kaz> WoT Scripting API calendar
Zoltan: Had issues with W3C calendar entry
Kaz: Outlook has difficulties sometimes
… ICS download is possible also
Cristiano: used public link in Google Calendar and imported it in Outlook
… shall we send notification to remove warning?
Zoltan: Yes
Cristiano: Done!
Marketing page
<kaz> WoT Marketing page - Web Conference Meetings
Daniel: 2nd point: Used to say the current slot is intermediary ...
Cristiano: Correct, problematic for US
… would keep the slot as is
Zoltan: Slot is okay for me, but sometimes I might have issues
PRs
Extend invokeAction
PR 561 - Extended return type of invokeAction()
Daniel: No news from my side
… once I have time to work I will summarize the decision
Issues
Use-case WoT in the Browser
Issue 566 - [Use-case] WoT in the Browser
Cristiano: Issue coming from McCool
… going over use-cases issues
… we can validate use-case
… report back with real feature request
… it is about WoT in the browser
Zoltan: websocket is a possibility
Cristiano: Ben in web-thing-protocol is a relevant CG
Zoltan: feedback from browser people
… native dependencies in the browser... will not happen
Cristiano: MQTT, CoAP, WebSocket and HTTP can be supported
Kaz: We need to think about use-case
… we need to clarify what "WoT in browser" means
… browser vendors supporting WoT ?
Cristiano: It would be nice
… I don't think it will happen
… used as library is fine
… requirements on browser ?
Zoltan: Interest w.r.t. dependency
… problem with external dependencies
… not acceptable for browser vendors
… we have to go with existing APIs in browser
Cristiano: limited to HTTP, CoAP, MQTT, WebWocket ...
Zoltan: WoT is a web application
… we cannot have Scripting API though
Daniel: We can
Zoltan: But just not as native.. just as JS library
Daniel: I think we can live with JS library
Cristiano: Correct, native support wasn't needed in the past
Kaz: If we're OK with starting with a Polifill library for WoT. That would make sense.
Cristiano: Yes
<CA summarizing the discussion in the issue>
Daniel: Need to report it back to Use-Case taskforce
Cristiano: Okay, user story is valid but no need on browser side
Daniel: New workflow in TD/Use-case requires use-case to foster new features
Cristiano: Work already done ... but can be described
Kaz: working group is main stakeholder, but work can be delegated to task force
… if Scripting TF is okay with starting with polyfill we can propose that
… can talk about it in main call
Mizushima: topic important
… W3C is browser
… we should submit this issue to use-case taskforce
… need to clarify what is needed
… not sure where the topic should be discussed
Cristiano: Correct, touches many task forces
Kaz: That's why I'm suggesting we bring this proposal to main call
… we can discuss how to deal with it as well
… procedure/process can be discussed
Zoltan: Technical input to the main call today
Cristiano: Yes, our feedback is important
Cristiano: Good that we have a direction now (issue is rather old)
Review Observe handler in the algorithms
Issue 455 - Review Observe handler in the algorithms
Cristiano: need to look into it again
[adjourned]