12:03:47 RRSAgent has joined #wot-script 12:03:47 logging to https://www.w3.org/2021/02/08-wot-script-irc 12:05:02 Mizushima has joined #wot-script 12:06:49 Meeting: WoT Scripting API 12:06:59 Chair: Daniel 12:07:12 present+ Kaz_Ashimura, Daniel_Peintner, Cristiano_Aguzzi 12:07:59 present+ Tomoaki_Mizushima 12:09:47 scribenick: kaz 12:09:51 zkis has joined #wot-script 12:10:33 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#8_February_2021 12:10:38 topic: Prev minutes 12:10:45 present+ Zoltan_Kis 12:10:47 -> https://www.w3.org/2021/02/01-wot-script-minutes.html Feb-1 12:14:33 dp: (goes through the minutes) 12:15:06 kaz: (fixes the URLs and also adds the titles to Issues and PRs) 12:15:14 present+ Zoltan_Kis 12:15:32 topic: Quick updates 12:15:55 dp: we're renaming the "master" branch to "main" 12:20:43 topic: PR 289 12:21:07 -> https://github.com/w3c/wot-scripting-api/pull/289 Add definitions for partialTD #289 12:21:40 dp: (shows the diff) 12:22:20 -> https://pr-preview.s3.amazonaws.com/w3c/wot-scripting-api/289/ef9c211...relu91:66d5a75.html#use-an-exposedthinginit diff - 5.2.1 Use an ExposedThingInit 12:22:54 ca: (explains the algorithm there) 12:24:36 dp: expanding the step 7 to search for missing required properties? 12:24:47 q+ 12:26:32 dp: what about the default values? 12:26:56 ca: we can assume empty as default but that would not be valid TD 12:27:39 ... see also section 4.2 12:27:57 -> https://pr-preview.s3.amazonaws.com/w3c/wot-scripting-api/289/ef9c211...relu91:66d5a75.html#expanding-a-thing-description 4.2 Expanding a Thing Description 12:28:29 zk: can understand Daniel's point, but we need to specify the algorithm clearly here 12:29:19 dp: it's true we should be clear 12:29:30 ... but we should not be too restrictive 12:29:41 zk: we should add that kind of notes 12:30:09 ca: think it's specific enough but not too restrictive 12:30:49 q? 12:31:14 zk: we could add some guidance on how to handle href 12:31:23 dp: also 'title' 12:31:32 s/href/'href'/ 12:33:17 (some more discussion) 12:33:49 dp: maybe the step 7 ( Search for missing required properties in td accordingly to TD JSON Schema) can be preserved asis 12:33:58 ... and the detail to be defined separately 12:34:19 zk: iterative approach to improve the description is fine 12:34:58 q? 12:35:06 ack kaz 12:36:26 kaz: accepting this proposed algorithm is ok by me 12:36:41 ... but we should add some concrete example TD to be parsed here 12:37:12 ... also we should clarify which step handles which TD fragment or token because some of the steps lack the detail 12:37:22 ca: agree with both the comments 12:37:32 dp: right 12:38:01 ... we should add concrete TD example here 12:38:36 zk: the note for step 7 (TODO: possibly expand this step) could be added as an Editor's note 12:38:39 dp: yes 12:39:07 ca: totally agree 12:39:30 ... should have examples on "before the step" and "after the step" 12:40:55 kaz: maybe we can simply merge this PR 289 itself and then think about further improvement later 12:41:10 ca: would like to think about security portions as well 12:42:37 dp: we should consider proper security scheme as well 12:44:36 ... regarding the step 4 12:44:43 ... "For each scheme defined in securityDefinitions check if it is supported by the Protocol Bindings . if not remove scheme" 12:45:59 ... it's OK to have only one Protocol Binding which supports som security scheme 12:46:06 ca: ok 12:46:42 dp: let's ask McCool for guidance too 12:48:46 ... how to make sure the users' suggestions are fulfilled? 12:49:13 ... (gives the comments to PR 289) 12:49:16 ... thanks! 12:49:30 s/thanks!/thanks, Cristiano!/ 12:50:34 topic: Issue 296 12:50:50 -> https://github.com/w3c/wot-scripting-api/issues/296 DataSchemaValue in TS should not be any #296 12:52:18 -> https://github.com/w3c/wot-scripting-api/pull/297 related PR - make TS definitions for DataSchemaValue more accurate #297 12:53:23 ca: there was another PR as well 12:53:44 -> https://github.com/w3c/wot-scripting-api/issues/292 another PR - Simplification of interface InteractionOutput #292 12:55:17 zk: it's already clear and implemented 12:55:38 dp: (shows section 6.2.2 12:55:39 1 12:55:45 s/1// 12:55:58 s/6.2.2/6.2.1 of the Editor's Draft) 12:56:20 -> https://w3c.github.io/wot-scripting-api/#the-value-function 6.2.1 The value() function - wot-scripting-api ED 12:57:39 dp: what is problematic to me is the step 2 at section 6.2.1 12:57:50 ... "If the value of the [[value]] internal slot is not undefined, resolve promise with that value and abort these steps." 12:59:10 zk: the WoT Scripting API is for the implementer of the Scripting API developers 12:59:34 ... we need to check the algorithm to see who is generating what 13:00:39 dp: actually, section 6.1 states "DataSchemaValue is an ECMAScript value that is accepted for DataSchema defined in [WoT-TD] (i.e. null, boolean, number, string, array, or object)." 13:00:58 -> https://w3c.github.io/wot-scripting-api/#the-interactioninput-type 6.1 The InteractionInput type 13:01:10 dp: would like to think about how to fix the description 13:01:26 ... at DataSchemaValue definition 13:01:44 zk: the proposed change at PR 297 is fine 13:02:20 -> https://github.com/w3c/wot-scripting-api/pull/297/files changes within PR 297 13:03:00 (some more discussion) 13:03:19 dp: (adds comments based on Zoltan's advice) 13:04:10 -> https://github.com/w3c/wot-scripting-api/pull/297#issuecomment-775135788 Daniel's comment 13:04:11 -->https://github.com/w3c/wot-scripting-api/pull/297#issuecomment-775135788 13:04:33 s|-->https://github.com/w3c/wot-scripting-api/pull/297#issuecomment-775135788|| 13:04:36 [adjourned] 13:04:40 rrsagent, make log public 13:04:45 rrsagent, draft minutes 13:04:45 I have made the request to generate https://www.w3.org/2021/02/08-wot-script-minutes.html kaz