13:01:15 RRSAgent has joined #wot-discovery 13:01:19 logging to https://www.w3.org/2023/12/11-wot-discovery-irc 13:01:25 Mizushima has joined #wot-discovery 13:02:41 ktoumura has joined #wot-discovery 13:03:51 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Discovery_WebConf#11_December_2023 13:08:09 no too many people here - have a short meeting only, but need to wait for kaz to come back 13:08:34 scribenick: McCool 13:08:41 topic: minutes 13:09:11 -> https://www.w3.org/2023/12/04-wot-discovery-minutes.html Dec-4 13:09:24 chair: McCool 13:10:07 present+ Kaz_Ashimura, Michael_McCool, Kunihiko_Toumura, Tomoaki_Mizushima 13:11:30 mm: minutes were approved, after typo fix 13:12:10 scribenick: kaz 13:12:14 topic: Logistics 13:12:28 mm: Discovery meeting next week on Dec 18 is cancelled 13:12:43 ... also cancellations due to holidays 13:13:08 ... the next call is Jan 15 13:13:13 topic: Resources 13:13:23 mm: right now, we have a placeholder HTML 13:13:27 ... it's good for now 13:13:46 ... but we need to get registered with the DID registry 13:14:13 ... need to coordinate with the TD repo as well 13:14:25 ... have to get volunteers for that purpose next year 13:14:41 ... myself will concentrate on the DID registry issue 13:15:04 ... will make sure it will happen 13:15:59 ... (adds a link for did-spec-registries/pull/486) 13:16:23 -> https://github.com/w3c/did-spec-registries/pull/486/files link for did-spec-registries PR 486 13:16:25 rrsagent, make log public 13:16:29 rrsagent, draft minutes 13:16:30 I have made the request to generate https://www.w3.org/2023/12/11-wot-discovery-minutes.html kaz 13:16:52 mm: seems there is some conflict now... 13:17:13 meeting: WoT Discovery 13:17:15 mm: seems there is some conflict now... 13:17:20 s/mm: seems there is some conflict now...// 13:17:21 rrsagent, draft minutes 13:17:22 I have made the request to generate https://www.w3.org/2023/12/11-wot-discovery-minutes.html kaz 13:18:03 ... once the fix is done, can get published 13:18:25 topic: Planning 13:18:35 subtopic: Use Cases and Requirements 13:18:47 mm: getting good shape but need go be reviewed 13:19:07 ... probably need some re-organization 13:19:29 ... but have clarified topics on Discovery 13:19:53 ... need to send an email to the whole WG 13:20:29 ... to be sent to the IG? 13:20:31 s/WG/group/ 13:20:43 kaz: the Use Cases and Requirements document itself is done by the IG 13:21:01 ... on the other hand, the use case topics are related to Discovery done by WG 13:23:12 ... so you can send the review request to both the IG and the WG 13:23:17 mm: what about the CG? 13:23:48 kaz: technically, if CG Members would like to give reviews for an IG document, they should join the public-wot-ig mailing list 13:23:53 mm: that's true 13:24:01 ... would talk with Ege about that 13:24:13 rrsagent, draft minutes 13:24:14 I have made the request to generate https://www.w3.org/2023/12/11-wot-discovery-minutes.html kaz 13:25:48 JKRhb has joined #wot-discovery 13:28:14 present+ Jan_Romann 13:28:14 q+ 13:28:37 q- 13:28:49 kaz: do you expect to get reviews by those who provided use cases but possibly still non-Members as well? 13:28:52 mm: right 13:29:35 rrsagent, draft minutes 13:29:37 I have made the request to generate https://www.w3.org/2023/12/11-wot-discovery-minutes.html kaz 13:30:50 kaz: btw, you might want to send it to public-wot-ig and public-wot-wg instead of the Member lists :) 13:30:53 mm: ok 13:30:57 q? 13:31:57 (review request sent out) 13:32:36 ... ideally all the contributors should subscribe this public-wot-ig list 13:33:21 rrsagent, draft minutes 13:33:23 I have made the request to generate https://www.w3.org/2023/12/11-wot-discovery-minutes.html kaz 13:33:32 topic: Resources - revisited 13:33:55 (discussion on how to generate HTML descriptions from the TTL ontologies) 13:34:23 mm: at the moment, good placeholder 13:34:38 ... but would be great if we could get your help, Jan 13:34:46 jr: which ontology? 13:34:58 mm: only one ontology for WoT Discovery 13:35:07 q+ 13:35:57 kaz: in that case, I'd suggest Michael create an Issue describing which TTL file to be converted to what kind of HTML file 13:36:08 ... then Jan could work on that to help you 13:36:11 mm: ok 13:39:16 q+ 13:39:51 ack k 13:40:09 ... what we do is 13:40:24 ... 1. update the HTML content 13:40:35 ... 2. replace the HTML in wot-resources 13:40:58 https://github.com/w3c/wot-usecases/issues/252 13:42:03 mm: or maybe 3-step approach 13:42:17 kaz: in that case, you should mention "what to be done at which repository how" 13:42:40 mm: ok 13:43:21 ... 1. set up the script to generate the HTML from TTL on wot-discovery 13:43:41 ... 2. update the HTML to reflect the actual content of the TTL file on wot-discovery 13:43:54 ... 3. replace the HTML on wot-resources 13:45:14 s|https://github.com/w3c/wot-usecases/issues/252|| 13:46:00 -> https://github.com/w3c/wot-discovery/issues/533 Issue 533 - Update HTML for Discovery ontology 13:48:51 q+ 13:49:31 topic: Status 13:49:48 mm: would create some more issues on wot-use-cases 13:50:05 kaz: I can understand the current situation and the difficulty of how to manage the use case calls at the moment 13:50:23 ... however, technically, WoT Use Cases discussion is done by the WoT IG 13:50:49 ... and some of the IG-only participants might want to join the discussion too 13:51:08 ... so we should think about how to hold the use cases discussion in a broader manner 13:51:29 mm: yeah 13:51:38 ... let me create an issue on the wot-discovery side first 13:53:02 s/on the wot-discovery side first// 13:53:33 -> https://github.com/w3c/wot-usecases/issues/253 wot-usecases Issue 253 - Update Status of each Discovery Requirement 13:54:10 https://github.com/w3c/wot-discovery/issues/534 13:54:31 s|https://github.com/w3c/wot-discovery/issues/534|-> https://github.com/w3c/wot-discovery/issues/534 wot-discovery Issue 534 - Link Work Items to Requirements in UC&R document| 13:54:43 q+ 13:55:23 topic: Resources - revisited 13:55:49 kaz: btw, wot-discovery issue 533, which was created during this call, and an older one Issue 524 are identical. right? 13:56:03 https://github.com/w3c/wot-discovery/issues/509 13:56:16 i|509|-> https://github.com/w3c/wot-discovery/issues/533 Issue 533 - Update HTML for Discovery ontology| 13:56:56 i|509|-> https://github.com/w3c/wot-discovery/issues/524 Issue 524 - Generate HTML file for ontology/discovery-core.ttl| 13:57:22 s|https://github.com/w3c/wot-discovery/issues/509|-> https://github.com/w3c/wot-discovery/issues/509 Issue 509 - Create and Publish an Ontology File for DID Vocabulary| 13:57:29 mm: Issue 509 also 13:57:34 ... (closes 509 and 524) 13:58:16 -> https://github.com/w3c/wot-discovery/issues/515 Issue 515 - Publish Context and Ontology 13:58:24 mm: 515 can be also closed 13:58:27 https://github.com/w3c/wot-discovery/issues/524 13:58:59 https://github.com/w3c/wot-discovery/issues/518 13:59:02 s|https://github.com/w3c/wot-discovery/issues/524|| 13:59:41 s|https://github.com/w3c/wot-discovery/issues/518|-> https://github.com/w3c/wot-discovery/issues/518 Issue 518 - Publish JSON Schema for TDD at stable URL| 13:59:48 mm: 518 also can be closed 14:00:18 topic: Next call 14:00:23 mm: will be Jan 15 14:00:26 [adjourned] 14:00:51 rrsagent, draft minutes 14:00:52 I have made the request to generate https://www.w3.org/2023/12/11-wot-discovery-minutes.html kaz 14:01:11 mahda-noura has joined #wot-discovery