12:06:15 <RRSAgent> RRSAgent has joined #wot
12:06:15 <RRSAgent> logging to https://www.w3.org/2022/05/25-wot-irc
12:06:21 <kaz> chair: McCool
12:06:30 <McCool_> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#25_May_2022
12:06:54 <kaz> present+ Kaz_Ashimura, Michael_McCool, Daniel_Peintner, Ege_Korkan, Erich_Barnstedt
12:06:56 <mlagally_> mlagally_ has joined #wot
12:06:59 <matsuda> matsuda has joined #wot
12:07:17 <kaz> present+ Kunihiko_Toumura, Michael_Lagally, Tetsushi_Matsuda, Tomoaki_Mizushima
12:07:28 <kaz> rrsagent, make log public
12:07:33 <kaz> rrsagent, draft minutes
12:07:33 <RRSAgent> I have made the request to generate https://www.w3.org/2022/05/25-wot-minutes.html kaz
12:08:00 <cris_> cris_ has joined #wot
12:08:21 <dape> scribe: dape
12:09:13 <kaz> present+ Cristiano_Aguzzi
12:09:16 <dape> TOPIC: Previous Minutes
12:09:30 <dape> -> May-18 -> https://www.w3.org/2022/05/18-wot-minutes.html
12:09:56 <dape> <McCool going over minutes>
12:10:48 <Mizushima> Mizushima has joined #wot
12:12:14 <dape> MMC: any objections?
12:12:17 <kaz> meeting: WoT-IG/WG
12:12:20 <kaz> rrsagent, draft minutes
12:12:20 <RRSAgent> I have made the request to generate https://www.w3.org/2022/05/25-wot-minutes.html kaz
12:12:23 <dape> -> none -> minutes approved
12:12:40 <kaz> present+ Michael_Koster
12:12:47 <dape> TOPIC: Quick updates
12:12:51 <kaz> present+ Sebastian_Kaebisch
12:13:00 <dape> SUBTOPIC: IEEE P2874 Updates
12:13:16 <dape> MMC: invited to give a talk
12:13:23 <dape> ... 1 June 2022 at 1:00pm Eastern Time
12:13:36 <dape> ... will prepare draft
12:13:51 <dape> SUBTOPIC: Cancellations and updates
12:14:16 <dape> MMC: Arch Call moved to Editor call slot
12:14:30 <dape> ... forgot to update W3C calendar
12:14:52 <dape> ... will do that next time
12:15:34 <kaz> q+
12:15:34 <dape> ... will setup dedicated DTDL call invite to avoid confusion
12:15:55 <dape> ML: Use use-case call dial-in?
12:16:14 <dape> MMC: not possible, conflicts with editor call
12:16:15 <sebastian_> sebastian_ has joined #wot
12:16:15 <sebastian_> q+
12:16:23 <dape> ... cleaner to have a dedicated invite
12:17:03 <dape> Kaz: WebEx for editor/use-case has been changed, so we can use that
12:17:10 <kaz> -> https://lists.w3.org/Archives/Member/member-wot-wg/2022May/0000.html wot-tuesday-8am-boston
12:17:22 <kaz> s/boston/boston (Member-only)/
12:17:32 <dape> MMC: Suggest new invite to avoid confusion
12:17:35 <dape> q?
12:17:39 <kaz> ack k
12:18:04 <dape> MMC: Hannover fair?
12:18:15 <dape> SK: Next week, Monday to Thursday
12:18:43 <dape> ... Ege will most likely not be available also
12:18:55 <dape> MMC: Please update cancellation section
12:19:18 <dape> SUBTOPIC: JP Member meeting
12:19:32 <dape> Kaz: had meeting on Wed last week
12:19:48 <dape> ... talked about several updates
12:19:58 <dape> MMC: Follow-up items?
12:20:10 <dape> Kaz: resources are in Japanese
12:20:18 <dape> ... got good impression
12:20:32 <dape> TOPIC: Publications
12:20:40 <dape> SUBTOPIC: Wide Review
12:20:53 <kaz> s/impression/impression on WoT as well :)/
12:20:58 <dape> MMC: Issues are in flight
12:21:07 <dape> ... TDs has completed all necessary changes
12:21:34 <dape> ... in draft, for discovery
12:21:41 <dape> ... Explainer is pretty much done
12:22:02 <dape> ... ready for review next week
12:22:43 <dape> ... we need to publish WD, e.g. Architecture
12:22:53 <dape> ... we have Explainer draft for Profiles
12:22:59 <dape> ... needs some more work
12:23:44 <dape> SK: One issue open for TD w.r.t. internationalization
12:23:51 <dape> ... we hope to solve it today
12:24:40 <dape> MMC: The extension plan is slightly out of sync
12:24:54 <dape> ... https://github.com/w3c/wot/blob/main/charters/wg-2021-extension-plan.md
12:25:37 <dape> ... BTW, TPAC 2022 has been confirmed
12:26:20 <dape> SUBTOPIC: Calls for WD Updates
12:26:50 <dape> MMC: 2 week review time... normally
12:27:04 <dape> ... I suggest 1 week review period
12:27:26 <dape> ... TD is in flight ...candidate branch today?
12:27:35 <dape> ... any objection for 1 week review
12:27:45 <dape> ... 2 weeks will impact schedule
12:27:50 <kaz> q?
12:27:57 <dape> ML: WD update closed when?
12:28:18 <dape> MMC: It takes about 1 week to go through process
12:28:19 <kaz> ack s
12:28:41 <dape> ... after creating branch we can work on WD
12:28:47 <kaz> q+
12:29:02 <dape> ML: Next week is a problem. Vacation period in Europe
12:29:16 <dape> MMC: Not a CR candidate
12:29:45 <dape> ML: wondering about cut-off date for MergeRequests
12:30:20 <dape> MMC: Branch today
12:30:29 <dape> ... rest goes to next draft
12:30:38 <dape> SK: I think we talk about CR, not WD
12:30:50 <dape> MMC: For CR, we need 2 weeks
12:31:05 <dape> SK: Correct, we are heading to CR
12:32:46 <kaz> -> https://github.com/w3c/wot-thing-description/tree/main/publication/ver11/3-wd Guide on how to edit the draft for publication
12:33:05 <dape> Kaz: editors, please look at guideline and check documents
12:33:31 <dape> ... the faster we can resolve issues that faster we are
12:33:52 <dape> ... start with static version... rather than branch
12:34:28 <kaz> s/that faster we are/the faster we can publish the drafts/
12:35:43 <kaz> s/start with static version... rather than branch/please generate a static version HTML in addition to tagging a branch for the document check/
12:35:47 <dape> MMC: w.r.t. Architecture, we have a stable version for a week already
12:35:54 <dape> ML: Suggest not to rush
12:36:31 <dape> MMC: Okay, lets give architecture 1 more week
12:36:46 <dape> ... for TD, we should allow for 2 weeks from now
12:37:03 <dape> SK: CR version, right
12:37:24 <dape> MMC: Yes, but let's decide later
12:37:38 <dape> SK: Okay, we will merge the pending PRs today.
12:37:55 <dape> .. freeze the document, review for 2 weeks
12:38:21 <dape> ... in 2 weeks we decide on CR or WD depending on (number of) comments
12:38:36 <dape> TOPIC: Review other Ongoing Action Items
12:38:46 <dape> ... -> https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Ongoing_Action_Items
12:39:08 <kaz> s/... ->/->/
12:39:26 <kaz> s/Items/Items Ongoing actions/
12:39:30 <dape> TOPIC: Liaisons
12:39:48 <dape> MMC: Sebastian will setup OPC UA meeting
12:40:25 <dape> MMC: ITU-T SG20, they are working on smart-city
12:40:42 <dape> ... Next SG20 mtg is 19-28 July 2022; need further followup before then
12:41:06 <dape> Kaz: ECHONET likes to start further collaboration
12:41:24 <dape> MMC: I see, will be input to next charter discussions
12:41:45 <dape> Kaz: IEC CDD (Common Data Dictionary)
12:41:47 <kaz> s/collaboration/collaboration with the WoT-JP CG first/
12:42:01 <dape> Kaz: will talk about the next steps with them on June 13 again.
12:42:23 <kaz> q+
12:42:44 <mlagally_> q+
12:43:06 <dape> TOPIC: AC review
12:43:21 <dape> Kaz: AC review announcement was send out yesterday
12:43:37 <dape> ... please ask your AC rep
12:43:53 <dape> ... we need 20 approvals in total
12:44:13 <dape> s/20 approvals/20 supports
12:44:26 <kaz> -> https://www.w3.org/2002/09/wbs/33280/wotwg2022/ AC review form (Member only)
12:44:40 <kaz> ack k
12:44:43 <dape> TOPIC: TF Reports
12:45:08 <dape> SUBTOPIC: Architecture
12:45:24 <dape> ML: Architecture document is stable, please review
12:45:29 <dape> SUBTOPIC: Profile
12:45:51 <dape> ML: talked about real out-of-the box interoperability
12:45:55 <dape> ... please provide comments
12:46:13 <dape> ... we talked about proposals/platforms
12:46:24 <McCool_> https://github.com/w3c/wot-profile/issues/200
12:46:39 <dape> SUBTOPIC: Discovery
12:46:49 <dape> MMC: Talked about security bootstrapping
12:47:01 <dape> ... like HTTP negotiation
12:47:16 <dape> ... I hope all concerns are addressed
12:47:17 <McCool_> q?
12:47:20 <McCool_> ack m
12:47:39 <dape> SUBTOPIC: Marketing
12:47:56 <McCool_> https://github.com/w3c/wot-marketing/issues/321
12:47:58 <dape> MMC: would like to focus on "Should the CG manage (some of) the WoT web pages?"
12:48:31 <dape> ... Clarification to limit scope of CG
12:48:53 <dape> ... like : Developers, Documentation, and Videos
12:49:01 <dape> ... purely about content
12:49:08 <dape> ... not design et cetera
12:49:49 <dape> ... pages are about informative documentation and training materials
12:50:07 <Ege> q+
12:50:29 <dape> Ege: we don't want CG to be another group
12:50:44 <kaz> q+
12:50:51 <kaz> ack k
12:50:51 <dape> ... we would like to have specs better visible
12:50:53 <kaz> ack e
12:50:55 <kaz> q+
12:51:23 <dape> ... don't plan to have separate page for CG
12:52:43 <dape> Ege: moreover, marketing task force is currently a website taskforce
12:52:55 <dape> ... outreach should become a CG task
12:53:45 <dape> MMC: Important question. Is CG responsible for the afore mentioned pages
12:54:07 <dape> MMC: Agree with McCools comments on issue
12:54:25 <dape> ... all WoT groups should clarify what they do
12:54:31 <mlagally_> q+
12:54:41 <dape> ... WoT team provides auto-generated pages
12:54:55 <dape> ... we should think about what CG should add
12:55:10 <sebastian_> q+
12:55:24 <dape> ... for example, Japanese group drives outreach/meeting informations
12:55:27 <dape> q+
12:55:36 <kaz> -> https://www.w3.org/groups/ Auto-generated group pages
12:55:42 <kaz> s/pages/page/
12:56:00 <cris_> q+
12:56:01 <dape> ML: Confusion comes because we do not have clear definitions
12:56:06 <kaz> ack k
12:56:24 <dape> ... marketing taskforce responsible for outreach
12:56:41 <dape> ... CG more for meetings, testings
12:56:51 <dape> ... CG should not do official communication
12:57:06 <kaz> q+
12:57:10 <kaz> ack ml
12:57:13 <dape> Ege: Who does official communication?
12:57:26 <dape> s/Who does/Who does do
12:57:30 <kaz> i|Confusion|-> https://wot-jp-cg.netlify.app WoT-JP CG page as an example|
12:57:50 <kaz> s/WoT team/the W3C Team/
12:58:13 <kaz> s/MMC: Agree with/Kaz: Agree with/
12:58:21 <dape> ML: the main website should stay within WG/IG
12:58:58 <dape> MMC: I suggest to use same page, but sub-pages might be handled by CG
12:59:19 <dape> Ege: not sure if this is what we want
12:59:51 <dape> MMC: Tools list for me can be a CG task
12:59:54 <kaz> s|we should think about what CG should add|We WoT-IG/WG should think about what to be added to our own generated pages in addition to the /groups/wg/wot and /groups/ig/wot, and the CG also should think about what to be added to the CG page in addition to /groups/cg|
13:00:11 <dape> ... new feature should be an IG activity
13:00:33 <dape> ... suggest to separate content CG vs IG/WG
13:00:41 <dape> q?
13:00:51 <kaz> s|outreach/meeting informations|outreach event information and deployment guideline information on their own generated pages|
13:02:10 <kaz> rrsagent, draft minutes
13:02:10 <RRSAgent> I have made the request to generate https://www.w3.org/2022/05/25-wot-minutes.html kaz
13:02:38 <dape> SK: activity in marketing / website  can be seen as CG results
13:02:51 <dape> ... should consider having a different webpage
13:03:05 <dape> ... not hosted by W3C, like json-ld.org
13:04:00 <kaz> q?
13:04:03 <kaz> ack s
13:04:04 <McCool_> ack s
13:04:08 <sebastian_> q-
13:04:09 <Fady> Fady has joined #wot
13:04:13 <kaz> ack d
13:05:10 <dape> DP: I fear splitting sites creates confusion
13:05:48 <dape> ack dape
13:06:13 <sebastian_> I need to go.
13:06:42 <dape> CA: Issue is clear. Can CG publish content on those 3 pages.
13:06:55 <dape> ... we can ask for a vote?
13:07:03 <dape> ... suggest to have a single website
13:07:13 <dape> ack cris_
13:07:34 <dape> Kaz: Different opinions from different people
13:07:42 <dape> ... need more discussions
13:08:25 <dape> ... some would like consolidated page
13:08:43 <dape> ... CG is different from W3C process viewpoint
13:09:33 <dape> MMC: Please provide comments in issue 321
13:09:53 <dape> ... please focus on question: CG to manage content on 3 pages
13:12:53 <kaz> s|some would like consolidated page|it sounded to me that some would like the CG to maintain the consolidated WoT page at www.w3.org/WoT|
13:13:02 <kaz> s/CG is/but CG is/
13:13:34 <kaz> [adjourned]
13:13:39 <kaz> rrsagent, draft minutes
13:13:39 <RRSAgent> I have made the request to generate https://www.w3.org/2022/05/25-wot-minutes.html kaz
13:22:05 <ktoumura> ktoumura has left #wot
14:04:18 <Mizushima> Mizushima has left #wot
14:10:21 <dape> dape has joined #wot
15:30:27 <Zakim> Zakim has left #wot
16:03:58 <bkardell_> bkardell_ has joined #wot
18:29:27 <stevelee> stevelee has joined #wot