- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Mon, 21 Sep 2020 18:23:41 +0900
- To: public-wot-wg@w3.org
available at: https://www.w3.org/2020/08/31-wot-minutes.html also as text below. Thanks a lot for taking the minutes, Zoltan! Kazuyuki --- [1]W3C [1] http://www.w3.org/ - DRAFT - WoT Scripting API 31 Aug 2020 Attendees Present Zoltan_Kis, Kaz_Ashimura, Daniel_Peintner, Cristiano_Aguzzi Regrets Tomoaki_Mizushima Chair Zoltan Scribe zkis Contents * [2]Topics 1. [3]Approving past 2 minutes 2. [4]Issue 253 https://github.com/w3c/wot-scripting-api/issues/253 closed by PR 3. [5]Issue 241 https://github.com/w3c/wot-scripting-api/issues/241 4. [6]Issue 237 https://github.com/w3c/wot-scripting-api/issues/237 * [7]Summary of Action Items * [8]Summary of Resolutions __________________________________________________________ Approving past 2 minutes <kaz> [9]Aug-17 [9] https://www.w3.org/2020/08/17-wot-minutes.html <kaz> [10]Aug-24 [10] https://www.w3.org/2020/08/24-wot-minutes.html <scribe> scribe: zkis Zoltan: updated the readme, and for the older docs, if not maintained, we could move them to the archive <scribe> ACTION: ZK updates the rationale.md Aug 17 minutes approved. Zoltan: can we do validation in constructor? Cristiano: yes, it can be done ... also, in expose() we need to check if the runtime supports the forms defined by the TD Zoltan: makes sense Daniel: node-wot picks one Form and throws away the rest Zoltan: to my understanding, the Forms are in OR relationship, so at least one Form should pick Daniel: and we throw away all other Forms ... node-wot doesn't use URLs for instance in HTTP Forms, they are pruned from the start Cristiano: but we should support hints Zoltan: definitely we need to update the expose() algorithm Daniel: it's difficult to support hints Cristiano: this is true for Forms perhaps, but what about security ... e.g. if we want OAuth and that is not supported Zoltan: security schemes define if they are OR, AND, OneOf type - scripting algorithms should follow that semantics <scribe> ACTION: CA file an issue security scheme <scribe> ACTION: ZK update the expose() algorithm (with a tracking issue) Aug 24 minutes approved Issue 253 [11]https://github.com/w3c/wot-scripting-api/issues/253 closed by PR [11] https://github.com/w3c/wot-scripting-api/issues/253 <kaz> closed Issue 241 [12]https://github.com/w3c/wot-scripting-api/issues/241 [12] https://github.com/w3c/wot-scripting-api/issues/241 Zoltan: interaction is better understood by developers, we can put a note explaining the relationship with affordance Daniel: TD spec uses affordance Cristiano: interaction is more clear indeed, but there is the argument to be in line with other specs Daniel: making a comment in the issue Issue 237 [13]https://github.com/w3c/wot-scripting-api/issues/237 [13] https://github.com/w3c/wot-scripting-api/issues/237 API discussion for exposing errors Cristiano: would add another proposal ... using the subscribed as a Promise() Zoltan: we need a status for subscription and this could be merged with that Daniel: we could have a callback also for that Zoltan: we need a property, since the state is triggered by the error Cristiano: the apps wants to make choices based on the error, so it's fine to expose Daniel: would prefer providing the callbacks in the function signature Zoltan: and we stay with the Promise Cristiano: maybe passing callbacks in an object would be better perhaps call adjourned Summary of Action Items [NEW] ACTION: CA file an issue security scheme [NEW] ACTION: ZK update the expose() algorithm (with a tracking issue) [NEW] ACTION: ZK updates the rationale.md Summary of Resolutions [End of minutes] __________________________________________________________ Minutes manually created (not a transcript), formatted by David Booth's [14]scribe.perl version ([15]CVS log) $Date: 2020/09/07 06:46:09 $ [14] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [15] http://dev.w3.org/cvsweb/2002/scribe/
Received on Monday, 21 September 2020 09:23:46 UTC