14:08:15 RRSAgent has joined #wot-td 14:08:19 logging to https://www.w3.org/2023/07/26-wot-td-irc 14:08:54 Kazeem has joined #wot-td 14:09:38 mahdanoura_ has joined #wot-td 14:23:32 chair: Ege_Korkan, Michael_Koster 14:23:52 Meeting: WoT Thing Description 14:25:35 s/WoT Thing Description/WoT-WG - TD-TF/ 14:26:40 present+ Kaz_Ashimura, Ege_Korkan, Kazeem, Mahda_Noura, Sebastian_Kaebisch, Jan_Romann, Michael_Koster 14:29:25 topic: Minutes Review 14:29:27 scribenick: kazeem 14:29:52 -> https://www.w3.org/2023/07/19-wot-td-minutes.html July-19 14:29:56 q+ 14:31:03 Kaz: meeting reviews should be sent out sfor review so that we wont to review the meeting during the call 14:31:21 s/sfor/for/ 14:32:18 Kaz: one week before the next meeting 14:32:22 Ege: ok... 14:33:49 s/meeting reviews should be sent out for review so that we wont to review the meeting during the call/We had some discussion during the main call about minutes review. The proposal there was sending out the draft minutes for review beforehand and avoiding detailed review during the calls./ 14:34:18 JKRhb has joined #wot-td 14:34:19 s/ok.../We've not got resolution about that proposal, so let's review the TD minutes for today./ 14:34:21 Ege: minutes approved 14:34:35 rrsagent, draft minutes 14:34:37 I have made the request to generate https://www.w3.org/2023/07/26-wot-td-minutes.html JKRhb 14:34:52 rrsagent, make log public 14:34:54 i/minutes approved/kaz: For today, that's fine. Let's see the main call resolution next week./ 14:35:20 Ege: should meetings in August be less or stays the same since it will be holiday period 14:36:04 i/For today/scribenick: kaz/ 14:36:33 i/approved/scribenick: Kazeem/ 14:36:35 Kaz: week of August 14 should be considered 14:36:40 rrsagent, make log public 14:36:44 rrsagent, draft minutes 14:36:45 I have made the request to generate https://www.w3.org/2023/07/26-wot-td-minutes.html kaz 14:37:09 i/should meetings/topic: Schedule/ 14:37:10 rrsagent, draft minutes 14:37:12 I have made the request to generate https://www.w3.org/2023/07/26-wot-td-minutes.html kaz 14:38:52 Ege: Aug 2: Yes, August 9th: maybe, August 16th:No, August 23rd: yes, August 30th: maybe. 14:39:19 s/:No/: No/ 14:40:05 present+ Kazeem_Oladipupo 14:40:10 present- Kazeem 14:40:13 rrsagent, draft minutes 14:40:14 I have made the request to generate https://www.w3.org/2023/07/26-wot-td-minutes.html kaz 14:40:26 present+ Tomoaki_Mizushima 14:40:26 rrsagent, draft minutes 14:40:27 I have made the request to generate https://www.w3.org/2023/07/26-wot-td-minutes.html kaz 14:40:51 topic: Thing description 14:41:11 i/Thing/topic: Binding Templates/ 14:41:30 i/Thing/ek: Kaz is working on publication./ 14:41:40 i/Kaz is/scribeick: kaz/ 14:41:45 scribenick: Kazeem 14:42:16 mjk has joined #wot-td 14:42:44 subtopic: PR 1858 14:42:55 -> https://github.com/w3c/wot-thing-description/pull/1858 PR 1858 - Remove mention of atrisk section 14:43:25 subtopic: PR 14:43:26 q? 14:44:12 Kaz: both file should be fixed 14:44:40 Ege: yes. 14:45:13 s/both file/both files (.ttl and .html)/ 14:45:16 proposal: The TD Task Force agrees to merge https://github.com/w3c/wot-thing-description/pull/1858 14:46:02 resolution: The TD Task Force agrees to merge https://github.com/w3c/wot-thing-description/pull/1858 14:46:14 Ege: resolution made 14:47:05 subtopic PR 1859 14:47:51 proposal: The TD Task Force agrees to merge https://github.com/w3c/wot-thing-description/pull/1858 after getting approval of PLH 14:48:16 resolution: The TD Task Force agrees to merge https://github.com/w3c/wot-thing-description/pull/1858 after getting approval of PLH 14:48:21 Kaz: the resoulution should be merged after getting approval of PLH 14:48:22 s/Ege: resolution made// 14:48:26 Ege: ok 14:48:37 s/subtopic PR 1859// 14:49:22 Ege: does not change specification text so it shold be ok to merge? 14:49:23 subtopic: PR 1859 14:49:27 q( 14:49:29 s/q(// 14:49:30 q+ 14:49:39 s/subtopic: PR 1859// 14:49:46 i|does not|subtopic: PR 1859| 14:51:48 i|does not|-> https://github.com/w3c/wot-thing-description/pull/1859 PR 1859 - Render at-risk warning only if note is "at risk" 14:52:07 Kaz: index.html should not be touched if PR 1859 will be merged now 14:52:39 s/if PR 1859 will be merged now/if we want to merge PR 1859 now/ 14:52:50 rrsagent, draft minutes 14:52:51 I have made the request to generate https://www.w3.org/2023/07/26-wot-td-minutes.html kaz 14:52:58 subtopic PR 1856 14:53:22 -> https://github.com/w3c/wot-thing-description/pull/1856 PR 1856 - Start documenting NAMESPACES 14:54:13 Ege: the link should not point to master branch. 14:56:39 ... current setup makes versioning impossible. 14:57:24 q+ 14:57:24 ...question to Kaz are we able to put a jsonld file into TD 1.0 version? 14:57:36 Kaz: it depends how to show the resource to vendors 14:59:15 ...we can redirect any URL from WoT to github, this method needs to be thought about. 14:59:42 Ege: we are suing the method already. 15:00:59 Kaz: let sumarrise the current status 15:02:01 Ege: suggests we use publication folder 15:02:32 s/let sumarrise the current status/Before proposing concrete alternative directly, please once summarize the current situation, and then requirements for what to be done ideally for each version of TD spec, 1.0, 1.1 and 2.0./ 15:05:03 scribenick: kaz 15:05:20 Ege: this Pullrequest 1856 itself creates a MD for that purpose 15:05:54 kaz: In that case, I'd suggest we merge this PR so that we can have further discussion based on the MD 15:06:18 ... putting various comments on the PR itself would not be useful for this kind of issue 15:06:33 ... because we need to clarify what is happening first 15:08:29 q+ 15:09:33 ack k 15:10:37 present+ Cristiano_Aguzzi 15:12:39 +1 15:12:53 sebastian has joined #wot-td 15:13:10 kaz: let's merge this PR 1856 itself, and have further discussion based on the MD 15:13:20 (PR 1856 merged) 15:13:32 subtopic: PR 1859 15:13:34 q? 15:13:36 q+ 15:13:53 ack k 15:14:30 scribenick: mjk 15:14:56 ege: any objections to merge PR #1859? 15:15:10 ... merged 15:15:38 topic: planning 15:16:12 ege: 2 PRs regarding planning to review 15:16:20 subtopic: PR 1111 15:16:26 i|any o|-> https://github.com/w3c/wot-thing-description/pull/1859 PR 1859 - Render at-risk warning only if note is "at risk"| 15:16:46 s/subtopic: PR 1859/subtopic: PR 1859 - revisited/ 15:16:52 ege: reorganize the planing document 15:17:12 s/#1859?/#1859 after removing the changes to index.html?/ 15:17:22 rrsagent, draft minutes 15:17:24 I have made the request to generate https://www.w3.org/2023/07/26-wot-td-minutes.html kaz 15:18:35 ... any opinions? please review and we can discuss next week 15:18:57 s/PR 1111/wot PR 1111/ 15:19:19 i|reor|-> https://github.com/w3c/wot/pull/1111 wot PR 1111 - Reorganize TD work items| 15:19:20 q+ 15:19:26 subtopic: PR #1112 - summarizing historical data on a work item 15:21:14 -> https://github.com/w3c/wot/pull/1112 wot PR 1112 - Historical data landscape 15:21:15 kaz: it would be useful to review the message from Michael Koster from last week 15:21:30 s/subtopic: PR #1112/subtopic: wot PR #1112/ 15:21:38 https://lists.w3.org/Archives/Member/member-wot-wg/2023Jul/0006.html 15:21:47 q+ 15:22:14 ack k 15:22:41 mjk: what we're doing here is following McCool's basic proposal made during the main call 15:22:50 ... use cases for work item to be discussed first 15:23:05 ... also requirements drive the work items 15:23:15 ... we need to collect use cases and describe them 15:23:32 ... then clarify requirements for particular items 15:23:41 ... Ege and I talk about this idea 15:24:24 ... Ege has started some PRs but still useful to think about how to collect use cases as well 15:24:38 ek: yeah 15:25:03 ... initial proposals listed on the "Landscape of Historical Data Work Item" document within wot PR 1112 15:25:36 s/last week/last week as the basis before diving into the PRs./ 15:25:43 s/basis/basis for today/ 15:25:49 q? 15:25:52 ack c 15:26:02 ca: think so 15:26:42 ... btw, what about the structure of the folders? 15:26:52 q? 15:26:54 q+ 15:29:15 ack k 15:29:20 q+ 15:32:32 kaz: sorry but I'm a bit confused 15:32:36 mjk: also a bit confused 15:32:47 ... we're trying to clarify use case management 15:33:03 ... which would turn into requirements and then work items 15:33:15 ... should not duplicated the work 15:33:30 ... but should follow the discussion during the main call 15:33:52 ... this document still can list the work items, though 15:34:43 ... all the use cases listed here are already made by people 15:35:08 ... we could evaluate the proposals 15:35:57 ... still could have a MD document describing the work items instead of solution world 15:36:03 s/world/spaces/ 15:36:10 ... we can stick on use cases 15:36:48 q? 15:36:50 ack m 15:36:51 q+ 15:38:30 q+ 15:38:32 kaz: given Ege has created PR 1112, this consolidated resource list itself is fine, but should be merged with McCool's proposals on use case management 15:38:54 ... on the other hand, TD TF should concentrate on the work items described by PR 1111 15:39:15 mjk: the question is what to be discussed during this TD-TF call 15:39:27 ... we have many work items already 15:39:48 ... 6 big items 15:39:56 q? 15:39:58 ack k 15:40:25 q+ 15:40:29 ack mjk 15:41:04 sk: we planned to have this planning discussion only for July 15:41:17 ... next week, we should have only the main call 15:41:40 ... we should use the whole 2-hour slot for new Charter prep 15:41:54 ... no reason not to use this time for that purpose 15:42:07 ... all the topics for the new Charter 15:42:10 ack s 15:43:13 kaz: not proposing that we limit the meeting to one hour, but rather to follow McCool's process ongoing 15:43:39 ... each TF handling of the use case discussion is unclear 15:44:19 q+ 15:44:20 ... each TF can work on concrete requirements discussion, but we need clarification on the main call 15:44:33 ack k 15:45:01 ege: question for Kaz, should we go into the use case discussion? 15:45:39 kaz: the discussion should proceed with McCool in the main call about the generic use case process, then in the individual TFs 15:45:43 q? 15:46:14 ... this PR should be on the main call agenda as feedback from the TD task force 15:46:21 q+ 15:47:08 kaz: individual MD files can be merged as the basis for starting the discussion 15:47:58 kaz: suggest we merge 1111 as general instructions and take 1112 to the main call 15:48:40 ege: we can look at it from the use case starting point or the work item starting point 15:49:17 kaz: TD TF should not get into the detail of the use case discussion but bring it to the main call 15:49:48 ack e 15:49:50 ack m 15:50:03 mjk: in this call, we can take our work items 15:50:17 ... and list use cases within separate MDs 15:50:40 ... then bring it to the main call as example of use case management 15:50:50 ... to have broader discussion by the whole WoT WG 15:51:09 +1 for kaz and mjk 15:51:13 ... once we have requirements for specs, each TF can continue to work on that 15:51:29 ack mjk 15:51:42 ... getting feedback on that during the planning session of the main call 15:51:49 ... check the format, what to do, etc. 15:52:18 q+ 15:53:20 ek: think TD TF participants are experts on the possible requirements... 15:54:50 kaz: The "Landscape" document is kind of "Explainer", I think 15:55:00 ... so we can change the title to "Explainer" 15:55:22 ... and bring this to the main call as an example for the use case management discussion 15:55:25 ek: ok 15:55:31 q? 15:55:32 ack k 15:55:58 [adjourned] 15:56:02 rrsagent, draft minutes 15:56:03 I have made the request to generate https://www.w3.org/2023/07/26-wot-td-minutes.html kaz 15:57:09 i/what we're doing/scribenick: kaz/ 15:57:10 rrsagent, draft minutes 15:57:12 I have made the request to generate https://www.w3.org/2023/07/26-wot-td-minutes.html kaz 15:58:28 i/not proposing/scribenick: mjk/ 15:58:28 rrsagent, draft minutes 15:58:29 I have made the request to generate https://www.w3.org/2023/07/26-wot-td-minutes.html kaz 16:00:22 i/in this call,/scribenick: kaz/ 16:00:25 rrsagent, draft minutes 16:00:26 I have made the request to generate https://www.w3.org/2023/07/26-wot-td-minutes.html kaz 16:04:26 s/scribeick/scribenick/ 16:04:26 rrsagent, draft minutes 16:04:27 I have made the request to generate https://www.w3.org/2023/07/26-wot-td-minutes.html kaz 19:33:49 Zakim has left #wot-td