13:03:55 <RRSAgent> RRSAgent has joined #wot
13:03:55 <RRSAgent> logging to https://www.w3.org/2022/02/02-wot-irc
13:04:06 <kaz> meeting: WoT-IG/WG
13:04:29 <mlagally_> mlagally_ has joined #wot
13:04:30 <kaz> present+ Kaz_Ashimura, Michael_McCool, Cristiano_Aguzzi, Kunihiko_Toumura, Michael_Lagally
13:04:43 <Mizushima> Mizushima has joined #wot
13:05:35 <kaz> present+ Daniel_Peintner
13:06:50 <kaz> present+ Tomoaki_Mizushima, Ryuichi_Matsukura
13:08:44 <matsuda> matsuda has joined #wot
13:08:45 <ktoumura> ktoumura has joined #wot
13:09:00 <kaz> present+ Tetsushi_Matsuda, Sebastian_Kaebisch
13:09:16 <kaz> topic: Minutes
13:09:25 <kaz> -> https://www.w3.org/2022/01/26-wot-minutes.html Jan-26
13:09:27 <kaz> approved
13:09:45 <kaz> chair: McCool/Sebastian
13:09:55 <mlagally_> scribenick: mlagally
13:09:55 <kaz> scribenick: mlagally
13:10:00 <mlagally_> :-)
13:10:12 <kaz> i/approved/scribenick: kaz/
13:10:13 <mlagally_> topic: Quick Updates
13:10:32 <dape> q+
13:10:33 <kaz> rrsagent, make log public
13:10:38 <kaz> rrsagent, draft minutes
13:10:38 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/02-wot-minutes.html kaz
13:11:06 <mlagally_> Editors call - some alignments in scripting, Event handling in the TD, discovery is mostly frozen
13:11:52 <sebastian> q+
13:11:55 <mlagally_> mizushima: WoT Japanese CG: 22 people participated in meeting last Friday. Questions about how to implement it easily, how to handle events
13:12:04 <mlagally_> mmc: is there a list of attendees?
13:12:31 <mlagally_> kaz: there are minutes on github, but CG does not care about affiliations, records just names
13:12:52 <kaz> q+
13:13:06 <mlagally_> sk: 2 issues in last TD call - Plans to set up a Bacnet binding. We should also ask Takenaka if he is interested to work on this.
13:13:14 <mlagally_> kaz: will report in TD call
13:13:29 <kaz> s/will/have already talked with Kasuya-san, and will/
13:13:55 <mlagally_> mmc: As a general idea Use Case descriptions should be created using the use case document for further inclusion into the use cases document
13:14:05 <mlagally_> ... any plans for a future CG meeting?
13:14:21 <mlagally_> mizushima: Echonet lite event is planned for March
13:14:33 <kaz> q?
13:14:37 <kaz> ack d
13:14:38 <kaz> ack s
13:14:39 <kaz> ack k
13:14:50 <kaz> q+
13:15:08 <mlagally_> dape: scripting API is a WoT Note, notes should not have conformance statements, there's also a "Note" track that has conformance statements.
13:15:12 <dape> https://lists.w3.org/Archives/Member/member-wot-wg/2022Jan/0022.html
13:15:20 <mlagally_> ... we plan to move to this "note track"
13:15:22 <kaz> s/https/-> https/
13:15:22 <mlagally_> q+
13:15:30 <kaz> s/html/html Daniel's message/
13:15:37 <kaz> -> https://github.com/w3c/wot-scripting-api/issues/354 Scripting Issue 354
13:15:43 <dape> ack dape
13:16:16 <mlagally_> kaz: I put that topic into TF reports, when do we want to make a group resolution?
13:16:32 <mlagally_> dape: want to give people a 1 week review, next week?
13:17:14 <mlagally_> kaz: W3C process document has been significantly updated - group notes can contain normative statements, but these documents are not covered by W3C patent policy
13:17:41 <dape> q?
13:17:47 <kaz> s/covered/endorsed by the W3C as a whole or covered/
13:17:47 <mlagally_> mmc: This may apply to other documents as well, such as security guidelines
13:17:48 <kaz> ack k
13:17:54 <kaz> ack m
13:18:03 <kaz> present+ Zoltan_Kis
13:18:28 <mlagally_> mlagally: what's the difference between a "note" and a "note track"?
13:19:11 <mlagally_> kaz: document is not endorsed by the W3C as a whole, it is not a rec
13:19:31 <mlagally_> ... the status of the document will be significantly changed, boiler plate
13:19:44 <mlagally_> ... respec may make this change already automatically
13:19:57 <McCool_> q?
13:19:58 <dape> ack mlagally_
13:20:01 <kaz> zakim, who is on the call?
13:20:01 <Zakim> Present: Kaz_Ashimura, Michael_McCool, Cristiano_Aguzzi, Kunihiko_Toumura, Michael_Lagally, Daniel_Peintner, Tomoaki_Mizushima, Ryuichi_Matsukura, Tetsushi_Matsuda,
13:20:04 <Zakim> ... Sebastian_Kaebisch, Zoltan_Kis
13:20:10 <mlagally_> topic: chartering
13:20:37 <mlagally_> IG charter: request for approval was sent
13:20:48 <mlagally_> WG charter: not approved - this may happen today
13:21:03 <kaz> s/sent/sent to W3M, and should be discussed right now in parallel/
13:21:22 <kaz> s/WG charter/WG charter extension/
13:21:25 <kaz> q+
13:21:48 <cris_> q+
13:22:18 <mlagally_> ... at the moment we formally don't have a WG, cannot publish documents
13:22:47 <mlagally_> mlagally: can we make it explicit, that the dates in the WG extension plan are tentative
13:22:59 <mlagally_> mmc: only the last date is fixed
13:23:18 <mlagally_> kaz: we should decouple the schedule discussion and extension procedure
13:23:29 <mlagally_> ... we need horizontal review, ...
13:23:46 <dezell> dezell has joined #wot
13:23:54 <mlagally_> ... we can get 1 year extension to Jan next year, should think about schedule separately
13:24:01 <dezell> present+ David_Ezell
13:24:13 <mlagally_> topic: rechartering
13:25:12 <mlagally_> We should take into account the use cases for the next charter period and should start use case and requrement analysis before we finalize the new charter.
13:25:46 <mlagally_> ... will add this to the schedule
13:25:54 <cris_> ack c
13:26:00 <mlagally_> mlagally: let's discuss in the next UC call
13:26:02 <kaz> s/we need horizontal review/regarding the extension procedure, we need horizontal reviews again and it would take one month. Then need to get the AC review and it would also take one month or so. So I'm asking W3M for 4-mo extension to finalize the procedure. However, we can think about the updated publication schedule based on the assumption of extending our WG Charter by 12-mo./
13:26:04 <kaz> ack k
13:26:14 <kaz> s/topic: re/topic: WG re/
13:26:18 <mlagally_> topic: publications
13:26:52 <mlagally_> kaz: I'm working on the process to publish Use Cases document and TD, will work later this week.
13:28:24 <mlagally_> mlagall: Architecture review of normative parts showed some inconsistencies - will talk about details in tomorrow's arch call
13:29:16 <mlagally_> mmc: security TF could manage security review of all WoT specifications
13:29:31 <mlagally_> ... questionnaire is very browser centric
13:29:32 <kaz> s/mlagall:/mlagally:/
13:30:01 <mlagally_> mlagally: we should do that, will reduce number of parallel communication trails with security experts
13:30:04 <cris_> q+
13:30:19 <mlagally_> topic: CG chair
13:30:54 <kaz> present+ David_Ezell
13:31:02 <mlagally_> mmc: CGs are pretty ad-hoc, typically only one chair, chair can select co-chairs
13:31:06 <mlagally_> q+
13:31:15 <kaz> rrsagent, draft minutes
13:31:15 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/02-wot-minutes.html kaz
13:31:36 <kaz> present+ Zoltan_Kis
13:31:38 <kaz> rrsagent, draft minutes
13:31:38 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/02-wot-minutes.html kaz
13:31:43 <mlagally_> ... mmc explains details about the chair selection process
13:31:57 <mlagally_> ... CG decides how this is handled
13:32:10 <mlagally_> ... we should have a resolution about which procedure to use
13:32:16 <kaz> present+ Sebastian_Kaebisch
13:32:21 <kaz> q+
13:32:22 <mlagally_> ... Dave Raggett should decide on the process
13:32:43 <McCool_> https://www.w3.org/community/council/wiki/Chair_selection
13:33:55 <McCool_> proposal: recommend that the "Simple" algorithm be used to select the new WoT CG chair
13:33:58 <kaz> q?
13:34:09 <dape> q+
13:34:13 <McCool_> proposal: recommend that the "Simple" algorithm be used to select the new WoT CG chair, and that we ask Dave Raggett to announce to the group
13:34:20 <McCool_> proposal: recommend that the "Simple" algorithm be used to select the new WoT CG chair, and that we ask Dave Raggett to announce to the CG
13:34:31 <cris_> https://www.w3.org/community/about/tool/#choose-chair
13:34:44 <mlagally_> Cristiano: I'm fine with the simple algorithm, need to understand modalities how to self-nominate
13:35:10 <mlagally_> ... website says that only W3C staff can nominate chairs
13:35:23 <dape> q-
13:36:09 <kaz> ack c
13:36:19 <mlagally_> mmc: Let's ask Dave to do the necessary procedures, announce nominations afterwards
13:36:40 <McCool_> proposal: recommend that the "Simple" algorithm be used to select the new WoT CG chair, and that we ask Dave Raggett to announce to the CG, and also enable nominations in the system by removing himself as chair
13:36:50 <kaz> rrsagent, draft minutes
13:36:50 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/02-wot-minutes.html kaz
13:37:24 <McCool_> q+
13:37:31 <kaz> ack ml
13:39:11 <mlagally_> mlagally: a chair needs to separate between the role of a chair and representing his company. He should make it explicit when he speaks for his company and needs to have a balanced view that represents the interests of all WoT members.
13:39:16 <McCool_> proposal: We ask Dave Raggett to recommend that the "Simple" algorithm be used to select the new WoT CG chair, and that we ask Dave Raggett to announce to the CG, and also enable nominations in the system by removing himself as chair
13:39:17 <dsr_> dsr_ has joined #wot
13:39:48 <mlagally_> ... I'm sure we have enough good candidates for that, will not run for chair.
13:40:45 <mlagally_> kaz: Everybody should join the CG first and understand the proposal of how the nomination should be done.
13:41:03 <mlagally_> mmc: There are 224 members but not much activity.
13:41:37 <mlagally_> kaz: We don't have to make resolution in this call, but on the CG mailing list. Everybody who is interested in CG discussion should join.
13:42:13 <mlagally_> ... we can make a proposal for ourself
13:42:27 <mlagally_> q?
13:42:33 <kaz> s/ourself/ourselves, though/
13:42:48 <kaz> ack k
13:42:54 <McCool_> ack m
13:42:56 <kaz> ack m
13:43:01 <kaz> q+ mlagally
13:43:01 <mlagally_> mmc: We can make a proposal for the CG, the CG can make a resolution
13:44:02 <mlagally_> mlagally: I encourage we get regular updates from the CG chair(s) in this call
13:44:16 <mlagally_> mmc: We should have a charter
13:44:22 <mlagally_> topic: testing
13:45:22 <mlagally_> mmc: We need to decide when to have the testfest, I agree that we have 2 test fests in the schedule.
13:45:52 <mlagally_> ... We need to decide right away so we can get organised.
13:45:55 <kaz> i|topic: testing|-> https://github.com/w3c/cg-charter Kaz mentions there is a template for CG Charters as well|
13:46:44 <mlagally_> ... current dates don't hold
13:47:11 <mlagally_> ... plan of having the testfest / plugfest in the same week.
13:47:36 <mlagally_> mlagally: I encourage and support that.
13:47:50 <McCool> McCool has joined #wot
13:48:33 <McCool> proposal: hold TestFest/Plugfest the week of 14-18 March, with a daily Testfest sync call at 8am ET and a Plugfest call at 9am ET
13:49:49 <mlagally_> ... this narrow time slot works for all members around the globe
13:50:38 <McCool_> resolution: hold TestFest/Plugfest the week of 14-18 March, with a daily Testfest sync call at 8am ET and a Plugfest call at 9am ET
13:51:02 <mlagally_> topic: liasons
13:51:26 <mlagally_> mmc: tomorrow there's a call for a Webinar, myself, Kaz and Sebastian are speaking
13:51:34 <mlagally_> ... currently updating the slides
13:52:07 <kaz> -> https://www.itu.int/en/ITU-T/webinars/20220203/Pages/default.aspx ITU-T Webinar site
13:52:18 <kaz> -> https://github.com/w3c/wot/blob/main/PRESENTATIONS/2022-02-WoT-ITU-T-McCool.pdf McCool's slides
13:52:29 <kaz> -> https://github.com/w3c/wot/blob/main/PRESENTATIONS/2022-02-WoT-ITU-T-Thing-Description-Kaebisch.pdf Sebastian's slides
13:52:40 <kaz> -> https://github.com/w3c/wot/blob/main/PRESENTATIONS/2022-02-WoT-ITU-T-Ashimura.pdf Kaz's slides
13:53:56 <mlagally_> ... I'm meeting offline with Christine Perey, we work on reviewing geolocation use cases. I also review the geopose standard, there are some gaps of how we can embed location into TDs
13:54:26 <mlagally_> kaz: For Echonet there's a plan in the CG
13:54:39 <mlagally_> ... next steps for smart home is the actual binding
13:55:24 <mlagally_> mmc: historical data, Christine is involved in that, there are some use cases for digital twins
13:55:36 <mlagally_> topic: TF reports
13:56:00 <mlagally_> dape: scripting: we are aligning with discoery TF, I already mentioned the "Note track"
13:56:18 <mlagally_> mmc: we should talk about exposing an interface
13:56:29 <mlagally_> dape: right, this is not part of the current APIs
13:57:18 <mlagally_> mmc: Security: several PRs in the pipeline, not merged yet. In the PR for architecture I added an section.
13:59:00 <mlagally_> ... Discovery: We had a discussion earlier today (in Profiles), hope the proposal resolves the issue
13:59:57 <mlagally_> sk: will discuss events in today's TF, apart from we are kind of stable, some smaller changes
14:01:05 <kaz> q+
14:01:08 <kaz> ack ml
14:01:37 <mlagally_> mmc: purpose of a feature freeze is to get testing possible, target a mostly frozen document
14:02:01 <kaz> ack k
14:03:16 <sebastian> sorry, I need to move to a next call
14:03:21 <mlagally_> mlagally: unfortunately cannot participate in today's TD call, please create an issue with remaining questions for the event proposal, so we can address it in tomorrow's architecture call
14:03:47 <kaz> [adjourned]
14:03:52 <kaz> rrsagent, draft minutes
14:03:52 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/02-wot-minutes.html kaz
14:05:49 <dsr_> dsr_ has joined #wot
14:06:00 <ktoumura> ktoumura has left #wot
14:24:45 <dsr_> dsr_ has joined #wot
14:27:17 <kaz> regrets+ Ege
14:27:19 <kaz> rrsagent, draft minutes
14:27:19 <RRSAgent> I have made the request to generate https://www.w3.org/2022/02/02-wot-minutes.html kaz
14:54:14 <dsr_> dsr_ has joined #wot
15:09:52 <sebastian> https://w3c.github.io/wot-binding-templates/bindings/protocols/modbus/index.html
15:12:11 <dsr_> dsr_ has joined #wot
15:17:30 <sebastian> proposal: group decides to freeze the TD features after the TD call. There is an exception for the eventing discussion which will be decided next week.
15:29:11 <dsr_> dsr_ has joined #wot
16:01:31 <dsr_> dsr_ has joined #wot
16:02:06 <Zakim> Zakim has left #wot
16:21:29 <dsr_> dsr_ has joined #wot
16:33:12 <dsr_> dsr_ has joined #wot
17:01:48 <sebastian> sebastian has joined #wot
17:30:45 <dsr_> dsr_ has joined #wot
18:33:12 <dsr_> dsr_ has joined #wot
19:23:16 <dsr_> dsr_ has joined #wot
19:40:31 <dsr_> dsr_ has joined #wot
20:12:21 <dsr_> dsr_ has joined #wot
20:42:20 <dsr_> dsr_ has joined #wot
21:16:01 <dsr_> dsr_ has joined #wot
21:46:22 <dsr_> dsr_ has joined #wot
22:03:00 <dsr_> dsr_ has joined #wot
22:48:42 <dsr_> dsr_ has joined #wot
23:50:01 <dsr_> dsr_ has joined #wot