11:58:48 RRSAgent has joined #wot-profile 11:58:48 logging to https://www.w3.org/2022/03/02-wot-profile-irc 11:59:17 McCool has joined #wot-profile 12:00:18 meeting: WoT Profile 12:00:25 present+ Kaz_Ashimura, Michael_McCool 12:02:25 Ege has joined #wot-profile 12:03:02 present+ Michael_Lagally 12:05:39 present+ Ege_Korkan 12:05:44 scribenick: kaz 12:05:52 Mizushima has joined #wot-profile 12:06:17 regrets+ Ben 12:06:19 present+ Tomoaki_Mizushima 12:06:23 topic: Agenda 12:06:35 -> https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#WoT_Architecture_.28Profile.29_-_March_2nd.2C_2022 agenda for today 12:06:46 Agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#WoT_Architecture_.28Profile.29_-_March_2nd.2C_2022 12:06:53 mm: (goes through the agenda) 12:07:35 regrets+ Sebastian 12:07:57 topic: Minutes 12:08:01 -> https://www.w3.org/2022/02/23-wot-profile-minutes.html Feb-23 12:08:57 ml: (goes through the minutes) 12:10:12 approved 12:10:34 topic: Implementation report 12:11:31 -> https://github.com/w3c/wot-profile/tree/main/testing wot-profile/testing 12:11:59 s|profile/testing|profile/testing/| 12:12:06 mm: creating a PR 12:12:11 ml: let's revisit later then 12:12:24 topic: Terminology 12:12:39 -> https://github.com/w3c/wot-profile/pull/180 Cleanup terminology 12:12:53 ml: some troubles with ReSpec about references 12:13:03 ... just fixed by this PR 12:13:25 (merged) 12:13:54 s/topic:/subtopic:/ 12:14:14 i/Terminology/topic: PRs/ 12:14:41 i|ull/180|subtopic: PR 180| 12:14:45 subtopic: PR 133 12:15:04 -> https://github.com/w3c/wot-profile/pull/133 PR 133 - Reinstating the Open Issues section 12:15:17 ml: is everybody happy to merge this? 12:16:32 ek: it's rather a section on "long-standing issues" than "open issues" 12:16:44 ... ok with "open issues", though 12:16:57 ml: ok, let's merge it 12:17:00 (merged) 12:17:23 subtopic: PR 118 12:17:38 -> https://github.com/w3c/wot-profile/pull/118 PR 118 - Remove redundant Accept headers - closes #113 12:17:49 ml: looks reasonable 12:18:28 -> https://pr-preview.s3.amazonaws.com/w3c/wot-profile/118/d51d816...benfrancis:c7b837c.html#writeproperty diff - 5.2.1.2 writeproperty 12:18:44 ml: (goes through the section 5.2.1.2 quickly) 12:18:46 ... any questions? 12:18:49 (none) 12:18:51 ml: ok 12:18:56 ... merging 12:18:59 (merged) 12:19:19 subtopic: PR 148 12:19:41 -> https://github.com/w3c/wot-profile/pull/148 PR 148 - Specify JSON serialisation of Problem Details Format - closes #142 12:19:54 ml: this is a clarification 12:19:59 ... fine with merging it 12:20:04 ... any comments? 12:20:06 (none) 12:20:08 (merged) 12:20:38 q+ 12:20:54 subtopic: PR 85 12:21:08 -> https://github.com/w3c/wot-profile/pull/85 PR 85 - Create echonetExampleTD.td.jsonld 12:21:17 ml: merge it or close it? 12:21:25 ek: no strong preference 12:22:08 kaz: have you got review from Matsuda-san, etc. for htis? 12:22:12 s/htis/this/ 12:22:41 ml: not yet 12:22:50 kaz: would be nicer to get a quick review from them 12:22:53 ml: good point 12:23:05 ... should ask them for review 12:27:29 ... (asks a review from Matsuda-san on the PR) 12:27:42 subtopic: PR 124 12:28:04 -> https://github.com/w3c/wot-profile/pull/124 PR 124 - Move and reword Security section 12:28:21 ml: (goes through "Files changed") 12:28:45 q? 12:28:46 ack k 12:29:58 mm: the sentence on Core Profile security to be split into two sentences 12:31:22 ... maybe we can add a review comment 12:31:41 ml: or we can merge this PR itself and create an additional issue/PR to modify it 12:33:34 mm: we could change this to "Security Considerations" and should add a "Privacy Considerations" 12:34:04 ... fine with merging this PR itself, though 12:34:33 ml: (creates a new issue for adding a new "Privacy Considerations" section) 12:35:56 s/creates a new issue for adding a new "Privacy Considerations" section/creates two new issues, one for "Security considerations" and another for "Privacy considerations"/ 12:36:18 -> https://github.com/w3c/wot-profile/issues/182 Issue 182 - New section: Security considerations 12:36:43 -> https://github.com/w3c/wot-profile/issues/183 Issue 183 - New Section: Privacy Considerations 12:36:57 subtopic: PR 124 12:37:20 s/subtopic: PR 124// 12:37:55 (merging PR 124, and got conflicts to solve) 12:38:33 (resolve the conflicts) 12:38:36 (merged) 12:41:46 subtopic: PR 181 12:42:22 -> https://github.com/w3c/wot-profile/pull/181 PR 181 - WIP: Implementation Report 12:43:00 ml: seems many lines have been removed... 12:43:07 mm: let me fix it... 12:43:15 (will revisit this later) 12:43:26 subtopic: PR 146 12:43:50 -> https://github.com/w3c/wot-profile/pull/146 PR 146 - Update references to WoT Thing Description 1.1 - closes #143 12:44:10 ml: some conflicts here 12:44:35 mm: should use the class attribute for assertion extraction 12:45:57 ml: this block with the id of "profile-abstract-2" doesn't include any RFC2119 keywords but has the class for them 12:46:03 mm: let's remove the class 12:47:02 ml: (fixes the problems) 12:49:04 topic: Event model 12:49:15 ml: there were questions during the previous call 12:49:37 [[ 12:49:38 do we need a single event model? 12:49:39 do all consumers have to implement all event models? 12:49:39 scalability requirements 12:49:39 implementability 12:49:40 ]] 12:49:50 s/do we/* do we/ 12:49:56 s/do all/* do all/ 12:50:04 s/scala/* scala/ 12:50:14 s/implemen/* implemen/ 12:50:21 rrsagent, make log public 12:50:27 rrsagent, draft minutes 12:50:27 I have made the request to generate https://www.w3.org/2022/03/02-wot-profile-minutes.html kaz 12:52:21 ml: and possible alternatives: 12:52:23 [[ 12:52:32 completely remove events from core profile 12:52:32 define 3 variants of core profile: core+SSE, core+longpoll, core+webhook 12:52:32 include 3 event mechanisms in core profile, make event support optional for consumers 12:52:32 mandate a single event model to be supported by all consumers 12:52:33 ]] 12:52:39 s/comp/1. comp/ 12:52:44 s/define/2. define/ 12:52:49 s/include/3. include/ 12:52:58 s/mandate/4. mandate/ 12:53:10 ml: we need McCool and Sebastian for this discussion 12:53:21 q+ 12:53:50 q+ 12:55:42 kaz: we should explain potential use cases and then think about which levels of the use cases to be covered by the current version WoT specs 12:55:59 ml: need to add new use cases to the use cases document? 12:56:23 kaz: it depends on whether the requirements are already covered or not 12:56:43 ml: think all the requirements are already covered by the existing use cases 12:56:57 ek: the question is which use cases to be prioritized 12:57:54 kaz: you can pick up some of the use cases and explain your need for the event handling 12:58:16 ek: right 12:58:42 ... we should see which level of event handling to be covered based on the existing concrete use cases 12:59:27 ml: ok, let's have concrete discussion then 12:59:44 [adjourned] 12:59:48 rrsagent, draft minutes 12:59:48 I have made the request to generate https://www.w3.org/2022/03/02-wot-profile-minutes.html kaz 13:00:18 chair: Lagally 13:00:19 rrsagent, draft minutes 13:00:19 I have made the request to generate https://www.w3.org/2022/03/02-wot-profile-minutes.html kaz 13:06:57 Mizushima has left #wot-profile 14:59:28 Zakim has left #wot-profile