10:57:15 <RRSAgent> RRSAgent has joined #wot
10:57:19 <RRSAgent> logging to https://www.w3.org/2023/02/16-wot-irc
10:57:26 <kaz> meeting: 2nd WoT WG Charter Meeting - Day 3
10:59:36 <kaz> present+ Kaz_Ashimura, Michael_McCool
10:59:53 <McCool> McCool has joined #wot
11:01:47 <kaz> present+ Ege_Korkan
11:03:23 <ktoumura> ktoumura has joined #wot
11:05:11 <cris_> cris_ has joined #wot
11:06:18 <kaz> present+ Cristiano_Aguzzi, Kunihiko_Toumura, Michael_Koster, Sebastian_Kaebisch
11:07:26 <mlagally> mlagally has joined #wot
11:08:13 <kaz> present+ Michael_Lagally
11:08:29 <kaz> rrsagent, make log public
11:08:33 <kaz> rrsagent, draft minutes
11:08:34 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
11:08:56 <kaz> q+
11:09:59 <kaz> chair: McCool
11:10:11 <kaz> q-
11:11:34 <kaz> topic: Scribes
11:11:38 <kaz> Cristiano and Ege
11:12:03 <cris_> topic: PR list
11:12:11 <cris_> mc: in order from easy to difficult
11:12:16 <McCool> https://github.com/w3c/wot-charter-drafts/pull/44
11:12:19 <cris_> subtopic: PR 44
11:12:30 <cris_> mc: should be straightforward
11:12:44 <cris_> ... add one line about collaboration for geolocation
11:12:52 <kaz> q+
11:12:53 <cris_> ... any objections?
11:13:15 <cris_> kaz: there still some old PRs in the old repository
11:13:25 <kaz> q-
11:13:30 <cris_> mc: we'll get back to it, adding it into the agenda
11:13:48 <kaz> s/PR list/Review Issues, PRs and Status/
11:13:59 <cris_> mc: back to the PR any objections?
11:14:00 <kaz> i/in order/scribenick: cris_/
11:14:02 <cris_> ... ok merge it
11:14:11 <kaz> rrsagent, draft minutes
11:14:13 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
11:14:31 <cris_> ... if you see a group missing re-open issue 27 and add it
11:14:51 <kaz> i/Cristiano and Ege/scribenick: kaz/
11:15:06 <kaz> s/subtopic: PR 44//
11:15:16 <kaz> i|pull/44|subtopic: PR 44|
11:15:19 <kaz> rrsagent, draft minutes
11:15:20 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
11:15:38 <kaz> s/there still/there are still/
11:15:40 <cris_> ... we decided to not mention horizontal review group
11:16:11 <cris_> ... but the charter still contains two groups, do we keep them?
11:16:14 <kaz> i|in order from|-> https://w3c.github.io/wot-charter-drafts/wot-wg-2023-draft.html Draft WoT WG Charter|
11:16:17 <kaz> rrsagent, draft minutes
11:16:18 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
11:16:54 <cris_> ... opening a issue about it
11:17:03 <kaz> i|in order from|-> https://github.com/w3c/wot-charter-drafts/pulls PRs on wot-charter-drafts repo|
11:17:04 <kaz> rrsagent, draft minutes
11:17:05 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
11:17:21 <McCool> https://github.com/w3c/wot-charter-drafts/issues/45
11:17:50 <cris_> subtopic: Issue 36
11:17:53 <McCool> https://github.com/w3c/wot-charter-drafts/issues/36
11:17:59 <cris_> mc: from Ege
11:18:00 <kaz> i|PRs on wot|-> https://github.com/w3c/wot-charter-drafts/issues/20 wot-charter-drafts issue 20 - Things to Fix|
11:18:01 <kaz> rrsagent, draft minutes
11:18:02 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
11:18:08 <Ege> Ege has joined #wot
11:18:23 <cris_> ege: the main reason is that we talk a lot about CG collaboration
11:18:24 <sebastian> sebastian has joined #wot
11:18:40 <cris_> ... I didn't mention website on purpose
11:18:59 <cris_> ... this issue is just about taking into account cg feedback and social media coordination
11:19:00 <mjk> mjk has joined #wot
11:19:09 <cris_> ... social media is an open question.
11:19:27 <cris_> ... there is a PR
11:20:21 <kaz> -> https://github.com/w3c/wot-charter-drafts/pull/41 PR 41 - Expand WoT CG collaboration
11:20:25 <cris_> mc: ok you added a couple of words
11:20:36 <cris_> ... but you are not mentioning IG
11:20:48 <cris_> ege: but this is just WG charter
11:20:50 <cris_> mc: ok
11:21:12 <cris_> mc: should we do it also for Japanese CG?
11:21:12 <kaz> q+
11:21:35 <cris_> ege: yeah we can, I was thinking doing it myself but is not under my duties
11:21:48 <cris_> mc: we can copy it and add traslations
11:21:57 <McCool> q?
11:21:58 <cris_> ... any other comments?
11:22:00 <luca_barbato> luca_barbato has joined #wot
11:22:09 <cris_> kaz: it is vague
11:22:18 <cris_> ... what do you mean by reports?
11:22:38 <McCool> q+
11:22:39 <cris_> ... want do you mean about events?
11:23:02 <cris_> ege: I meant specifications
11:23:25 <cris_> ... regarding joint events, we can discuss it
11:23:40 <kaz> present+ Ben_Francis
11:23:52 <kaz> present+ Luca_Barbato
11:24:13 <cris_> ... I just want to involve WG memebers to events easier
11:24:40 <cris_> kaz: I understand but it is dangerous to mix it with the WG charter
11:25:10 <Ege> q+
11:25:13 <cris_> ... the sentence is good, but I would not add events and social media
11:25:18 <kaz> ack k
11:25:23 <cris_> mc: do we really agree the "via" statment?
11:25:38 <kaz> s/understand/understand your position as the CG Chair,/
11:25:39 <cris_> ... it is ok to remove it
11:26:18 <Ege> q?
11:26:20 <kaz> s/the sentence/the sentence before the "via" part/
11:26:34 <cris_> q+
11:26:54 <kaz> s/I would not add/I don't think we should specifically mention/
11:27:02 <cris_> ege: I'm ok not inclusive
11:27:07 <kaz> s/social media/social media here./
11:27:09 <kaz> q+
11:27:13 <kaz> ack m
11:27:15 <kaz> ack e
11:27:30 <cris_> ... I just want to be sure that it will be a bidirectional collaboration
11:28:01 <cris_> mc: it is about WG and commit to the collaboration
11:29:00 <cris_> ... also is just collect and not acting on the reports
11:29:03 <kaz> rrsagent, draft minutes
11:29:05 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
11:29:21 <cris_> ... we can tweak it a little bit
11:29:40 <McCool> q?
11:30:18 <kaz> ca: agree with Ege. sort of collaboration to be put here
11:30:27 <kaz> ... close collaboration with the CG
11:30:43 <kaz> ... maybe could be moved out to another document, though
11:30:52 <kaz> ack c
11:31:06 <kaz> i/agree/scribenick: kaz/
11:31:07 <McCool> q?
11:31:48 <cris_> kaz: yes, I understand. However, the charter is meant to describe the expectations in an abstract manner
11:32:00 <mlagally> q+
11:32:09 <cris_> ... the specific manner should be moved to other documents
11:32:51 <cris_> ... the part after "via" is a little bit danger, why don't we discuss it later on about it?
11:32:53 <kaz> ack k
11:33:06 <cris_> mc: we can update the PR and review it later
11:33:09 <kaz> s/danger/dangerous/
11:33:35 <cris_> ... I'm ok keeping reports or joint events
11:34:01 <cris_> .... but social media should be removed
11:34:04 <cris_> q?
11:34:51 <Ege> q+
11:34:53 <cris_> ml: we have so many groups, but always the same people. Are we over engineering our process?
11:35:15 <kaz> s/I understand/I understand your intention as the CG Chair/
11:35:28 <cris_> ... suggestion CG gather interesting use cases and implementations, IG analyze it, WG acts on the spec
11:35:34 <kaz> s/expectations/expectations from the WoT WG side/
11:36:26 <ryuichi> ryuichi has joined #wot
11:36:32 <cris_> ege: we can't bring CG presentations to IG, different patent policy.
11:36:55 <cris_> ... and also we don't want to mandate WG people to join CG meetings but rather make it easy to them to join
11:36:56 <kaz> s/the specific manner should be moved to other documents/further expectations from the CG side should be discussed more, e.g., during the WoT Marketing calls and can be put on another separate document on the CG collaboration./
11:37:02 <kaz> rrsagent, draft minutes
11:37:03 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
11:37:13 <kaz> q+
11:37:19 <kaz> ack ml
11:37:24 <kaz> ack E
11:37:32 <kaz> ack k
11:38:28 <cris_> subtopic: PR 48
11:39:06 <kaz> s/48/43/
11:39:13 <kaz> -> https://github.com/w3c/wot-charter-drafts/pull/43
11:39:26 <kaz> sk: a lot of ORGs here
11:39:48 <kaz> ... but some of there don't exist or not holding discussion any more
11:40:10 <mlagally> q+
11:40:16 <kaz> ... my proposal is moving non-active Orgs to the wiki page
11:40:45 <McCool> seb we lost you
11:41:19 <McCool> q+
11:41:29 <kaz> mm: what about ITU-T?
11:41:48 <kaz> sk: is still important but we've been not holding concrete discussions for a while
11:41:59 <kaz> ml: think this is a good proposal basically
11:42:15 <kaz> ... my comment is how to handle the IDTA
11:42:43 <kaz> ... would keep both Platform Industrie 4.0 and IDTA
11:42:55 <kaz> mm: what about ETRI?
11:43:00 <kaz> q+
11:43:03 <kaz> ack ml
11:43:17 <kaz> ack mc
11:43:38 <cris_> kaz: ETRI is a W3C member, from Korea
11:43:45 <cris_> ... they are getting more active recently
11:43:59 <kaz> rrsagent, draft minutes
11:44:01 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
11:44:07 <cris_> mm: he is the current list
11:44:20 <kaz> i/understand your/scribenick: cris_/
11:44:32 <cris_> mc: CSA is new, for matter
11:44:33 <kaz> i/a lot of ORGs/scribenick: kaz/
11:44:44 <kaz> i/ETRI is/scribenick: cris_/
11:44:53 <cris_> mc: we don't mention ETRI
11:44:57 <kaz> q+
11:45:06 <cris_> seb: I will update it
11:45:19 <cris_> kaz: we should ask ETRI representatives
11:45:41 <cris_> ... if they want to be listed as liasion org or participants.
11:45:56 <kaz> rrsagent, draft minutes
11:45:57 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
11:46:33 <cris_> mc: they collaborated recently, we should include them
11:47:42 <cris_> ... the PR cleaned also the text. Some English issues; we can fix those later
11:48:03 <kaz> q+
11:48:11 <cris_> ... it took off Microsoft from the standard orgs
11:48:15 <cris_> ... but that's fine
11:48:25 <cris_> seb: I'd like to add it somewhere
11:48:26 <Ege> q+
11:48:43 <cris_> kaz: we can include stronger industry collaborations
11:48:47 <mlagally> q+
11:48:49 <kaz> ack k
11:48:52 <Ege> q-
11:48:55 <cris_> mc: we can discuss in another PR
11:49:03 <cris_> ... any objections to this PR?
11:49:07 <cris_> ... ok, merging
11:50:33 <kaz> s|we can include stronger industry collaborations|As I already suggested yesterday, we should explain our intention on "stronger industry collaboration" in the scope section first, and we should describe what to be done for that including not only SDOs but also projects and Member/non-Member companies.|
11:50:36 <kaz> rrsagent, draft minutes
11:50:38 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
11:50:46 <mlagally> q-
11:54:38 <cris_> ... ok merged
11:54:51 <cris_> ... issue is not closed so that we can keep track of other liasons
11:55:17 <cris_> ... issue 37
11:55:29 <McCool> https://github.com/w3c/wot-charter-drafts/pull/42
11:55:30 <cris_> ... you can use it for additional orgs
11:55:44 <cris_> subtopic: PR 42
11:55:49 <cris_> mc: new mission statment
11:56:01 <cris_> ... draft status
11:56:06 <kaz> s|https://github.com/w3c/wot-charter-drafts/pull/42||
11:56:10 <sebastian> q+
11:56:15 <kaz> i|new mission|-> https://github.com/w3c/wot-charter-drafts/pull/42|
11:56:24 <kaz> rrsagent, draft minutes
11:56:25 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
11:56:52 <cris_> ... the PR adds two sentences
11:57:29 <cris_> ege: it is not done yet
11:57:38 <cris_> mc: do you want input now?
11:57:43 <cris_> ege: we can wait
11:57:57 <cris_> ... maybe just one point
11:58:11 <benfrancis> q+
11:58:42 <cris_> ege: problems with how the process is described
11:59:16 <cris_> ... it seems that is not working how it is described
11:59:30 <mlagally> q+
11:59:43 <cris_> mc: in practice we don't really follow it
11:59:49 <kaz> q+
11:59:54 <kaz> ack seb
12:00:13 <Mizushima> Mizushima has joined #wot
12:00:21 <cris_> seb: I like the mission statement, what about add a reference to the previous charter?
12:00:45 <cris_> ... also we can remove the last sentence, about Interest group
12:01:16 <cris_> ... it is not realistic, it should be moved to IG charter
12:01:34 <sebastian> ack s
12:02:02 <cris_> ben: I get the sense, but it is not clear on what do you want to achive
12:02:08 <McCool> q+
12:02:16 <cris_> ... it raises more questions
12:02:17 <Ege> q+
12:02:30 <kaz> ack b
12:02:30 <cris_> ... what do you want the group to do?
12:02:37 <kaz> q- Ege
12:02:37 <McCool> ack b
12:02:38 <kaz> qq+ Ege
12:02:43 <kaz> ack e
12:02:43 <Zakim> Ege, you wanted to react to b
12:02:50 <cris_> ege: what I want to say: the WoT can be a building block for other places as well
12:03:24 <cris_> ... integration means that for example the TD can be used in other SDO
12:03:31 <cris_> s/SDO/SDOs/
12:04:22 <cris_> mc: we had a resolution to emphasize industrial adoption
12:05:22 <cris_> ben: words need to be clarified: industry and commercial
12:05:37 <cris_> ege: for sure industry is not referring to industrial IoT
12:05:52 <cris_> ... it is more a synonym for commercial
12:05:58 <kaz> ack ml
12:06:41 <cris_> ml: we are not talking about enhancing other standard.
12:06:46 <cris_> ... should we mention this?
12:07:09 <cris_> ... then we can state outreach instead of integrate with ecosystems and comunities
12:08:16 <cris_> ege: enhancing part was already there, and I think we are doing it
12:08:21 <sebastian> q+
12:08:35 <cris_> ml: but it might be a little bit confusing
12:10:23 <cris_> kaz: I don't agree with Ben, I got the impression that we all here have a strong industry collaboration
12:10:52 <cris_> ... but we are not sure what include about these aspects in the charter sections
12:11:29 <cris_> :)
12:11:38 <kaz> s/I don't agree with Ben,/I tend to agree with Ben./
12:11:55 <kaz> s/I got the/To be honest, I got an/
12:12:37 <McCool> ack k
12:12:38 <McCool> ack m
12:12:48 <cris_> seb: should avoid to complicate everything
12:13:01 <McCool> q+
12:13:05 <kaz> s/we all here have a strong industry collaboration/unfortunately, we as the whole WoT WG are not really sure about how to explain our expectations, though we all would like to think about better industry adoption./
12:13:38 <kaz> s/but we are not sure what include about these aspects in the charter sections/So we're not sure what kind of descriptions to be included here./
12:13:41 <kaz> q?
12:13:45 <kaz> ack s
12:14:08 <Ege> scribenick: Ege
12:14:14 <mlagally> q+
12:14:36 <kaz> rrsagent, draft minutes
12:14:37 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
12:15:15 <Ege> sk: enhancing is a broad term, but we are indeed a complementary work that allows enhancing running systems
12:15:15 <Ege> q?
12:15:15 <Ege> mm: we should close the queue and discuss next steps
12:15:50 <kaz> ack ml
12:16:13 <Ege> ml: we can get comments like "Why do they not help us?" so we should be clear
12:16:19 <Ege> mm: we can say "enhance the use of"
12:16:20 <kaz> s/should avoid to complicate/should avoid complicating/
12:16:48 <kaz> q+
12:17:24 <kaz> ack m
12:17:49 <Ege> mm: we can discuss further on this on the next main call, ege can you work on it
12:17:53 <Ege> ek: yes sorry about it
12:18:14 <Ege> kaz: to improve this PR, should people give comments here?
12:18:28 <Ege> mm: I think so yes. Comments, suggestions to the text
12:19:09 <Ege> kaz: we need a consolidated document
12:19:28 <Ege> kaz: a native english speaker should modify the text at some point too
12:19:45 <sebastian> q+
12:21:08 <kaz> s/we need a consolidated document/Technically, that's a possible option, but given the current situation that we don't really have consensus on what to be put there, I'm not sure if that is the best option. Probably, we need another iteration anyway./
12:21:14 <Ege> sk: I don't think that we have a disagreement
12:21:20 <kaz> ack k
12:21:22 <Ege> ... we need to enhance to wording though
12:21:24 <kaz> q+
12:21:24 <sebastian> ack s
12:22:10 <kaz> ack k
12:22:14 <Ege> kaz: We can comment on the issue or PR but we need another iteration of this kind of discussion
12:22:51 <Ege> mm: we have a wordsmithing problem we seem to agree on the direction
12:23:52 <McCool> https://github.com/w3c/wot-charter-drafts/pull/39
12:23:53 <Ege> topic: PR 39
12:24:12 <Ege> mm: it addresses issue 24
12:24:16 <kaz> s/but/ but GitHub is not an ideal tool for this kind of situation, i.e., everybody has slightly different ideas about "industry adoption"./
12:24:45 <kaz> s/we need/Using this GitHub PR to get some more opinions is fine, but we need/
12:25:11 <kaz> s/this kind of discussion/to get actual consensus./
12:25:37 <kaz> s/topic: PR 39//
12:25:45 <kaz> i|39|subtopic: PR 39|
12:25:51 <kaz> rrsagent, draft minutes
12:25:53 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
12:26:54 <kaz> -> https://github.com/w3c/wot-charter-drafts/issues/24 issue 24 - Consolidate Work Items
12:27:06 <kaz> (McCool and Ege goes through the changes)
12:27:37 <kaz> -> https://pr-preview.s3.amazonaws.com/w3c/wot-charter-drafts/pull/39.html Preview
12:28:17 <kaz> ek: added Protocol and Payload Bindings
12:28:19 <kaz> q+
12:28:47 <kaz> mm: need to wait until Ege adds further clean-up
12:29:44 <Ege> kaz: The PR 39 is confusing. We should have bigger categories
12:29:55 <Ege> ... is this an intermediary step?
12:29:57 <kaz> i/goes/scribenick: kaz/
12:30:06 <kaz> i/The PR/scribenick: Ege/
12:30:50 <Ege> mm: topics are cross cutting across deliverables
12:31:03 <Ege> ... so as long as we have about 10 items, we should be fine
12:31:22 <Ege> kaz: we should give the purpose of the items
12:32:54 <Ege> mm: the structure is confusing that we have goals up there and then scopes later on
12:33:02 <benfrancis> q+
12:33:33 <kaz> s/we should give the purpose of the items/After reducing the items within the Scope section, we need to explain what the WoT WG will do for the next Charter period so that all the AC Reps can understand it
12:33:36 <kaz> ack k
12:33:48 <kaz> q+
12:33:51 <Ege> mm: do we need additional level of categorization?
12:34:07 <mlagally> q+
12:34:48 <mlagally> q++
12:35:03 <cris_> +1 for a bottom section explaining horizontal categories
12:35:20 <Ege> ek: I dont think we need big categories but some explanation on what the work items are aiming for is fine
12:35:54 <Ege> ml: we should have less details, this is too technical
12:36:07 <kaz> s/understand it/understand it. Maybe we could put all the items into several higher categories when we explain what we want to work on.
12:37:06 <kaz> q?
12:37:06 <Ege> bf: I agree that all these support digital twins. Focusing the ecosystem wording is vague
12:37:08 <kaz> ack b
12:37:10 <kaz> ack ml
12:37:13 <kaz> q- +
12:37:21 <Ege> bf: ecosystem is a vague term in general
12:37:59 <Ege> kaz: we need to explain what we want to do in the next charter period
12:38:27 <Ege> kaz: it should be listed in the mission statement above
12:39:34 <kaz> s/we need to explain what/To be clear, my point is not just adding high-level categories of our work items, but that we need to explain what/
12:40:14 <kaz> s/it should be listed in the mission statement above/It should be inline with the description within the mission statement above./
12:40:19 <kaz> rrsagent, draft minutes
12:40:20 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
12:41:44 <Ege> mm: let's go back to the consolidation PR
12:42:18 <kaz> q+
12:42:33 <Ege> mm: we are getting there but still a bit too many items
12:43:19 <Ege> kaz: for now it is fine but I think that this cannot be sent to AC reviews
12:44:16 <Ege> mm: any objections?
12:44:25 <Ege> q+
12:44:30 <kaz> ack k
12:45:33 <kaz> s/for now it is fine but I think that this cannot be sent to AC reviews/As an initial draft, merging this PR is fine. However, we need to explain our intention clearer rather than just listing detailed 13 items like this./
12:45:44 <Ege> ek: I dont think that we can squeeze this any further, we need higher level categories
12:45:53 <Ege> mm: yes so we need higher level description
12:46:38 <kaz> s/dont/don't/
12:46:50 <kaz> ack e
12:48:13 <Ege> q+
12:48:26 <benfrancis> q+
12:48:46 <Ege> topic: PR 46
12:49:02 <Ege> mm: I think that digital twin is a broad topic
12:49:18 <kaz> i|I think|-> https://github.com/w3c/wot-charter-drafts/pull/46|
12:49:26 <kaz> rrsagent, draft minutes
12:49:27 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
12:50:04 <benfrancis> q-
12:50:33 <kaz> q+
12:50:43 <benfrancis> +1 to McCool's comment on "Digital Twins" not being a good work item, but a general application area covered by other work items.
12:50:48 <Ege> mm: so a bit too open ended
12:50:57 <Ege> ack e
12:51:44 <Ege> kaz: digital twin is a typical use case of WoT, so I agree with mccool and benfrancis comment on irc
12:52:51 <Ege> mm: so not merging now. We should link to behavioral description standards
12:53:04 <kaz> s/digital twin is a typical use case of WoT, so I agree with mccool and benfrancis comment on irc/Basically agree with McCool and Ben. Just mentioning "Digital Twins" as one of the work items here would be confusing. We rather should add high-level description on what we want to do./
12:53:42 <kaz> s/want to do./want to do, and we can mention Digital Twins as a typical application there. However, we still need to think about how to explain that there./
12:53:54 <Ege> ml: We need better linking to the physical entity
12:54:16 <kaz> ack k
12:54:18 <kaz> q+
12:54:43 <mlagally> q+
12:55:17 <mjk> q?
12:55:22 <sebastian> I have to go. Please find here the slides about the protocol binding discussion of yesterday's TD / Binding TF call: https://github.com/w3c/wot-charter-drafts/files/10745556/WoT_Binding_2.0.pdf
12:56:13 <kaz> kaz: @@@
12:56:52 <mjk> q+
12:57:23 <Ege> mm: I dont think that we can do a behavior description in this 2 year period, we can only link to it
12:57:30 <kaz> s/@@@/I'm getting a bit concerned because these items like "Behavioral Description" and "Digital Twins" would be big topics which would require yet another dedicated WG for each./
12:57:32 <kaz> ack k
12:57:35 <kaz> ack ml
12:57:39 <mlagally> ack m
12:57:47 <Ege> mm: we can let this be revised
12:57:53 <mlagally> * sorry mjk
12:58:22 <Ege> mm: we should stop looking at PR
12:58:35 <kaz> s/for each./for each. So we should be careful about what to be done by the WoT WG and how to describe that within the Charter./
12:58:40 <kaz> rrsagent, draft minutes
12:58:41 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
12:59:02 <Ege> topic: next steps
12:59:06 <kaz> s/topic: PR 46/subtopic: PR 46/
12:59:08 <kaz> rrsagent, draft minutes
12:59:09 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
12:59:27 <kaz> q?
13:00:30 <kaz> mm: wondering about the procedure
13:00:43 <Ege> q+
13:01:00 <kaz> kaz: need to get preliminary reviews by W3M and Wide Review groups, then AC Review
13:01:32 <kaz> ... think preliminary reviews would take one month or so, and AC Review may take 2 months
13:01:47 <kaz> q+
13:01:59 <Ege> ack e
13:02:31 <Ege> mm: can we use use cases and testing together with main call for the charter?
13:02:39 <kaz> i/I'm getting/scribenick: kaz/
13:03:02 <Ege> mm: so let's commit to use case call at least
13:03:02 <kaz> i/we can do/scribenick: Ege/
13:03:04 <Ege> ... I will send an email
13:04:32 <kaz> ack k
13:05:16 <kaz> kaz: given the situation so far, I got an impression that people don't really understand what level of description is needed for the Charter document itself./
13:06:07 <kaz> s|itself./|itself. So I don't think just using the GitHub Issues/Pullrequests to consolidated updated edits would really make sense. Probably we need to organize some more dedicated meetings as well.|
13:06:19 <kaz> mm: yeah, making consensus takes time.
13:06:24 <kaz> [adjourned]
13:06:31 <kaz> rrsagent, draft minutes
13:06:33 <RRSAgent> I have made the request to generate https://www.w3.org/2023/02/16-wot-minutes.html kaz
15:02:45 <zkis> zkis has joined #wot
15:29:05 <Zakim> Zakim has left #wot