15:05:44 RRSAgent has joined #wot-td 15:05:44 logging to https://www.w3.org/2022/11/30-wot-td-irc 15:05:53 meeting: WoT-WG - TD-TF 15:06:37 present+ Kaz_Ashimura, Ege_Korkan, Bjoern_Kaemper, Cristiano_Aguzzi, Daniel_Peintner, Jan_Romann, Klaus_Hartke, Michael_Koster 15:07:12 scribenick: mjk 15:07:24 topic: Guest 15:07:39 -> https://www.w3.org/Consortium/Patent-Policy-20200915/ W3C Patent Policy 2020 15:08:11 ege: introducing Bjorn Kamper and reminder about the patent policy 15:08:36 q+ 15:08:56 dape has joined #wot-td 15:09:09 bk: agrees to the patent policy and introduces himself 15:09:53 kaz: reminder that the words in this call may be used as part of a W3C specification and need to agree on this point 15:09:58 bk: agreed 15:11:10 bk: has projects around information modeling and communication protocols 15:11:35 bk: working on administration shell and OPC-UA 15:12:08 ... created OPC companion specs for pumps and compressors 15:13:17 ... interested in the BACnet binding for automated creation of monitoring points from information models 15:14:03 q? 15:14:04 ack k 15:14:12 agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#November_30.2C_2022 15:14:48 rrsagent, make log public 15:14:52 rrsagent, draft minutes 15:14:52 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 15:16:49 mk: to clarify that TD will map diverse protocols to a common information model 15:16:50 q+ 15:17:06 q+ 15:17:12 bk: yes, IS is the common information model 15:17:22 s/IS/AS 15:18:21 kaz: will you use the protocol binding to adapt to different protocols? 15:18:38 s/will you use/are you using/ 15:18:45 bk: yes, we base this on experience with the modbus binding 15:19:08 q+ 15:19:13 ack k 15:19:14 ack e 15:19:20 q+ 15:19:44 ege: do you (Bjorn) want to contribute to the specification as an author? 15:19:57 bk: yes, as needed 15:21:10 ack k 15:21:59 ege: other questions? 15:22:16 topic: review minutes from last week 15:22:31 s/ege: do you (Bjorn) want to contribute to the specification as an author?// 15:22:39 s/bk: yes, as needed// 15:23:35 rrsagent, make log public 15:23:40 rrsagent, draft minutes 15:23:41 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 15:24:49 Bkaemper has joined #wot-td 15:25:18 ege: any comments or changes? 15:25:20 q+ 15:25:41 JKRhb has joined #wot-td 15:26:15 ege: we need to correct the initials of some people, minutes approved 15:26:32 topic: binding template PRs 15:27:07 PR #209, template for binding templates 15:27:30 kh: this is a starting point based on the original issue #144 15:27:56 s/on the/examples in the 15:28:30 q+ 15:28:35 ack k 15:28:35 ack k 15:29:10 kh: we need to respect the BACnet copyright and check for usage rules 15:29:49 ack e 15:29:58 ege: does anyone know what the guideline is? 15:29:58 q+ 15:30:54 kh: the best outcome is to have BACnet people involved and contributing 15:31:28 kaz: we need to look at the charter and see what we should include in the W3C document 15:31:59 i|PR #209|subtopic: PR 209| 15:32:01 i|PR #209|subtopic: PR 209| 15:32:13 kh: for example, we need to describe the URL format, which is described in the ASHRAE document 15:32:29 s|subtopic: PR 209|-> https://github.com/w3c/wot-binding-templates/pull/209 PR 209 - BACnet Binding| 15:32:37 rrsagent, make log public 15:32:37 ... best would be to get ASHRAE to register the URI scheme with IAMA and make it public 15:32:40 rrsagent, draft minutes 15:32:40 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 15:32:53 q? 15:32:53 q? 15:32:54 ack k 15:32:58 q+ mjk 15:34:06 ackm 15:34:09 ack m 15:34:29 mjk: we also need to look at vocabulary and payload binding 15:35:04 s/the W3C document/the W3C document. I don't think copying the content, which is defined by the other SDO, to the Binding Templates document and publish it using the W3C WG Note CSS is included./ 15:35:15 rrsagent, draft minutes 15:35:15 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 15:35:48 ege: is Joel Bender the correct contact? 15:35:55 q+ 15:36:18 mk: what is the question to Joel? 15:36:38 ege: collaborate on the URI scheme and vocabulary 15:37:39 kaz: we spoke with Joel earlier in the year, but we should, as a group, think more about how we work with these external resources and clarify our needs 15:37:57 ... and it should be done in the context of an official liaison afgreement 15:38:07 s/afgreement/agreement 15:39:15 sebastian has joined #wot-td 15:39:15 q+ 15:39:28 s/agreement/agreement, at least a simple liaison./ 15:39:30 ack k 15:39:33 Mizushima has joined #wot-td 15:39:35 q+ 15:40:25 sk: our charter does have a provision for interacting with external organizations around binding templates 15:40:55 kaz: we need to have more discussion and get beyond the abstract charter 15:41:21 ege: OK, we will schedule that discussion 15:41:57 ege: review the updated and simplified binding templates document 15:42:16 s/review/subtopic: review/ 15:43:05 ... please review and see if we can merge the updates next week 15:43:07 q+ 15:43:12 ack k 15:43:14 ack s 15:43:16 ack c 15:43:30 q? 15:43:33 i|OK, we|-> https://www.w3.org/2022/07/wot-wg-2022.html current WoT WG Charter| 15:43:40 cris: looks good, will review and provide feedback 15:44:04 sub-topic: content negotiation for CoAP 15:44:11 rrsagent, make log public 15:44:15 rrsagent, draft minutes 15:44:15 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 15:44:54 i|any comments or|-> https://www.w3.org/2022/11/23-wot-td-minutes.html Nov-23| 15:45:17 ege: Jan has updated the document 15:45:17 s/ackm// 15:45:52 s/ege: subtopic:/subtopic:/ 15:45:55 rrsagent, draft minutes 15:45:55 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 15:45:55 ege: discussion of the use of the accept option 15:46:03 q? 15:46:08 ... any comments or questions? 15:46:38 kh: didn't have time to look at the changes, but looks good except for the missing table entry 15:46:56 ... if Jan will update and send to Klaus, he will review and approve 15:47:21 ege: if no further objections, we will merge on Klaus' approval 15:47:34 proposal: merge PR 193 once Klaus Hartke gives positive review 15:47:51 i|please review|-> https://github.com/w3c/wot-binding-templates/pull/198 PR 198 - Overview of the binding templates documents and relationship with others| 15:48:00 RESOLUTION: Merge PR 193 once Klaus Hartke gives positive review 15:48:52 q+ 15:49:02 https://github.com/w3c/wot-binding-templates/pull/211 15:49:14 ege: subtopic: PR #211, remove link to the CoAP ontology 15:49:52 ack k 15:49:59 rrsagent, draft minutes 15:49:59 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 15:50:01 ege: any objections? 15:50:08 ...merged 15:50:32 subtopic: PR #183, Modbus design 15:51:16 ege: we have already discussed, are there any further comments? 15:51:54 i|Jan has up|-> https://github.com/w3c/wot-binding-templates/pull/193 PR 193 - Alternative proposal for handling CoAP Content-Formats 15:52:15 cris: it looks like everything is addressed 15:52:24 s/ege: subtopic: PR #211/subtopic: PR #211/ 15:52:29 rrsagent, draft minutes 15:52:29 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 15:52:41 s|https://github.com/w3c/wot-binding-templates/pull/211|| 15:53:12 i|any objections|-> https://github.com/w3c/wot-binding-templates/pull/211 PR 211 - Remove ontology link from coap| 15:53:16 rrsagent, draft minutes 15:53:16 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 15:53:55 i|we have already|-> https://github.com/w3c/wot-binding-templates/pull/183 PR 183 - feat(modbus): move addres and quantity to URL components| 15:53:57 rrsagent, draft minutes 15:53:57 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 15:54:01 ... there is some work to support a future subscription mechanism that doesn't impact this PR 15:55:39 ege: we should track this and see what the requirement to support is 15:56:16 q+ 15:56:30 ege: there is a general question about non-IP protocols 15:56:59 ege: is there a need to identify observable properties vs. polling? 15:57:18 cris: there are issues about programming the sample rate, etc. 15:57:20 present+ Sebastian_Kaebisch 15:57:28 ... there needs to be an abstraction 15:57:29 chair: Ege/Sebastian 15:57:29 rrsagent, draft minutes 15:57:29 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 15:58:26 cris: we should think the modbus case through 15:59:11 kaz: we need to think about the general use case across different protocols 16:00:10 ... both the abstraction and the concrete translation requirements 16:00:17 q? 16:00:23 ack k 16:01:07 ... for example, the payload mapping for BACnet 16:03:08 ege: interesting to think about where the consumer functions need to go in the WoT specifications 16:03:59 subtopic: PR #210, CODEOWNERS to automate review requests 16:06:05 kh: owners should also have permission to write 16:06:17 ack k 16:06:20 rrsagent, draft minutes 16:06:20 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 16:06:24 q+ 16:06:59 i|owners|-> https://github.com/w3c/wot-binding-templates/pull/210 PR 210 - Create CODEOWNERS| 16:07:15 ege: authors should be code owners 16:07:34 q? 16:08:01 ack k 16:08:08 kaz: do we really need this? 16:09:02 ege: the reasons are automation and transparency 16:09:25 mk: the automation would be helpful for me 16:10:29 ege: the automation would help because we have a lot of documents 16:10:50 kaz: we still need to have leads keep track of the process 16:10:54 q+ 16:11:25 dape: is write access necessary? 16:11:47 ack dape 16:11:53 s/access/access for code owners/ 16:11:58 q+ 16:13:04 ack c 16:13:45 q+ 16:14:00 q? 16:14:14 kh: it looks like write access is required to make code owners work 16:14:56 kaz: we could give editors write permission through the editors team 16:15:11 ack k 16:15:12 kh: then all team members would get all review requests 16:15:46 seb: I have the ability to change the settings as needed 16:16:29 ege: the action needed is to add Klaus and Cristiano to the editors team 16:16:59 kaz: I can do that 16:17:16 https://github.com/w3c/wot-binding-templates/pull/212 16:17:17 action: kaz to give Klaus and Cristiano write permission for wot-binding-templates 16:17:17 Sorry, but no Tracker is associated with this channel. 16:18:55 subtopic: how to use @context for vocabularies 16:19:29 q+ 16:19:30 ege: this is done by example but not specified 16:20:36 cris: is it a question of specifying the IRI? 16:21:20 s|https://github.com/w3c/wot-binding-templates/pull/212|| 16:21:34 i|this is done|-> https://github.com/w3c/wot-binding-templates/pull/212 PR 212 - Add context and vocabulary requirement| 16:21:37 ege: it's needed to resolve references 16:21:48 q+ 16:21:50 ack c 16:22:03 cris: can we allocate the IRIs for each vocabulary? 16:22:03 ack c 16:22:11 ege: yes, we need to publish these 16:22:37 ack k 16:24:09 kh: we need specific instructions 16:24:24 ege: creating a follow-up issue #216 for this 16:24:29 q? 16:24:40 ege: any more comments? 16:24:51 ... merged 16:25:34 q+ 16:25:35 kh: has permission to merge now 16:26:32 present+ Tomoaki_Mizushima 16:26:38 rrsagent, draft minutes 16:26:40 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 16:27:18 kaz: we should be careful about the policy now, so we avoid accidental merges 16:27:33 ack k 16:27:50 https://github.com/w3c/wot-binding-templates/issues/205 16:28:33 topic: schemas for protocol binding templates 16:28:56 +1 16:29:03 ege: proposing to include a schema with a protocol binding, please review issue #203 16:29:24 s|https://github.com/w3c/wot-binding-templates/issues/205|| 16:29:40 s/#203/#205 16:29:46 i|+1|-> https://github.com/w3c/wot-binding-templates/issues/205 Issue 205 - JSON Schemas of Protocol Binding Templates| 16:29:51 topic: TD 16:29:52 rrsagent, draft minutes 16:29:52 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 16:30:10 q+ 16:32:02 ack k 16:34:21 ege: the CR request has been sent to W3M 16:34:28 q+ 16:34:48 ... there is still an issue of API keys in JSON payloads 16:35:53 s/sent to W3M/issued on the transition repository/ 16:35:56 ack k 16:37:08 ege: there seems to be an old pattern that we may not need to support 16:37:14 q+ 16:37:18 s/CR request/CR Transition Request/ 16:37:48 ack dape 16:37:59 i|the CR|subtopic: CR Transition| 16:38:08 dape: this is also being reviewed in the security team 16:38:27 i|the CR|-> https://github.com/w3c/transitions/issues/467 transitions issue 467 - CR Request for Web of Things (WoT) Thing Description 1.1| 16:39:52 subtopic: new charter items, PR #1033, please review and propose items for discussion next week 16:40:16 i|there seems|-> https://w3c.github.io/wot-thing-description/#security-apikey 6.3.4.5 API key usage| 16:40:16 s/PR/issue/ 16:41:06 subtoipc: PR for ordering assertions as they appear in the specification 16:41:31 seb: we agreed to do this 16:41:38 ege: merged 16:41:39 rrsagent, draft minutes 16:41:39 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 16:42:05 https://github.com/w3c/wot-thing-description/pull/1733 16:42:40 ege: please review and prepare for discussion 16:43:06 https://github.com/w3c/wot-thing-description/issues/1135 16:43:12 subtopic: issues labeled to be closed 16:43:30 seb: start with the oldest 16:43:31 s/, please review and propose items for discussion next week// 16:44:56 ege: issue #1135 - closed 16:44:57 q+ 16:45:04 https://github.com/w3c/wot-thing-description/issues/1177 16:45:36 ack k 16:45:49 ege: issue #1177 - composition vs. inheritance 16:46:21 ... there are examples of composition in the TD 1.1 document 16:46:29 seb: agree 16:46:30 i|please review|-> https://github.com/w3c/wot/pull/1033 wot PR 1033 - Create new charter items for TD| 16:46:34 rrsagent, draft minutes 16:46:34 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 16:46:58 ege: closed 16:47:13 s/subtoipc:/subtopic:/ 16:47:15 rrsagent, draft minutes 16:47:15 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 16:47:16 https://github.com/w3c/wot-thing-description/issues/1267 16:47:22 rrsagent, draft minutes 16:47:22 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 16:47:37 ege: issue # 1267, W3C logo 16:47:48 q+ 16:48:33 ack k 16:48:57 kaz: we can ignore this, as the public version doesn't have the issue 16:49:16 ege: closed 16:49:20 i/PR for ordering ass/ege: lease review and propose items for discussion next week/ 16:49:23 https://github.com/w3c/wot-thing-description/issues/1280 16:51:52 q+ 16:51:59 https://github.com/w3c/wot-thing-description/issues/1350 16:52:08 q? 16:52:57 ack k 16:53:25 mjk_ has joined #wot-td 16:53:34 (back) 16:53:39 i|we agreed to do this|-> https://github.com/w3c/wot-thing-description/pull/1752 PR 1752 - Update Implementation Report (Indexing)| 16:53:48 rrsagent, draft minutes 16:53:48 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 16:53:58 ege: issue #1280 closed 16:54:20 https://github.com/w3c/wot-usecases/pull/197 16:54:35 ege: issue #1350 - use case documents for TD and protocol binding 16:55:18 seb: we can review at the use case call next week 16:55:47 ege: OK 16:56:00 https://github.com/w3c/wot-thing-description/issues/1413 16:56:14 ege: issue #1413 - available language/locale 16:57:41 seb: there was another issue that was closed in i18n 16:58:47 ege: closed 16:59:22 https://github.com/w3c/wot-thing-description/issues/1497 16:59:41 ege : issue #1497 - identifiers don't rotate enough 17:00:07 ... security has reviewed and proposed closing 17:00:32 ... closed 17:00:50 q+ 17:00:52 ege: we are out of time today, is there any other business 17:01:29 ... none, adjourned 17:14:20 rrsagent, draft minutes 17:14:20 I have made the request to generate https://www.w3.org/2022/11/30-wot-td-minutes.html kaz 19:29:04 Zakim has left #wot-td 20:48:48 JKRhb has joined #wot-td