14:00:57 <RRSAgent> RRSAgent has joined #wot-td
14:01:01 <RRSAgent> logging to https://www.w3.org/2023/05/17-wot-td-irc
14:02:18 <luca_barbato> luca_barbato has joined #wot-td
14:03:09 <sebastian> sebastian has joined #wot-td
14:03:14 <dape> dape has joined #wot-td
14:03:38 <mjk> mjk has joined #wot-td
14:06:01 <Ege> https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#May_17.2C_2023
14:11:46 <cris_> cris_ has joined #wot-td
14:14:32 <kaz> meeting: WoT-WG - TD-TF
14:14:55 <kaz> present+ Kaz_Ashimura, Ege_Korkan, Daniel_Peintner, Luca_Barbato, Michael_Koster, Sebastian_Kaebisch
14:15:15 <sebastian> topic: minutes review
14:15:40 <kaz> scribenick: sebastian
14:15:58 <kaz> -> https://www.w3.org/2023/04/26-wot-td-minutes.html Apr-26
14:17:18 <kaz> present+ Cristiano_Aguzzi, Tomoaki_Mizushim
14:17:29 <kaz> present- Tomoaki_Mizushim
14:17:35 <kaz> present+ Tomoaki_Mizushima
14:18:18 <sebastian> Ege: any comments?
14:18:27 <sebastian> no
14:18:32 <sebastian> minutes approved
14:18:45 <sebastian> topic: Moderator
14:19:16 <Ege> https://lists.w3.org/Archives/Member/member-wot-wg/2023May/0002.html
14:19:16 <sebastian> Ege: the idea was to select a new moderator in today's call
14:19:22 <sebastian> ... there was also an email sent
14:19:33 <sebastian> q+
14:20:26 <sebastian> Ege: there can be multiple moderator
14:20:59 <kaz> s/moderator/moderators/
14:21:52 <kaz> q+
14:21:56 <kaz> ack s
14:23:35 <sebastian> SK: we should keep the mode until end of this charter
14:24:20 <sebastian> ... lets start a new moderators in new charter
14:24:31 <mjk> q+
14:25:06 <kaz> ack k
14:25:13 <kaz> kaz: @@@
14:25:31 <sebastian> Kaz: Siemens should official announce that Ege takeover moderation
14:25:42 <kaz> s/kaz: @@@/
14:26:05 <kaz> s/Siemens/If Ege is interested in becoming the TF moderator, Siemens/
14:26:09 <sebastian> ... Michael Koster is also intersthing in TF lead
14:26:19 <kaz> s/Michael/Note that Michael/
14:26:31 <kaz> s/interesting/interested/
14:27:08 <kaz> s/TF lead/becoming the TF lead. We could have two co-Moderators if needed, but we should clarify who to work on what./
14:28:18 <sebastian> MK: I'm working together with Siemens on the BACnet binding
14:29:13 <sebastian> ... there should be moderators from differen organizations
14:29:30 <sebastian> s/differen/different
14:29:52 <sebastian> Kaz: the current model is odd
14:30:13 <dape> q+
14:31:09 <sebastian> Ege: shall we decided now or in next charter?
14:31:18 <sebastian> MK: Im still interested in that role
14:31:34 <sebastian> Kaz, Im agree
14:31:45 <sebastian> :-)
14:32:20 <sebastian> Daniel: in scription having two moderators works quite well
14:32:30 <sebastian> q+
14:32:34 <kaz> ack mj
14:32:36 <kaz> ack da
14:32:38 <kaz> q+
14:33:57 <dape> s/scription/scripting
14:34:24 <sebastian> SK: agree, 2 moderators make sense. When we started TD work there were also 2 mderators: Taki and myself
14:34:42 <sebastian> s/mderators/moderators
14:36:38 <sebastian> Kaz: if sebastian busy currently, then Ege can takeover moderation and maybe togehter with Michael Koster
14:37:28 <sebastian> Ege:  So maybe then we can have a proposal to to continue like this to the end of the Charter and agree on 2 moderators
14:37:54 <kaz> s/the Charter/the current extended Charter/
14:38:23 <sebastian> MK: I could be a candidate
14:44:51 <kaz> q?
14:44:53 <kaz> ack s
14:44:55 <kaz> ack k
14:44:57 <kaz> q+
14:45:16 <sebastian> I cannot hear MK well
14:45:36 <sebastian> ok, I have connection problems
14:53:56 <kaz> kaz: don't really think we could get actual resolution today
14:54:33 <kaz> ... so would suggest both the candidate moderators think about the expected roles, e.g., technical spec descriptions and project management
14:55:25 <kaz> i/don't/scribenick: kaz/
14:55:34 <kaz> mjk: makes sense
14:56:31 <kaz> ek: one of the moderators mainly works on technical descriptions and another works on project management makes to me too
14:57:33 <sebastian> sebastian has joined #wot-td
14:58:21 <Ege> proposal: one moderator focuses on the technical text (the specification) and the other one does project management work such as keeping up with the timeline, relationships to other deliverables (dependencies)
14:59:20 <kaz> q+
14:59:26 <cris_> q+
15:00:20 <MIzushima> +1 kaz
15:00:26 <Ege> proposal: one moderator mainly works on the technical text (the specification) and the other one mainly does project management work such as keeping up with the timeline, relationships to other deliverables (dependencies). Both moderators keep sync with each other.
15:00:32 <kaz> ack k
15:01:52 <cris_> ack c
15:03:22 <MIzushima> q＋
15:03:43 <kaz> s/q＋//
15:03:47 <kaz> q+
15:04:19 <sebastian> TM: this resolution should only valid for this charter only
15:04:38 <kaz> s/only/period only/
15:05:03 <sebastian> ... next charter we should discuss again
15:05:41 <sebastian> s/charter only/charter
15:06:31 <sebastian> Kaz: to clearify TM statement, we should evaluate the working mode again in the new charter
15:06:58 <Ege> proposal: For this charter period, the TF decided that one moderator will mainly work on the technical text (the specification) and the other one mainly does project management work such as keeping up with the timeline, relationships to other deliverables (dependencies).
15:07:49 <kaz> rrsagent, make log public
15:07:52 <Ege> proposal: For this charter period, the TF decided that there will be two moderators. One moderator will mainly work on the technical text (the specification) and the other one mainly does project management work such as keeping up with the timeline, relationships to other deliverables (dependencies).
15:07:52 <kaz> rrsagent, draft minutes
15:07:54 <RRSAgent> I have made the request to generate https://www.w3.org/2023/05/17-wot-td-minutes.html kaz
15:08:08 <Ege> proposal: For this charter period, the TF decided that there will be two co-moderators. One moderator will mainly work on the technical text (the specification) and the other one mainly does project management work such as keeping up with the timeline, relationships to other deliverables (dependencies).
15:08:57 <Ege> resolution: For this charter period, the TF decided that there will be two co-moderators. One moderator will mainly work on the technical text (the specification) and the other one mainly does project management work such as keeping up with the timeline, relationships to other deliverables (dependencies).
15:09:25 <sebastian> Kaz: Im ok to put the names in the resolution itself
15:10:19 <sebastian> MK: propsal that Ege will do the work stream and myself the project management
15:10:25 <kaz> s/Im/I'm/
15:11:49 <Ege> proposal: For this charter period, the TF decided that there will be two co-moderators. Ege Korkan will mainly work on the technical text (the specification) and Michael Koster mainly does project management work such as keeping up with the timeline, relationships to other deliverables (dependencies).
15:12:54 <sebastian> EK: any objections?
15:12:57 <kaz> i/For/kaz: please note what is more important is the co-Moderators are encouraged to talk with each other closely about how to run the TF, and I'm happy to help you :)/
15:13:05 <Ege> resolution: For this charter period, the TF decided that there will be two co-moderators. Ege Korkan will mainly work on the technical text (the specification) and Michael Koster mainly does project management work such as keeping up with the timeline, relationships to other deliverables (dependencies).
15:13:06 <sebastian> no
15:13:24 <dape> DP: +1
15:13:47 <sebastian> MK: thanks
15:14:27 <sebastian> topic: TPAC
15:14:47 <sebastian> EK: we are collecting TD based topics here https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf/2023_WoT_TPAC_Agenda
15:15:35 <dape> q+
15:15:39 <kaz> ack k
15:15:41 <sebastian> q+
15:15:52 <kaz> s/topic: TPAC/topic: TPAC agenda/
15:16:04 <kaz> q+
15:16:07 <sebastian> EK: are there any topics to add so far?
15:16:09 <sebastian> q-
15:16:15 <dape> ack dape
15:17:22 <sebastian> DP: are the groups in Spain which we want to meet?
15:18:01 <sebastian> Kaz: we need to check the questionnaire
15:18:49 <kaz> -> https://www.w3.org/2002/09/wbs/1/GroupsTPAC2023/results TPAC questionnaire (Member-only)
15:18:53 <Ege> q?
15:18:57 <kaz> ack k
15:19:05 <sebastian> <EK enters deadline for contributions, 28.2023>
15:20:31 <kaz> s/check the questionnaire/check the questionnaire. It seems there will be at least the JSON-LD CG meeting, which may be combined with the JSON-LD WG meeting./
15:20:34 <sebastian> Kaz: it seems that we can have a meeting with Greg Kellog, he organize a meeting for the JSON-LD CG
15:20:38 <Ege> topic: Binding Templates
15:20:39 <Ege> https://github.com/w3c/wot-binding-templates/pull/286 and https://github.com/w3c/wot-binding-templates/pull/288
15:21:15 <kaz> q+
15:21:51 <sebastian> Ege: question to Kaz, if some help needed for the publication
15:23:16 <sebastian> Kaz: we did the resolution in today's main call. We need to run the W3C checking tools such as the Link checker
15:24:21 <dape> dape has left #wot-td
15:24:53 <sebastian> <Ege creates a new issue for the ToDos for publication>
15:25:15 <kaz> i/286/subtopic: Publication/
15:25:32 <sebastian> topic: Thing Description
15:25:58 <sebastian> EK: McCool generated a new version of the testing report
15:26:11 <sebastian> -> https://w3c.github.io/wot-thing-description/testing/report11.html
15:26:19 <kaz> i|Ege cre|-> https://github.com/w3c/wot-thing-description/blob/main/publication/ver11/4-wd/README.md guideline for publication instruction on wot-thing-description|
15:27:55 <Ege> https://github.com/w3c/wot-thing-description/pull/1800
15:27:59 <sebastian> EK: McCool is going to provide PRs to remove the remaining at-risk assertions
15:28:24 <sebastian> subtopic: PRs
15:28:47 <sebastian> s/subtopic: PRs/topic: TD PRs
15:29:04 <kaz> s/html/html Updated Implementation Report for TD/
15:29:06 <sebastian> subtopic: PR API Key for simple types
15:29:15 <sebastian> -> https://github.com/w3c/wot-thing-description/pull/1800
15:29:50 <kaz> s/1800/1800 PR 1800 - Mention apikey creation is only for object and arrays/
15:29:54 <kaz> scribenick: kaz
15:30:50 <kaz> merged
15:31:08 <kaz> s/subtopic: PR API Key for simple types/subtopic: PR 1800/
15:31:11 <kaz> subtopic: PR 1802
15:31:37 <kaz> -> https://github.com/w3c/wot-thing-description/pull/1802 PR 1802 - Fix html checker errors
15:32:39 <sebastian> +1
15:32:42 <kaz> q+
15:33:23 <JKRhb> JKRhb has joined #wot-td
15:33:36 <dape> dape has joined #wot-td
15:34:00 <JKRhb> rrsagent, draft minutes
15:34:02 <RRSAgent> I have made the request to generate https://www.w3.org/2023/05/17-wot-td-minutes.html JKRhb
15:35:05 <kaz> ek: need to add edits to the TTL files
15:35:57 <kaz> ack k
15:36:59 <kaz> merged
15:37:04 <kaz> subtopic: PR 1790
15:37:31 <kaz> -> https://github.com/w3c/wot-thing-description/pull/1790 PR 1790 - Editorial fixes for issue 1735
15:37:39 <kaz> ek: (shows the changes)
15:37:54 <kaz> q+
15:39:25 <kaz> ack k
15:39:57 <kaz> kaz: note that we should be very careful to add any changes at this stage, because we had already published a Candidate Recommendation
15:40:00 <kaz> ek: yeah
15:40:10 <kaz> ... completely editorial and typo fixes
15:42:41 <kaz> ... also added clarification for a term definition "Levels of a TD" which is also non-normative
15:42:44 <kaz> kaz: ok
15:43:10 <Ege> q?
15:44:00 <kaz> kaz: btw, what is the cause of the validation error for the PR 1790?
15:44:22 <kaz> -> https://github.com/w3c/wot-thing-description/actions/runs/4810341640/jobs/8562830297?pr=1790 validation error
15:45:12 <kaz> ek: can be still merged
15:45:14 <kaz> merged
15:45:55 <kaz> s/can be/bug within the SHACL definition. can be/
15:46:04 <kaz> subtopic: PR 1687
15:46:28 <kaz> s/1687/1820/
15:46:46 <kaz> -> https://github.com/w3c/wot-thing-description/pull/1820 PR 1820 - Add semantic annotation def and use it
15:46:59 <kaz> ek: (shows the diff)
15:47:54 <kaz> ... Sebastian has fixed the problem
15:47:56 <kaz> merged
15:48:03 <kaz> subtopic: PR 1821
15:48:28 <kaz> -> https://github.com/w3c/wot-thing-description/pull/1821 PR 1821 - Extend proxy-to description
15:48:45 <kaz> ek: (shows the changes)
15:49:40 <kaz> merged
15:49:50 <kaz> subtopic: PR 1822
15:50:14 <kaz> -> https://github.com/w3c/wot-thing-description/pull/1822 PR 1822 - Explain multiple inputs
15:51:40 <kaz> kaz: do you still want to wait for Zoltan's feedback?
15:52:10 <kaz> ek: yes, he generated the original issue 913
15:52:19 <sebastian> I have already to go. Bye
15:52:43 <kaz> -> https://github.com/w3c/wot-thing-description/issues/913 Issue 913 - Improve the text on Action parameters (vs input)
15:53:25 <kaz> subtopic: PR 1823
15:53:38 <kaz> -> https://github.com/w3c/wot-thing-description/pull/1823 PR 1823 - Remove manually added rfc classes
15:55:15 <kaz> ek: would like to wait for McCool as well
15:55:39 <kaz> ... but it seems there is mixed syntax for the RFC keywords
15:56:06 <kaz> ... one generated by ReSpec, and another manually generated for the CSS setting
15:56:43 <kaz> kaz: I'm OK with automatic generation by ReSpec but we should be consistent about how to handle the CSS setting for the RFC keywords
15:56:45 <kaz> ek: agree
15:58:33 <kaz> ... it seems the actual difference is [[title="MUST"]]
15:59:06 <kaz> ... the line generated by ReSpec doesn't have [[title="MUST"]] attribute
15:59:23 <kaz> q?
15:59:43 <kaz> q+
16:00:28 <kaz> kaz: However, I'm afraid it's rather a bug of ReSpec in that case...
16:00:29 <kaz> ack k
16:02:06 <kaz> ... maybe we need to look into the other WG's HTML as well to see how ReSpec works with ordinary HTML
16:03:10 <kaz> ek: yeah, would like to look into the other specs as well to see what is happening with them
16:04:03 <kaz> kaz: yeah, checking our own tooling and also what's happening with the the other WG's HTMLs would make sense
16:04:17 <kaz> [adjourned]
16:04:25 <kaz> rrsagent, draft minutes
16:04:26 <RRSAgent> I have made the request to generate https://www.w3.org/2023/05/17-wot-td-minutes.html kaz
16:04:54 <kaz> chair: Ege
16:04:56 <kaz> rrsagent, draft minutes
16:04:57 <RRSAgent> I have made the request to generate https://www.w3.org/2023/05/17-wot-td-minutes.html kaz