14:54:24 <RRSAgent> RRSAgent has joined #wot-td
14:54:24 <RRSAgent> logging to https://www.w3.org/2022/01/19-wot-td-irc
14:54:39 <McCool> McCool has joined #wot-td
14:54:56 <kaz> meeting: WoT-WG - TD-TF
14:55:02 <kaz> present+ Kaz_Ashimura
15:04:27 <dape> dape has joined #wot-td
15:04:45 <JKRhb> JKRhb has joined #wot-td
15:05:24 <kaz> present+ Daniel_Peintner, Jan_Romann, Michael_McCool, Sebastian_Kaebisch, Tomas_Jaeckle
15:06:12 <kaz> present+ Michael_Lagally
15:06:39 <kaz> q+
15:06:45 <kaz> q-
15:07:00 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#Jan_19.2C_2022
15:07:35 <sebastian> topic: new member
15:07:56 <sebastian> Bosch joined the WoT group yesterday
15:08:17 <sebastian> Thomas Jäckle representing Bosch in WoT
15:08:22 <kaz> present+ Cristiano_Aguzzi
15:08:30 <sebastian> Thomas: hi everyone
15:08:56 <sebastian> ... I'm contributing to the Eclipse Ditto project
15:09:24 <sebastian> ... currently working on integration of WoT in Ditto. Using the Thing Model approach e.g.
15:09:51 <kaz> q+
15:10:31 <kaz> ack k
15:11:08 <thomas_jaeckle> thomas_jaeckle has joined #wot-td
15:13:29 <sebastian> topic: minutes check
15:13:37 <sebastian> check minutes from Dec 15
15:13:47 <sebastian> https://www.w3.org/2021/12/15-wot-td-minutes.html
15:20:01 <sebastian> McCool will check this issue https://github.com/w3c/wot-thing-description/issues/1211
15:21:39 <kaz> rrsagent, make log public
15:21:43 <kaz> rrsagent, draft minutes
15:21:43 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/19-wot-td-minutes.html kaz
15:21:49 <sebastian> any objections?
15:21:55 <sebastian> no
15:22:16 <sebastian> next minutes from last week
15:22:20 <sebastian> https://www.w3.org/2022/01/12-wot-td-minutes.html
15:22:24 <kaz> i/Bosch jo/scribenick: Sebastian/
15:22:44 <kaz> i/scribenick: Sebastian/scribenick: sebastian/
15:22:46 <kaz> rrsagent, draft minutes
15:22:46 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/19-wot-td-minutes.html kaz
15:23:09 <kaz> chair: Sebastian
15:23:43 <kaz> present+ Michael_Koster, Tomoaki_Mizushima
15:27:06 <sebastian> any comments, objections?
15:27:08 <sebastian> q?
15:27:10 <sebastian> no
15:27:51 <sebastian> topic: Webhook
15:28:27 <sebastian> ML: happy to have Bosch onboard
15:29:55 <sebastian> ML: let me give the background again
15:30:15 <sebastian> ... everything what has an interface a TD can be designed
15:30:19 <kaz> present+ Ege_Korkan
15:31:01 <sebastian> ... its mainly works for IP based connections
15:31:34 <kaz> i|happy to|-> https://github.com/w3c/wot-thing-description/issues/1323 Issue 1323 - Missing event/notification affordance or operation|
15:31:44 <sebastian> ... a servient is a combination of a consumer and provider
15:32:44 <sebastian> ... everything is a Thing and the TD describes the Things' interface
15:33:07 <sebastian> ... we have properties, actions and events
15:33:25 <sebastian> ... for event affordance we get notifications
15:34:19 <sebastian> <ML shows the place of the EventAffordance definition in the TD spec>
15:34:28 <sebastian> https://w3c.github.io/wot-thing-description/#eventaffordance
15:35:38 <sebastian> ... a consumer Thing do a subscription
15:36:22 <sebastian> ... consumer gets notify if values are changed
15:37:23 <sebastian> ... if there is a battery powered device it can not open the network the full time
15:38:30 <Ege> q+
15:38:31 <sebastian> ... a consumer register a listener at a Thing
15:38:44 <McCool> q+
15:39:18 <sebastian> ... we have TD for the consumer which is part of the event mechanism
15:39:22 <McCool> ack m
15:39:32 <McCool> q+
15:40:21 <sebastian> ... we need a kind of callback functionality for the event affordances
15:40:49 <sebastian> ... its an abstract model without specific protocol
15:41:06 <cris> cris has joined #wot-td
15:41:25 <sebastian> q+
15:41:38 <cris> q+
15:42:01 <sebastian> ... it would be good to have a notify in the event affordances
15:42:12 <mlagally___> mlagally___ has joined #wot-td
15:42:35 <sebastian> Ege: I'm agree with the use case
15:42:45 <sebastian> ... however, it is very protocol driven use case
15:43:39 <sebastian> ... TD needs 2 kind of consumer
15:44:09 <kaz> s/I'm agree/I agree/
15:44:16 <sebastian> ML: sounds to complicated which seems not needed
15:44:31 <sebastian> ... only one TD is needed
15:45:17 <sebastian> Ege: with notify it is pushed to the listener that was registered
15:45:48 <kaz> s/Things' interface/Thing's interface/
15:46:20 <kaz> s/... a consumer Thing/ML: a consumer Thing/
15:46:58 <sebastian> ML: the registration can a TD which would be a solution
15:47:13 <kaz> s/its an/it's an/
15:47:26 <kaz> q+
15:48:06 <sebastian> ML: TD spec is silent where I have to provide the listener information, e.g.
15:48:17 <kaz> ack ege
15:50:24 <sebastian> McCool: What I understood so far, there is missing information to initalize and execute Webhook based affordance
15:50:50 <sebastian> s/affordance/interaction
15:51:39 <sebastian> ML: shows the PR with a proposal
15:51:54 <sebastian> https://github.com/w3c/wot-thing-description/pull/1329
15:53:48 <sebastian> ack M
15:54:06 <sebastian> McCool: looks ok for me this kind of approach
15:54:38 <sebastian> Ege: Im wondering how the forms look like
15:55:02 <sebastian> ... would be good to have TD example
15:55:20 <sebastian> ML: ok I will take this action
15:56:18 <kaz> q?
15:57:13 <sebastian> ML: dataresponse is the response of the data notification
15:57:52 <sebastian> ... I need to go
15:58:21 <kaz> q?
15:58:35 <sebastian> McCool: lets continue this discussion in the issue and do discussion next week again
15:59:53 <McCool> q+
16:00:26 <kaz> -> https://pr-preview.s3.amazonaws.com/w3c/wot-thing-description/1329/21ce84a...6a563db.html#eventaffordance diff version from PR 1329 - 5.3.1.5 EventAffordance
16:01:39 <sebastian> ack s
16:02:09 <sebastian> Seb: Im ok with the dataresponse, however, not sure about the op type "notify"
16:02:25 <sebastian> Chris: Im not sure about the use case which is ML looking for
16:03:15 <kaz> s/Im/I'm/
16:04:23 <kaz> q?
16:04:28 <kaz> ak cris
16:04:32 <kaz> s/ak cris//
16:04:33 <kaz> ack c
16:04:33 <sebastian> ... by definition I'm not a consumer of the TD anymore as a consumer, it is also a producer
16:04:57 <kaz> s/anymore/any more/
16:06:32 <Ege> +1 for kaz
16:06:47 <kaz> ack k
16:06:54 <sebastian> Kaz: We need a detailed use case description
16:08:02 <sebastian> McCool: I'm concerned about duplicated definitions if TD is used to define the target resources
16:08:17 <sebastian> ... we need to understand more a practical use case
16:08:27 <kaz> s/description/description with concrete device setting, data transfer and interaction protocols, and should ask Michael Lagally to work on that. Then we can talk about what is needed based on that./
16:08:39 <sebastian> ack M
16:09:24 <sebastian> ... however, I understand this main intention of the use case
16:09:43 <sebastian> Chris: If you understand this use case why we cannot use a simple protocol for this?
16:13:47 <sebastian> McCool: we need only an action that uses the notify op
16:15:28 <dape> q?
16:15:33 <sebastian> ... however, issue came very late, needs more clearification
16:16:07 <dape> s/clearification/clarification
16:16:34 <kaz> q+
16:16:39 <sebastian> topic: publication plans
16:17:12 <sebastian> made resolution about publication the 2nd WD
16:17:45 <sebastian> ... in the main call
16:18:15 <kaz> s/made re/sk: made re/
16:18:18 <sebastian> Kaz: will work on the publication. Maybe next week will be ready, however, depends on issue which may arrise
16:18:32 <kaz> s/issue/issues/
16:19:35 <kaz> s/Maybe next week will be ready/would expect it'll be ready next week.
16:19:43 <kaz> s/arrise/arise/
16:20:26 <kaz> i/made resolution/subtopic: 2nd WD/
16:21:05 <kaz> i/subtopic: Updated schedule/
16:21:44 <kaz> s|i/subtopic: Updated schedule/||
16:21:54 <kaz> subtopic: Updated schedule
16:22:05 <kaz> -> https://github.com/w3c/wot/pull/1010/files proposed updates
16:22:14 <kaz> subtopic: Wide reiews
16:22:19 <sebastian> I will start to do the wide review process until end of this week for the TD spec
16:22:29 <kaz> s/I will/sk: I will/
16:22:40 <kaz> s/reiews/reviews/
16:22:42 <sebastian> topic: check PRs
16:24:16 <sebastian> subtopic: #1282
16:24:17 <sebastian> https://github.com/w3c/wot-thing-description/pull/
16:24:22 <sebastian> decided not to merge
16:25:26 <sebastian> subtopic: #1317
16:25:31 <sebastian> https://github.com/w3c/wot-thing-description/pull/1317
16:25:36 <kaz> q+
16:26:03 <sebastian> will be addressed until CR transition
16:26:47 <kaz> kaz: btw, we do need a change log section from the previous WD for the 2nd WD publication
16:27:12 <kaz> sk: good question. need to talk with Taki
16:27:51 <kaz> i/btw/subtopic: Change log for the 2nd WD/
16:28:00 <kaz> i/btw/scribenick: kaz/
16:28:03 <sebastian> subtopic: #1319
16:28:07 <kaz> scribenick: sebastian
16:28:08 <sebastian> https://github.com/w3c/wot-thing-description/pull/1319
16:31:10 <sebastian> decided to merge. Has no impact on the TD spec itself
16:32:38 <sebastian> subtopic: #1327
16:32:42 <sebastian> https://github.com/w3c/wot-thing-description/pull/1327
16:33:00 <sebastian> I need to check this PR before decided to merge
16:33:14 <sebastian> Daniel: we should be careful about this fix namespaces
16:33:44 <sebastian> add discussion label
16:35:00 <sebastian> subtopic: #1328
16:35:05 <sebastian> https://github.com/w3c/wot-thing-description/pull/1328
16:35:19 <sebastian> Kaz: this file was used for publication in the past
16:35:24 <sebastian> ... is not needed anymore
16:35:34 <kaz> s/anymore/any more/
16:36:01 <sebastian> decided to merge
16:41:34 <kaz> subtopic: #1342
16:41:45 <sebastian> https://github.com/w3c/wot-thing-description/pull/1342
16:41:52 <sebastian> needs further discussions
16:43:32 <sebastian> topic: TD Issues
16:43:42 <sebastian> Clarifications on readmultipleproperties and writemultipleproperties / writeallproperties
16:43:51 <sebastian> https://github.com/w3c/wot-thing-description/issues/1349
16:54:53 <kaz> i/Clarifications/subtopic: #1349/
16:55:02 <kaz> subtopic: #1357
16:55:09 <kaz> https://github.com/w3c/wot-thing-description/issues/1357
17:02:58 <kaz> q+
17:04:01 <kaz> (continue the discussion next week)
17:04:03 <kaz> ack k
17:04:31 <kaz> topic: Binding
17:04:52 <kaz> sk: let's discuss wot-binding-templates issue 144 next week
17:04:55 <kaz> [adjourned]
17:04:59 <kaz> rrsagent, draft minutes
17:04:59 <RRSAgent> I have made the request to generate https://www.w3.org/2022/01/19-wot-td-minutes.html kaz
20:08:04 <Zakim> Zakim has left #wot-td