13:07:02 RRSAgent has joined #wot 13:07:06 logging to https://www.w3.org/2023/02/28-wot-irc 13:07:12 meeting: 4th WoT WG Charter Meeting - Day 2 13:07:46 present+ Kaz_Ashimura, Michael_McCool, Ege_Korkan, Kunihiko_Toumura, Michael_Lagally, Tomoaki_Mizushima 13:07:48 chair: McCool 13:08:29 dape has joined #wot 13:08:45 rrsagent, make log public 13:08:48 rrsagent, draft minutes 13:08:50 I have made the request to generate https://www.w3.org/2023/02/28-wot-minutes.html kaz 13:10:03 scribenick: kaz 13:10:15 topic: PRs 13:10:23 -> https://github.com/w3c/wot-charter-drafts/pulls PRs 13:10:57 mm: (goes through the list of PRs above) 13:11:19 https://github.com/w3c/wot-charter-drafts/pull/66 13:11:25 subtopic: PR 66 13:11:34 -> https://github.com/w3c/wot-charter-drafts/pull/66 PR 66 - Move IG mention to collaboration section 13:11:39 mm: (shows the diff) 13:11:54 -> https://pr-preview.s3.amazonaws.com/w3c/wot-charter-drafts/66/4cef782...116eff5.html diff 13:12:15 mm: it's kind of odd to have the description on the WoT IG within the mission section 13:12:26 ... should have it under the collaboration section 13:12:35 luca_barbato has joined #wot 13:12:35 mlagally has joined #wot 13:12:36 present+ Luca_Barbato 13:12:51 present+ Daniel_Peintner 13:13:03 q+ 13:13:18 ... would think about how to describe it later 13:13:35 ml: process conversation several times on the WG and the IG 13:13:37 ack ml 13:13:45 ... preparation on the specs 13:14:01 ... the current scope of the WoT IG is basically collecting use cases 13:14:15 q+ 13:14:32 cris__ has joined #wot 13:14:39 q+ 13:14:45 ... and this proposed change would formalize the collaboration as part of the collaboration in general 13:14:57 mm: the question is related to the visibility 13:14:58 q+ 13:15:01 ack mc 13:15:18 ... not sure the process really belongs to the mission statement 13:15:41 s/really/should really/ 13:15:44 ack e 13:16:55 kaz: maybe we should describe the relationship among WoT-related groups a bit clearer at the top of "5. Coordination" section 13:16:58 ack k 13:17:00 mm: yeah 13:17:18 ... any objection to merging this PR itself? 13:17:31 ek: what about other W3C related groups? 13:17:55 mm: potential improvements 13:18:07 ... put WoT groups in a section of their own under collaboration 13:18:29 ... move the WoT IG to the top and emphasize its special status 13:18:39 ... then would move ahead 13:18:47 (no objections) 13:18:48 merged 13:18:54 present+Michael_Koster 13:18:58 present+ Cristiano_Aguzzi 13:19:07 zakim, who is on the call? 13:19:08 Present: Kaz_Ashimura, Michael_McCool, Ege_Korkan, Kunihiko_Toumura, Michael_Lagally, Tomoaki_Mizushima, Luca_Barbato, Daniel_Peintner, Michael_Koster, Cristiano_Aguzzi 13:19:45 s/merged// 13:20:10 subtopic: PR 55 13:20:24 -> https://github.com/w3c/wot-charter-drafts/pull/55 PR 55 - Reorganize and consolidate work items 13:20:44 mm: not reflecting the discussion from yesterday's meeting 13:20:50 ... Ege will work on improvement 13:20:52 https://github.com/w3c/wot-charter-drafts/pull/46 13:20:55 subtopic: PR 46 13:21:18 -> https://github.com/w3c/wot-charter-drafts/pull/46 PR 46 - Update wot-wg-2023-draft.html: Adding digital twins 13:21:45 q+ 13:21:51 mm: still need discussion 13:22:00 ack ml 13:22:08 ml: quick comment 13:22:59 ... general issues... 13:23:08 mm: please read the comments on the PR 46 13:23:22 ml: what is the final language? 13:23:48 mm: bunch of changes by Ege, but no change with this line 13:24:24 ... digital twins a part of new use cases 13:24:39 ml: not really happy with that 13:24:47 ... but ok with closing this PR itself 13:24:55 mm: ok 13:24:57 closed 13:25:04 ml: just a side note 13:25:26 ... comments from Ben around Digital Twins would be useful 13:25:39 mm: we can look at it later 13:25:51 subtopic: PR 55 - revisited 13:25:55 https://github.com/w3c/wot-charter-drafts/pull/55 13:25:58 present+ Ryuichi_Matsukura 13:26:07 present+ Ben_Francis 13:26:30 -> https://github.com/w3c/wot-charter-drafts/pull/55 PR 55 - Reorganize and consolidate work items 13:26:39 https://htmlpreview.github.io/?https://raw.githubusercontent.com/w3c/wot-charter-drafts/7b69f009ea23dce736c5b8029483f3dc177ab27e/wot-wg-2023-draft.html 13:26:43 mm: still a bit different? 13:26:53 ek: please look at the above preview 13:27:22 s/preview/preview to see the latest updates/ 13:28:10 mm: the scope section has been updated based on the discussion during yesterday's meeting 13:28:19 ... would like to merge this if possible 13:28:49 ... high-level items plus some of the additional descriptions here 13:28:56 zakim, who is on the call? 13:28:56 Present: Kaz_Ashimura, Michael_McCool, Ege_Korkan, Kunihiko_Toumura, Michael_Lagally, Tomoaki_Mizushima, Luca_Barbato, Daniel_Peintner, Michael_Koster, Cristiano_Aguzzi, 13:28:59 ... Ryuichi_Matsukura, Ben_Francis 13:29:13 q+ 13:29:18 ml: question on "increase descriptiveness of TDs" 13:29:46 q+ 13:29:54 ek: this is what I've just added 13:30:12 ... assuming websocket, etc. 13:30:17 q+ 13:30:21 ack e 13:30:21 qq+ 13:30:38 ... we can change the description if needed 13:30:42 ack c 13:30:50 mm: bunch of comments from Ben as well 13:31:01 ek: have not checked all the comments yet 13:31:02 mjk has joined #wot 13:31:25 ack c 13:31:25 cris__, you wanted to react to Ege 13:31:30 mm: let's handle the speaker queue first 13:31:34 ack ml 13:31:57 ml: just go back to the text 13:32:28 [[ 13:32:29 Increase Descriptiveness of TDs: 13:32:29 The WG will work on increasing the descriptive power of TDs to allow using them in more use cases. This includes describing dynamic resources, reusable connections, historical values (timeseries), repeating payloads, both static and dynamic geolocation information, manageable actions and more precise definitions of data schemas for each type of operation. 13:32:30 ]] 13:32:41 ml: some high-level scope on binding 13:32:57 q+ 13:33:06 q+ 13:33:09 mm: wondering about the process here 13:33:18 ... bunch of changes here 13:33:26 q+ 13:33:39 ... we can discuss each point one by one 13:34:02 ack e 13:34:04 q+ 13:34:08 q+ 13:34:28 ek: we're addressing the descriptiveness part 13:34:47 ... would agree with McCool and think we should merge this PR for further discussion 13:34:48 ack l 13:35:04 lb: if we have agreement on these features 13:35:21 ... any of those features we'll manage 13:35:40 ... if they have enough consensus 13:36:00 ... would agree with McCool to merge this for further discussion 13:36:05 q? 13:37:11 ack k 13:37:38 kaz: we should once concentrate on the 6 major categories 13:37:40 @@@ 13:37:50 bf: ok with merging this PR itself 13:37:51 ack b 13:38:06 ca: also fine with merging this PR itself 13:38:29 please use https://htmlpreview.github.io/?https://github.com/w3c/wot-charter-drafts/blob/f521e06bb97ba5eee19a58387ebda17b1977294c/wot-wg-2023-draft.html 13:38:49 s/@@@/... my question is if we agree on the 6 major categories here. If so, we can merge this PR and then think about how to improve the descriptions later./ 13:39:19 mm: could work on text changes 13:39:37 ... and agree with Kaz we should confirm we're OK with those 6 major categories 13:40:08 ... (goes through the 6 major categories again) 13:40:11 q? 13:40:13 ack c 13:40:28 q+ 13:40:45 ... Updates to existing specifications 13:40:53 ... Support WoT Interoperability 13:41:01 ... Improve Management of TDs 13:41:09 ... Increase Descriptiveness of TDs 13:41:17 ... Improve Security and Privacy 13:41:25 ... New Use Cases 13:41:25 q+ 13:42:32 kaz: quite minor 13:42:47 ... but should have consistent style for the title 13:42:47 q+ 13:42:52 ack k 13:42:58 mm: yeah, verb or noun 13:43:02 ack l 13:43:25 lb: we can even remove the ones already published 13:44:20 ... regarding historical values (timeseries), what do we mean by that? 13:44:31 mm: we could leave those points out 13:44:45 ... let's see the updated rendering 13:44:55 -> https://htmlpreview.github.io/?https://github.com/w3c/wot-charter-drafts/blob/f521e06bb97ba5eee19a58387ebda17b1977294c/wot-wg-2023-draft.html updated rendering 13:45:04 q? 13:45:07 ack e 13:45:18 ek: (explains the updated rendering) 13:45:43 mm: not hearing those 6 major categories themselves 13:45:55 ... so major objections to merge this PR itself? 13:45:56 +1 for merging 13:45:57 (none) 13:46:04 s/none/no objections/ 13:47:10 merged 13:47:27 mm: please provide actual text for further improvements 13:47:58 https://github.com/w3c/wot-charter-drafts/issues/68 13:48:04 ... (creates a new Issue on the style of the scope headers) 13:48:14 rrsagent, make log public 13:48:18 rrsagent, draft minutes 13:48:19 I have made the request to generate https://www.w3.org/2023/02/28-wot-minutes.html kaz 13:48:28 subotopic: PR 41 13:48:29 https://github.com/w3c/wot-charter-drafts/pull/41 13:48:37 s/otopic/topic/ 13:49:06 s|https://github.com/w3c/wot-charter-drafts/pull/41|-> https://github.com/w3c/wot-charter-drafts/pull/41 PR 41 - Expand WoT CG collaboration| 13:49:28 mm: (looks at the changes) 13:50:30 -> https://github.com/w3c/wot-charter-drafts/pull/41/files#diff-bb5a0dc2199e45f601c98b3a5a01ccf2c6d88347379b133530b1179568b2ad21 proposed policy.md 13:50:47 -> https://github.com/w3c/wot-charter-drafts/pull/41/files#diff-9f8270d1c95442c38dfd4a48e6236cede38a77aec5f027798376e104ea168786 proposed Draft Charter 13:50:49 q+ 13:52:21 mm: global community vs Japanese community 13:53:32 ack k 13:53:46 kaz: ok with the draft Charter change itself 13:53:59 ... and agree we need to clarify the policy on the WoT CG's work 13:54:16 ... However, the policy clarification still needs more discussion 13:54:31 ... so would suggest we continue the policy discussion separately 13:54:34 mm: right 13:54:50 ... what about the Charter text itself? 13:55:00 q? 13:55:00 q? 13:55:03 q+ Ege 13:55:07 ek: ok 13:55:20 s/ek: ok// 13:55:32 ... would add "DRAFT" to the CG work policy document 13:55:34 ek: ok 13:55:45 mm: would merge the PR itself then 13:55:48 (no objections) 13:56:07 (some conflicts :( ) 13:57:13 mm: (resolves the conflicts) 13:57:41 ... let's check if it renders properly 13:58:13 ... (some problem with the link for the WoT IG, but can be fixed later) 13:58:15 merged 13:58:26 topic: Next steps 13:58:31 mm: we're getting close 13:58:47 ... would like to use the half of the main call for the Charter discussion tomorrow 13:59:04 q+ 13:59:09 q+ 13:59:55 ek: quite a bit of issues there 14:00:06 s/there/on the GitHub repo/ 14:00:20 -> https://github.com/w3c/wot-charter-drafts/issues remaining issues 14:00:40 mm: effects the Charter for review? 14:00:46 ... or details? 14:01:32 ... Michael Lagally, can we use the Architecture call for the Charter discussion? 14:01:43 ack e 14:01:45 ml: if needed 14:01:45 q+ 14:02:14 kaz: in that case, we should use the whole one hour from the main call tomorrow 14:02:17 mm: right 14:02:39 ... let's assume two more hours this week, the main call tomorrow and the Architecture call on Thursday 14:03:30 benfrancis, are you available wednesday 4pm CEST? in the td binding call we can discuss #14 14:03:35 https://github.com/w3c/wot/pull/14 : toy example comment to show PR 14:03:36 [adjourned] 14:03:49 rrsagent, draft minutes 14:03:50 I have made the request to generate https://www.w3.org/2023/02/28-wot-minutes.html kaz 14:04:01 s|benfrancis, are you available wednesday 4pm CEST? in the td binding call we can discuss #14|| 14:04:02 https://github.com/w3c/wot/pull/14 : toy example comment to show PR 14:04:19 s|https://github.com/w3c/wot/pull/14 : toy example comment to show PR|| 14:04:20 rrsagent, draft minutes 14:04:21 I have made the request to generate https://www.w3.org/2023/02/28-wot-minutes.html kaz 16:03:53 Zakim has left #wot 16:12:42 Danrancan has joined #wot 16:13:24 asocrt has joined #wot 16:17:39 Github has joined #wot 16:19:37 rzr has joined #wot 16:25:06 bencrus has joined #wot 16:30:27 vianka has joined #wot 16:34:04 tallship has joined #wot 16:50:28 cris has joined #wot 16:53:07 ravani has joined #wot 17:01:09 w3c_modbot has joined #wot 17:01:10 KevinBush has joined #wot