14:04:29 <RRSAgent> RRSAgent has joined #wot-td
14:04:33 <RRSAgent> logging to https://www.w3.org/2023/03/15-wot-td-irc
14:04:35 <kaz> meeting: WoT-WG - TD-TF
14:05:03 <sebastian> sebastian has joined #wot-td
14:05:15 <luca_barbato> luca_barbato has joined #wot-td
14:05:35 <kaz> present+ Kaz_Ashimura, Daniel_Peintner, Ege_Korkan, Luca_Barbato, Sbastian_Kaebisch
14:05:40 <kaz> regrets+ Koster
14:06:01 <kaz> rrsagent, make log public
14:06:05 <kaz> rrsagent, draft minutes
14:06:06 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:06:45 <cris_> cris_ has joined #wot-td
14:06:47 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#March_15.2C_2023
14:07:35 <kaz> present+ Cristiano_Aguzzi
14:10:04 <luca_barbato> scribenick: luca_barbato
14:11:24 <sebastian> q+
14:11:32 <dape> s/Sbastian_Kaebisch/Sebastian_Kaebisch
14:11:51 <kaz> rrsagent, draft minutes
14:11:53 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:13:37 <kaz> topic: Minutes
14:13:46 <kaz> -> https://www.w3.org/2023/03/08-wot-td-minutes.html Mar-8
14:13:52 <kaz> rrsagent, draft minutes
14:13:54 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:14:00 <kaz> q+
14:14:00 <kaz> ack seb
14:15:05 <kaz> present+ Tomoaki_Mizushima
14:15:19 <luca_barbato> Sk: we should email the chair, the number of tasks regarding TD are getting larger and larger
14:16:17 <luca_barbato> ... we need at least two leaders
14:16:23 <kaz> s/Sk: we should email the chair, the number of tasks regarding TD are getting larger and larger/sk: would ask you all to think about joining the TF leader/
14:16:30 <kaz> q?
14:17:17 <luca_barbato> ege: check consensus for the past minutes
14:17:23 <luca_barbato> ... minutes approved.
14:18:09 <luca_barbato> topic: Task Force clarification
14:18:58 <luca_barbato> kaz: They are not bound to the charter document, and the FT leader/moderator can be decided later.
14:20:00 <cris_> q+
14:20:00 <kaz> s/clarification/leader clarification/
14:20:03 <kaz> ack k
14:20:13 <luca_barbato> ... we can have 3 moderators, Ege, Sebastian, ...
14:20:49 <dape> s/Ege, Sebastian, Koster
14:21:02 <dape> s/Ege, Sebastian, .../Ege, Sebastian, Koster
14:21:09 <luca_barbato> sebastian: The moderator requirements are to prepare the meeting and moderate them
14:21:17 <kaz> i|They are not bound to the charter document, and the FT leader/moderator can be decided later.|I'd like to provide some clarification on the procedure first. TF leader is not part of the Charter discussion. Also TF leader is not appointed by the WG Chair./
14:21:36 <kaz> rrsagent, draft minutes
14:21:38 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:22:29 <luca_barbato> chris: Wouldn't be better to to nominate separate responsible for sections of the TD?
14:22:47 <luca_barbato> ... e.g. 2 responsibles for the binding templates, 1 for profile, ...
14:22:49 <kaz> s/we can have/Choosing TF leader(s) is to be discussed by the TF itself like we chose Cristiano as an additional TF leader for Scripting API. We can simply report back to the main group later./
14:22:52 <kaz> rrsagent, draft minutes
14:22:53 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:23:19 <luca_barbato> q+
14:23:24 <kaz> s/later./later. If needed, we can have/
14:23:27 <kaz> rrsagent, draft minutes
14:23:28 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:23:35 <kaz> ack c
14:23:38 <kaz> q+
14:24:49 <luca_barbato> lb: We could have a list of topic first and then find moderators
14:25:11 <luca_barbato> ... and possibly have rotation on moderation if the workload is large enough to warrant it
14:26:13 <luca_barbato> kaz: we could discuss further when Koster is present
14:26:26 <luca_barbato> ... we should make sure that the moderators aren't from the same company
14:26:52 <luca_barbato> topic: Charter
14:27:17 <kaz> s|They are not bound to the charter document, and the FT leader/moderator can be decided later.|I'd like to provide some clarification on the procedure first. TF leader is not part of the Charter discussion. Also TF leader is not appointed by the WG Chair.|
14:27:45 <luca_barbato> ege: We do not have much left to say to discuss since most discussion already
14:28:08 <kaz> s|we should make sure that the moderators aren't from the same company|note that from my viewpoint, it would not be fair to have two moderators from one specific company.|
14:28:12 <luca_barbato> .. remaning items to discuss
14:28:15 <kaz> rrsagent, draft minutes
14:28:16 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:28:42 <luca_barbato> pull/88 -> repeating payload discussion
14:29:01 <luca_barbato> q+
14:29:02 <kaz> s/topic: Charter/topic: Charter-related topics/
14:29:07 <kaz> ack k
14:29:10 <kaz> rrsagent, draft minutes
14:29:12 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:30:42 <kaz> s/most discussion/most discussed/
14:31:06 <kaz> i|We do not|-> https://github.com/w3c/wot-charter-drafts/issues?q=is%3Aissue+is%3Aopen+label%3A%22WG+New+Charter+Plans+2023%22 Remaining issues|
14:31:16 <kaz> rrsagent, draft minutes
14:31:17 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:32:36 <Ege> https://github.com/w3c/wot-charter-drafts/pull/88
14:32:53 <kaz> s/https/-> https/
14:33:01 <kaz> s/88/88 PR 88 - Revised scope section, reordered, clarified language/
14:33:03 <kaz> rrsagent, draft minutes
14:33:04 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:33:41 <kaz> q+
14:33:41 <kaz> ack lu
14:34:20 <luca_barbato> kaz: clarification on what's about the PR
14:34:31 <kaz> rrsagent, draft minutes
14:34:32 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:34:38 <luca_barbato> ege: The change is just 1 line in the Charter document
14:34:58 <luca_barbato> subtopic: PR 78
14:35:00 <Ege> https://github.com/w3c/wot-charter-drafts/pull/78
14:35:05 <kaz> i|pull/88|subtopic: PR 88|
14:35:13 <kaz> s/https/-> https/
14:35:14 <cris_> +1
14:35:40 <luca_barbato> ege: The PR is about multimedia streaming, interested parties should comment on the PR
14:35:46 <kaz> s/78/78 PR 78 - Define Streaming and RTSP work items in Details/
14:35:56 <luca_barbato> subtopic: PR 59
14:36:18 <kaz> s/PR/Issue/
14:36:46 <kaz> -> https://github.com/w3c/wot-charter-drafts/issues/59 Issue 59 - Add composed Things work items
14:36:50 <cris_> q+
14:36:55 <kaz> ack k
14:37:03 <kaz> rrsagent, draft minutes
14:37:04 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:37:32 <kaz> s|pull/88 -> repeating payload discussion||
14:37:34 <kaz> rrsagent, draft minutes
14:37:35 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:37:43 <kaz> ack c
14:37:51 <luca_barbato> chris: What do we want to do, what are we missing?
14:38:54 <luca_barbato> one case we want to act upon the aggregate
14:38:58 <kaz> s/chris/cris/
14:39:06 <luca_barbato> ... one case we want to just signal the relationship
14:39:17 <kaz> s/one case/... one case/
14:39:20 <kaz> rrsagent, draft minutes
14:39:21 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:39:27 <luca_barbato> q+
14:39:37 <dape> q+
14:41:08 <kaz> ek: (shows Example 30 from the TD spec Editor's Draft)
14:41:18 <kaz> -> https://w3c.github.io/wot-thing-description/#example-an-electric-motor-is-member-of-the-electric-drive-collection Example 30 from TD
14:41:20 <Ege> ack l
14:41:34 <kaz> q+
14:42:07 <luca_barbato> lb: I'd like more clarification on this topic
14:42:20 <kaz> ack d
14:42:36 <luca_barbato> ege: We should see we have consensus on explore more on the next charter
14:43:52 <cris_> q+
14:44:00 <dape> ack dape
14:46:04 <cris_> ack c
14:46:06 <kaz> ack k
14:46:09 <luca_barbato> kaz: we should move the issue to the wot-thing-description repository
14:46:15 <luca_barbato> chris: +1
14:46:39 <dape> DP: allowing "group" interactions based on composed things sounds too much to me. Suppose an electric vehicle has several motors and a stop() interactions which then would need to be forwarded to "linked"  motors.  I don't think the TD should do that. A tool might do that though
14:46:49 <luca_barbato> topic: TD Testing
14:47:00 <kaz> s/we should/As already mentioned during the Charter call, this is not Charter issue but detailed work item for the next version of TD, so we should/
14:47:09 <kaz> s/move the issue/move this issue/
14:47:09 <luca_barbato> ege: many at-risk items in the TD are security assertions
14:47:20 <kaz> rrsagent, draft minutes
14:47:21 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:47:40 <luca_barbato> ... we should have the discussion in the next security call
14:48:13 <Ege> https://github.com/w3c/wot-testing/blob/main/events/2023.03.DevMtg/TD/atrisk-explanations.md
14:48:24 <luca_barbato> ... we should fill the document with our at risk items
14:48:25 <kaz> i/may at/subtopic: At-risk features/
14:48:50 <luca_barbato> ege: The deadline is 27th March
14:49:12 <luca_barbato> ... implementors are invited to participate
14:49:36 <luca_barbato> ... we will review the document next week
14:49:42 <kaz> s/we should fill/Also we should fill out/
14:49:50 <kaz> i/items/items above/
14:49:55 <kaz> rrsagent, draft minutes
14:49:56 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:50:02 <luca_barbato> topic: Binding Templates
14:50:42 <luca_barbato> subtopic: PR255
14:50:43 <Ege> https://github.com/w3c/wot-binding-templates/issues/255
14:50:49 <kaz> i/many at/subtopic: At-risk features/
14:50:51 <kaz> rrsagent, draft minutes
14:50:52 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:51:04 <kaz> s/risk items/risk items above/
14:51:05 <kaz> rrsagent, draft minutes
14:51:06 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:52:40 <luca_barbato> ege: The patch has the diagram
14:53:19 <luca_barbato> ... it explains the specific items of the Form
14:53:44 <sebastian> q+
14:53:45 <luca_barbato> q+
14:54:01 <luca_barbato> ... and how the requests flow looks like
14:54:16 <kaz> s/PR255/Issue 255/
14:54:37 <kaz> s/https/-> https/
14:54:45 <kaz> s/255/255 Issue 255 - A diagram to help understand what is happening in operation mappings./
14:54:47 <kaz> rrsagent, draft minutes
14:54:48 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
14:55:12 <cris_> +1 sebastian's comment
14:55:20 <dape> q+ to quotes in TD snippet
14:55:34 <luca_barbato> sebastian: looking forward to see the diagram
14:55:34 <kaz> q+
14:55:38 <kaz> ack s
14:55:40 <kaz> ack l
14:56:10 <luca_barbato> lb: png vs svg as medium in the document
14:56:17 <kaz> -> https://github.com/w3c/wot-binding-templates/pull/262 related PR 262 - Explain core binding mechanism
14:56:44 <dape> ack dape
14:56:44 <Zakim> dape, you wanted to quotes in TD snippet
14:57:04 <Ege> https://raw.githubusercontent.com/w3c/wot-binding-templates/ad5b7ac90e7e1b6a475d4c15db688659ea98d106/images/binding-mechanism.drawio.png
14:57:12 <kaz> s/https/-> https/
14:57:20 <kaz> s/png/png diagram preview/
14:57:46 <luca_barbato> ege: Shall we put the quotes in the snippet?
14:58:07 <luca_barbato> chris: It is not a valid json to begin with, not strong preference
14:58:12 <sebastian> q+
14:58:17 <kaz> ack k
14:58:19 <kaz> q+
14:58:59 <luca_barbato> sebastian: Would be nice to have more diagrams like this one
14:59:30 <luca_barbato> ege: We can make a requirement to add sequence diagrams in the protocol bindings
14:59:59 <kaz> ack s
15:00:04 <luca_barbato> ... we have some in the HTTP protocol binding
15:00:23 <luca_barbato> ... we can make sure to get the detail level not too deep
15:01:07 <luca_barbato> kaz: The TD snippet should be valid, we should add the quotes as needed
15:02:15 <luca_barbato> ... the diagram should have a paragraph describing the use-case related to it
15:02:43 <luca_barbato> s/use-case/application logic
15:03:21 <kaz> s/application logic/use case scenario/
15:03:37 <kaz> s/to it/to that/
15:04:44 <luca_barbato> sebastian: I would leave it as-is
15:05:33 <luca_barbato> kaz: I prefer the snippet to be valid even if it is a fragment
15:05:38 <luca_barbato> lb: +1
15:05:58 <luca_barbato> subtopic: Issue 252
15:05:58 <kaz> s/to be/being/
15:06:01 <McCool> McCool has joined #wot-td
15:06:22 <kaz> i/252/ek: ok. will fix it/
15:06:44 <luca_barbato> subtopic: PR 261
15:06:47 <Ege> https://github.com/w3c/wot-binding-templates/pull/261
15:06:56 <luca_barbato> ege: Fix ReSpec warnings
15:07:02 <kaz> i|261|-> https://github.com/w3c/wot-binding-templates/issues/252 Issue 252 - Mention that a binding is mandatory for a TD to exist|
15:07:28 <kaz> s/subtopic: PR 261//
15:07:36 <kaz> s/https/-> https/
15:08:01 <kaz> s/261/261 related PR 261 - Update ReSpec in ontology template/
15:08:07 <kaz> rrsagent, draft minutes
15:08:08 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
15:08:14 <luca_barbato> ege: Ok to merge?
15:08:19 <kaz> present+ Michael_McCool
15:08:22 <kaz> rrsagent, draft minutes
15:08:24 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
15:08:30 <luca_barbato> ... merged
15:08:50 <kaz> scribenick: kaz
15:09:02 <kaz> present+ Jan_Romann
15:09:05 <kaz> rrsagent, draft minutes
15:09:06 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
15:09:13 <kaz> q?
15:09:13 <kaz> ack k
15:09:26 <kaz> merged
15:09:39 <kaz> s/merged/(no objections)/
15:09:40 <kaz> merged
15:09:44 <kaz> rrsagent, draft minutes
15:09:46 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
15:10:08 <kaz> subtopic: PR 260
15:10:10 <Ege> https://github.com/w3c/wot-binding-templates/pull/260
15:10:19 <kaz> s/https/-> https/
15:10:29 <kaz> s/260/260 PR 260 - Use dct:creator instead of dct:author in ontologies/
15:10:37 <kaz> ek: any objections to merge?
15:10:39 <kaz> (none)
15:10:41 <kaz> merged
15:11:00 <kaz> subtopic: PR 263
15:11:02 <Ege> https://github.com/w3c/wot-binding-templates/pull/263
15:11:08 <kaz> s/https/-> https/
15:11:22 <kaz> s/263/263 PR 263 - Specifying terms influenced by different bindings/
15:11:26 <kaz> rrsagent, draft minutes
15:11:27 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
15:11:33 <JKRhb> JKRhb has joined #wot-td
15:11:53 <kaz> ek: (shows the preview)
15:12:36 <kaz> ... (describes the text and table under Example 5)
15:12:39 <luca_barbato> q+
15:12:39 <kaz> -> https://pr-preview.s3.amazonaws.com/w3c/wot-binding-templates/pull/263.html#example-subprotocol-usage-for-subscribing-events Example 5
15:13:30 <kaz> ek: this is still a draft, and would like to hear people's opinions
15:13:49 <kaz> lb: how are we going to specify which is correct href value?
15:14:04 <kaz> ek: if you see Modbus...
15:14:36 <kaz> -> https://w3c.github.io/wot-binding-templates/bindings/protocols/modbus/index.html#abnf Modbus URL ABNF Syntax
15:14:42 <kaz> bf: that seems to be risky...
15:15:21 <kaz> ... how to validate it?
15:16:08 <kaz> ... it could be a starting point, but we need further improvement
15:16:20 <cris_> q+
15:16:23 <dape> q+
15:16:36 <kaz> ... we have to figure out what socket to be used in this context
15:17:01 <kaz> ek: ideally the Consumer should pick one for their implementation
15:17:30 <kaz> ... if the choice was wrong, the configuration would be gone
15:17:45 <kaz> lb: would be better to specify the expectation
15:18:17 <kaz> ek: do you think asking the implementers to follow the ABNF notation is too much?
15:18:28 <kaz> lb: it would be risky
15:18:39 <JKRhb> rrsagent, draft minutes
15:18:40 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html JKRhb
15:19:08 <kaz> ... asking this in the Ontology would make sense
15:19:23 <kaz> q+
15:19:25 <kaz> ack lu
15:19:28 <kaz> ack c
15:19:30 <kaz> ca: agree
15:19:46 <kaz> ... don't see any Consumer implementations yet
15:20:16 <kaz> ... would be easier to follow the URL
15:20:23 <JKRhb> rrsagent, draft minutes
15:20:25 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html JKRhb
15:20:53 <kaz> ... the other point around registry
15:21:42 <kaz> dp: maybe you can show the table again...
15:22:07 <kaz> ... paragraph above the table says "keywords"
15:22:23 <kaz> ... also "Assignment" within the table seems to be odd
15:22:31 <kaz> ek: copied from the TD spec...
15:23:00 <kaz> dp: not sure about what term would be better, though
15:23:22 <kaz> s/"keywords"/"keywords" and "terms"/
15:23:24 <dape> ack dape
15:24:01 <kaz> ack k
15:25:27 <kaz> kaz: we should collect developer experience for binding with Modbus, etc.
15:26:18 <kaz> ... maybe a good topic for the possible Dev Meetup on Binding
15:26:28 <kaz> ek: ok
15:26:45 <kaz> ... would like to create an issue to remember this
15:27:20 <kaz> -> https://github.com/w3c/wot-binding-templates/issues/264 issue 264 - Get binding usage information from communities
15:27:52 <kaz> -> https://github.com/w3c/wot-binding-templates/pull/263#issuecomment-1470244570 Ege's comments on PR 263 based on the discussion
15:28:18 <kaz> rrsagent, draft minutes
15:28:19 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
15:29:14 <kaz> ek: (then goes through section 4.3)
15:29:25 <kaz> -> https://pr-preview.s3.amazonaws.com/w3c/wot-binding-templates/pull/263.html#platforms-intro preview - 4.3 Platform Binding Templates
15:29:52 <kaz> q+
15:31:25 <kaz> kaz: just to make sure, is there any clarification about the difference between "Protocol Binding" and "Platform Binding"?
15:32:20 <kaz> ek: yes, some text within the Introduction section
15:32:22 <kaz> kaz: ok
15:32:34 <kaz> ... remember we agreed on that text the other day
15:33:06 <kaz> ... but maybe it would be better to have that clarification text withing section 4 "Binding Template Mechanisms" itself?
15:33:17 <kaz> ek: right. can understand your point
15:33:40 <kaz> ... (creates another issue about that; to be done later)
15:33:51 <kaz> subtopic: PR 259
15:33:52 <Ege> https://github.com/w3c/wot-binding-templates/pull/259
15:34:16 <kaz> s/https/-> https/
15:34:29 <kaz> s/259/259 PR 259 - Rename CoAP blockwise parameters/
15:34:42 <kaz> jr: some discussion about the position
15:35:17 <kaz> -> https://github.com/w3c/wot-binding-templates/issues/256 related issue 256 - Rename cov:block2SZX to cov:block2Size
15:35:41 <kaz> jr: we could make this PR itself, and then I can add further improvement
15:36:37 <kaz> (this is updates for coap/coap.schema.json and coap/index.html)
15:36:44 <kaz> q+
15:37:28 <kaz> merged
15:37:39 <kaz> jr: will work on related PR 246
15:38:18 <kaz> ack k
15:38:51 <kaz> kaz: we won't talk about PR 246 itself today. right?
15:38:53 <kaz> ek: right
15:39:01 <kaz> subtopic: Issue 232
15:39:29 <kaz> -> https://github.com/w3c/wot-binding-templates/issues/232 Issue 232 - Next WD Path
15:39:36 <kaz> ek: our deadline is Mar 30
15:39:46 <kaz> ... would like to have more opinions around naming
15:40:17 <cris_> q+
15:40:17 <kaz> s/subtopic/topic/
15:40:20 <kaz> subtopic: Issue 243
15:40:26 <sebastian> q+
15:40:35 <luca_barbato> q+
15:40:46 <kaz> -> https://github.com/w3c/wot-binding-templates/issues/243 Issue 243 - Changing the Payload Bindings to Content Type Bindings
15:41:04 <kaz> mm: "Payload Bindings" would be clearer, I think
15:42:00 <kaz> ... "Payload" is more specific term than "Content Type"
15:42:16 <McCool> q?
15:42:42 <kaz> ca: could you elaborate the background a bit more, Ege?
15:42:45 <kaz> ack c
15:43:07 <kaz> sk: would agree with McCool
15:43:31 <kaz> ... "Content Type" sounds more generic to me
15:43:49 <kaz> ... "Payload" is to be exchanged for interaction
15:44:25 <kaz> ek: ok
15:44:32 <kaz> q+
15:44:36 <kaz> ack s
15:45:14 <kaz> ... we should see what different platforms do
15:45:27 <kaz> sk: we should clarify what is expected here
15:46:40 <kaz> ek: should go for platform discussion
15:47:36 <kaz> ... if the data schema with HUE or OCF goes in platforms, this change would make sense
15:47:40 <kaz> sk: right
15:47:50 <kaz> lb: should be able to look up the binding
15:48:24 <kaz> ... we have to make sure our expectation
15:48:38 <kaz> ek: Consumers would need to pick
15:49:56 <kaz> kaz: would agree with Luca's viewpoint
15:50:24 <cris_> q+
15:50:30 <kaz> ... we should clarify our expectation for binding first at the top of section 4
15:50:48 <kaz> ... protocol part and content part to be handle how
15:51:16 <kaz> ... then we should be able to choose which term would be the best, content or payload (or something else)
15:51:50 <kaz> lb: how to look up the content type and validate it?
15:52:10 <Ege> ack l
15:52:11 <Ege> ack k
15:52:17 <kaz> ... ack k
15:52:20 <kaz> s/... ack k//
15:52:33 <kaz> ack c
15:52:41 <kaz> ca: wanted to comment on the issue
15:52:53 <kaz> ... more aligned with what we started with
15:53:15 <kaz> ... we're now talking about how to serialize the information
15:53:21 <kaz> ... actual contentType content
15:53:53 <kaz> ek: would prefer making decision prior to the next publication
15:54:23 <kaz> ... McCool, do you still prefer "Payload Binding"?
15:54:55 <kaz> mm: if you all think "Content Type Binding", that's OK
15:54:57 <kaz> q+
15:55:50 <kaz> ack k
15:56:17 <kaz> kaz: is what we want really binding of "ContenType"?
15:56:27 <kaz> ... it implies "MIME Type" to people
15:56:59 <kaz> ... so if what we want is rather binding of the content as a whole, maybe it would be better to say "Content Binding" as Daniel mentioned
15:57:05 <kaz> mm: right
15:58:38 <kaz> lb: do we have examples on this kind of Binding (ContentType Binding/Payload Binding)?
15:58:42 <kaz> ek: yeah
15:59:52 <kaz> ... (shows the examples at Appendix B)
16:00:05 <kaz> -> https://pr-preview.s3.amazonaws.com/w3c/wot-binding-templates/pull/263.html#sec-payload-examples Appendix B. Examples of Payloads and Data Schemas from IoT Platforms and Standards
16:00:51 <kaz> ek: these are examples of SenML Payloads
16:01:10 <kaz> s/Payloads/Payload/
16:01:24 <kaz> s/these are examples/this is an example/
16:01:38 <sebastian> I have to go
16:01:39 <sebastian> bye
16:01:54 <kaz> lb: what if a payload using CBOR is transferred?
16:02:17 <kaz> ek: (shows example 6)
16:02:31 <kaz> -> https://pr-preview.s3.amazonaws.com/w3c/wot-binding-templates/pull/263.html#example-payload-binding Example 6 - JSON and CBOR media types in forms
16:02:43 <kaz> lb: what is the data schema for that?
16:02:50 <kaz> q+
16:03:23 <kaz> kaz: sorry but we're out of time
16:03:34 <kaz> ... so would suggest we continue the discussion next week
16:03:42 <Ege> https://github.com/w3c/wot-binding-templates/issues/226
16:04:03 <kaz> ek: ok
16:04:18 <kaz> ... note that there is a related issue 226 on "Platform Binding" as well
16:04:25 <kaz> [adjourned]
16:04:32 <kaz> rrsagent, draft minutes
16:04:33 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
16:05:20 <kaz> s/topic: Issue 232/topic: Issue 232 - Next WD Path/
16:05:22 <kaz> rrsagent, draft minutes
16:05:23 <RRSAgent> I have made the request to generate https://www.w3.org/2023/03/15-wot-td-minutes.html kaz
19:14:54 <Zakim> Zakim has left #wot-td