11:00:13 RRSAgent has joined #wot-script 11:00:13 logging to https://www.w3.org/2021/05/03-wot-script-irc 11:04:17 Meeting: WoT Scripting API 11:04:32 cris has joined #wot-script 11:04:35 present+ Kaz_Ashimura, Daniel_Peintner, Cristiano_Aguzzi 11:04:52 scribenick: kaz 11:05:03 topic: Agenda 11:05:11 zkis has joined #wot-script 11:05:17 s/Agenda/Minutes/ 11:05:25 -> minutes 19 april, see https://www.w3.org/2021/04/19-wot-script-minutes.html 11:05:45 dp: the call after the vF2F 11:05:51 present+ Zoltan_Kis 11:06:07 ... (goes through the minutes 11:06:12 s/minutes/minutes)/ 11:06:23 ... we'll postpone the publication 11:07:02 ... topics related to discovery 11:07:38 ... issues related to TD, discovery and security 11:08:09 ... requirements on the (possible) management api 11:08:19 ... any objections? 11:08:32 (none; approved) 11:08:54 -> minutes 6 April 2021, https://www.w3.org/2021/04/26-wot-script-minutes.html 11:09:03 s/6 April/26 April/ 11:09:14 dp: joint discussion with the Security TF 11:09:27 Mizushima has joined #wot-script 11:11:10 ... we need some kind of management api to handle security 11:11:59 present+ Tomoaki_Mizushima 11:12:16 ... any objections? 11:12:22 (none; approved) 11:13:28 Agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#3_May_2021 11:13:57 topic: Quick updats 11:14:15 subtopic: Security 11:14:28 -> https://github.com/w3c/wot-scripting-api/issues/315 Issue 315 - Security TaskForce related issues 11:14:39 ca: well summarized 11:15:02 dp: any other comments? fine? 11:15:35 zk: need to create some deliverable on runtime 11:15:40 q+ 11:15:55 ... different from the script api itself 11:16:07 ack k 11:16:17 kaz: implementation guideline, you mean? 11:16:32 zk: a bit different 11:17:04 dp: we could have some kind of management api. right? 11:17:09 ack k 11:17:12 q+ 11:17:34 zk: might need a different mode 11:18:04 ... what is defined by the current Scripting API is definition for client apis 11:18:09 s/apis/APIs/ 11:18:51 kaz: in that case, a separate document on the possible management API? 11:19:11 zk: a document about runtime of Scripting API 11:20:23 kaz: not really sure about the difference between an "implementation guideline" and a "runtime document" 11:20:47 ... but if we're ok with generating an informative WG Note about that, that's fine 11:20:54 s/fine/possible/ 11:23:21 ... if we want to generate a separate group Note about some topics, we should summarize what to be described by that document and bring the idea to the main call to get a group resolution 11:23:23 zk: ok 11:23:28 dp: ok 11:23:41 ... but still not really sure about what to be done there 11:24:42 ... would like to get consensus within this Scripting API first 11:25:07 ca: don't have any strong opinion at the moment. 11:25:37 ... different information could be included under one specific repository 11:26:24 dp: how to proceed? 11:26:36 kaz: we should clarify what we want to document first :) 11:27:15 https://github.com/w3c/wot-scripting-api/issues/299#issuecomment-826823233 11:27:21 zk: we can skim the issue listed here (=within the issue 315) 11:27:39 s/the issue listed/the issues listed/ 11:28:13 (issue 299 and 298 are included in issue 315) 11:28:46 -> https://github.com/w3c/wot-scripting-api/issues/299 Issue 299 - Chose a particular security schema for an ExposedThing 11:29:13 dp: we need to be careful about the API names 11:29:31 zk: we can control the device remotely 11:30:19 dp: there is an MD file about our basic ideas 11:30:57 zk: we should split the manager API topic from the Scripting API itself 11:31:41 ... so we should move the content of "script-manger" area to another repository 11:31:56 -> https://github.com/w3c/wot-scripting-api/tree/main/applications/script-manager script-manager area under wot-scripting-api repo 11:32:23 q? 11:32:25 ack k 11:34:28 zk: we need a separate namespace from the consumer discovery 11:34:53 ... it requires a different level of permission 11:35:28 q+ 11:35:54 q+ 11:37:13 dp: the developer should have method to control it 11:37:28 ... even though that is not the case with the node-wot implementation at the moment 11:40:59 ack k 11:41:12 kaz: sorry but I still don't really understand your expectations... 11:41:42 ... so would suggest you both clarify your expected features, phases, APIs, etc., first 11:42:10 ... and then we can think about how to deal with those points by what kind of documents 11:42:11 ack k 11:42:13 ack c 11:42:52 ca: exposedThing is almost a system-level API 11:43:39 ... for system-level implementations, what is needed to be implemented? 11:44:36 -> https://github.com/w3c/wot-scripting-api/issues/299#issuecomment-826823233 Cristiano's comment on Issue 299 11:45:09 dp: this happens for exposedThing 11:45:34 zk: we can take this forward but what security portion to be implemented? 11:46:09 ... exposedThing has to be created 11:46:33 ... and what to be provided by the runtime? 11:46:58 q? 11:47:00 q+ 11:47:12 ca: currently we don't do any validations 11:47:35 zk: cat it include any kind of security specifications? 11:48:00 ... wondering about what would be a better API definition 11:48:17 dp: we have a "wot" namespace already 11:48:35 ... but what would be included in the runtime? 11:49:36 zk: wot.runtime should have a different permission from wot.consume 11:49:58 ... 3 different levels for consume, level and expose 11:50:21 s/level and/discover and/ 11:50:47 ca: maybe we need those three levels 11:51:22 dp: wonder how to differentiate them 11:52:12 q? 11:52:28 zk: we can create a new runtime object for WoT 11:52:38 ... but with a different permission level 11:53:00 ... we have consume, expose and discover 11:53:09 ... and what else? 11:54:07 ... we can continue the discussion 11:55:30 kaz: those three are rather different phases. right? 11:55:59 zk: we use "phase" for provisioning, etc. 11:56:12 kaz: in that case, maybe three different modes 11:56:54 zk: need to continue the discussion 11:57:55 s/topic: Quick updats/topic: Joint calls/ 11:58:00 ack k 11:58:15 subtopic: Discovery 11:58:30 dp: will we have a joint discussion with the Discovery TF today? 11:59:05 https://github.com/w3c/wot-thing-description/issues/1097 11:59:08 zk: can be checked with McCool during the Security call 11:59:24 topic: TD 11:59:33 s/topic:/subtopic:/ 12:00:09 s/https/-> https/ 12:00:35 s/1097/1097 wot-thing-description Issue 1097 - Provide Typescript types definitions for Thing Descriptions 12:01:33 dp: some description on the wot-scripting-api repo 12:01:39 -> https://github.com/w3c/wot-scripting-api/blob/main/typescript/index.d.ts Daniel's writeup 12:02:02 [adjourned] 12:02:09 rrsagent, make log public 12:02:11 rrsagent, draft minutes 12:02:11 I have made the request to generate https://www.w3.org/2021/05/03-wot-script-minutes.html kaz 12:03:28 rrsagent, draft minutes 12:03:28 I have made the request to generate https://www.w3.org/2021/05/03-wot-script-minutes.html kaz 12:05:51 rrsagent, draft minutes 12:05:51 I have made the request to generate https://www.w3.org/2021/05/03-wot-script-minutes.html kaz 12:14:59 Chair: Daniel 12:15:00 rrsagent, draft minutes 12:15:00 I have made the request to generate https://www.w3.org/2021/05/03-wot-script-minutes.html kaz 12:37:14 zkis2 has joined #wot-script 13:35:13 Mizushima has left #wot-script 14:02:15 Zakim has left #wot-script 14:03:17 zkis has joined #wot-script 15:46:53 zkis2 has joined #wot-script