14:04:07 RRSAgent has joined #wot-sec 14:04:11 logging to https://www.w3.org/2024/01/15-wot-sec-irc 14:04:12 present+ WoT Security 14:04:25 present+ Mahda_Noura 14:04:35 present+ Kaz_Ashimura, Michael_McCool 14:05:19 ScribeNick: mahda-noura 14:06:07 topic: minutes 14:06:49 present+ Tomoaki_Mizushima 14:07:06 -> https://www.w3.org/2023/12/11-wot-sec-minutes.html Dec-11 14:07:39 mm: hoping to find TF lead 14:07:58 mm: the table we were completing is a use case activity 14:08:19 ...we could pause this meeting in the meantime while we finish the use case 14:08:41 ...we can select a date for out next meeting focusing on security 14:08:58 ...is there any objection to cancelling 4 security calls? 14:09:06 (none) 14:09:20 mm: our next security call can focus on work item linking 14:10:35 agenda: https://www.w3.org/WoT/IG/wiki/IG_Security_WebConf#15_January_2024 14:11:03 s/call can/call (Feb 19) can/ 14:11:42 mm: in our call last time, we had some concerns that this template is not the exact template, and there are 70+ use cases and we won't get to work on all in one meeting 14:11:50 ...the idea was to split the task 14:12:20 do have issue https://github.com/w3c/wot-usecases/issues/243 14:12:46 rrsagent, make log public 14:12:50 rrsagent, draft minutes 14:12:51 I have made the request to generate https://www.w3.org/2024/01/15-wot-sec-minutes.html kaz 14:13:10 chair: McCool 14:13:20 mm: going through this table is not the right thing to do technically 14:13:39 meeting: WoT Security 14:13:41 rrsagent, draft minutes 14:13:43 I have made the request to generate https://www.w3.org/2024/01/15-wot-sec-minutes.html kaz 14:13:59 mn: I agree that we should look at this table in the use case call 14:14:12 mm: clean up the issue tracker 14:14:26 i|hoping to find|approved| 14:14:47 i|hoping to find|topic: Cancelling calls and need for a new TF lead| 14:15:34 i|in our call last|topic: Use Cases and Requirements| 14:15:37 rrsagent, draft minutes 14:15:39 I have made the request to generate https://www.w3.org/2024/01/15-wot-sec-minutes.html kaz 14:16:19 subtopic: Discovery 14:16:32 mm: nothing new in that since a while 14:19:11 i|subtopic: Discovery|topic: Issues| 14:19:13 q+ 14:19:19 subtopic: WoT Security Issue Tracker 14:21:03 mm: Issue 209: https://github.com/w3c/wot-security/issues/209 14:22:20 ...This issue is a year old now, we have a number of issues, 3 of them are addressed but the rest not. I think this issue has been a bit confused with a bunch of different things in it 14:23:01 ack k 14:23:38 mm: I think we should split it into smaller issues 14:23:54 ...we capture this table somewhere else 14:25:06 i|subtopic: WoT Security Issue Tracker|subtopic: Scripting API| 14:25:35 i|subtopic: WoT Security Issue Tracker|-> https://github.com/w3c/wot-scripting-api/issues?q=is%3Aopen+label%3Asecurity+sort%3Aupdated-desc wot-scripting-api Issues with "Security" label| 14:25:56 rrsagent, draft minutes 14:25:57 I have made the request to generate https://www.w3.org/2024/01/15-wot-sec-minutes.html kaz 14:28:46 q+ 14:29:41 kaz: are all the discussions and the content from issue number 209 all included in the new issue? 14:29:59 mm: no, just one of the comment 14:30:34 kaz: how to deal with it? 14:31:27 mm: we close the issue, but factor out into other small issuers since a number of them have already been taken care of 14:32:04 kaz: maybe we can copy the discussion points from Jan 30 over 14:32:33 -> https://github.com/w3c/wot-security/issues/209#issuecomment-1408653478 discussion in Security TF call Jan 30 14:32:50 mm: My concern is that it's difficult to keep track of what has been dealt with and what not 14:33:09 kaz: for this purpose, we can copy over the discussion points 14:33:33 s/for this/for that/ 14:33:48 mm: my concern is that, we got a long list of things to be fixes and not all have been fixed, but we just have lost track of what has been done 14:34:30 kaz: maybe we can simply trash everything, but maybe there are important comments 14:34:56 s/there are/there several/ 14:35:47 mm: I think the ones we already have issues for, we don't necessarily need to keep 14:37:25 mm: some of the points that have already been addressed are commented under the issue 14:39:49 q? 14:39:50 ack k 14:40:52 q+ 14:41:19 ack k 14:42:39 mm: there is a bunch of stuff in this issue related to signing, key distribution and so on, we could put all of them in one issue 14:44:34 ...some leftover issues from issue number 209 are added into https://github.com/w3c/wot-security/issues/234 14:45:15 ...issue 209 https://github.com/w3c/wot-security/issues/209 is closed 14:45:45 ......PR https://github.com/w3c/wot-security/pull/233 is merged 14:47:19 ...I am wondering, Mahda, we had this cloud stuff issue 14:47:49 mn: I worked on this somewhile ago, but the problem is that there are no proper references that can be used as good sources 14:48:28 https://github.com/w3c/wot-security/issues/206 14:49:26 i|I am wondering|subtopic: Issue 206| 14:49:53 s|https://github.com/w3c/wot-security/issues/206|| 14:50:15 i|I am wondering|-> https://github.com/w3c/wot-security/issues/206 Issue 206 - Add and Update Cloud References| 14:50:49 mm: Issue IoT-Cloud Integration assigned to Mahda, not higher priority 14:51:03 subtopic: Issue 231 14:51:19 -> https://github.com/w3c/wot-security/issues/231 Issue 231 - Wot-sec ontology 14:52:15 mn: most of the WoT ontologies have similar problems 14:52:27 https://github.com/w3c/wot-security/issues/231 14:52:40 mm: this affects various downstream tasks 14:52:53 ... knowledge graphs and HTML rendering, etc. 14:53:12 ... other things like rdfs:domain a also missing 14:53:45 ... also should make sure there is a comment for every definition so that the documentation is asonable 14:53:56 ... in some cases, ay have to define some other classes 14:54:07 ... but most are easy 14:54:56 ... if we only add data object properties to existing classes, wil be backward compatible 14:55:21 ... but other changes may not be 14:55:52 s|https://github.com/w3c/wot-security/issues/231|| 14:56:20 subtopic: Issue 220 14:56:40 -> https://github.com/w3c/wot-security/issues/220 Issue 220 - [Discuss] Consider moving Terminology to the beginning 14:56:51 mm: let me mark this with "[Discuss]" 14:57:06 subtopic: Issue 202 14:57:16 -> https://github.com/w3c/wot-security/issues/202 Issue 202 - Reference terminology section of the architecture spec 14:57:27 mm: that issue is old and can be closed 14:57:39 ... based on the latest Editor's draft 14:58:01 -> https://w3c.github.io/wot-security/ Editor's draft 14:58:06 closed 14:58:26 topic: AOB 14:58:34 mm: let's focus on use cases for a while 14:58:37 q+ 14:58:50 ack k 14:59:22 kaz: meanwhile we need to find a new TF lead and think about how to organize the calls 14:59:26 mm: yeah 14:59:57 mn: will you attend the security TF if you are not the TF lead 15:00:12 i/will you/scribenick: mahda-noura/ 15:00:15 mm: I have to decide which call has a higher priority 15:00:42 i/subtopic: Issue 231/scribenick: kaz/ 15:01:25 mn: Would it make sense to consolidate the security into other TF's 15:01:38 s/TF's/TF's?/ 15:02:21 mm: We could consolidate with other task forces like Architecture 15:02:59 (need further discussion anyway) 15:03:06 [adjourned] 15:03:10 rrsagent, draft minutes 15:03:11 I have made the request to generate https://www.w3.org/2024/01/15-wot-sec-minutes.html kaz 20:35:10 Zakim has left #wot-sec