W3C

– DRAFT –
WoT-WG/IG

20 September 2023

Attendees

Present
Cristiano_Aguzzi, Daniel_Peintner, Ege_Korkan, Kaz_Ashimura, Kunihiko_Toumura, Luca_Barbato, Michael_Koster, Michael_McCool, Sebastian_Kaebisch, Tetsushi_Matsuda, Tomoaki_Mizushima
Regrets
-
Chair
McCool/Sebastian
Scribe
luca_barbato

Meeting minutes

Minutes

<kaz> Sep-6

McCool: Already reviewed before, there is a typo though

McCool: Any objection?

<sebastian> +1

<none>

McCool: The TPAC minutes will be reviewed on the TPAC-specific section

Quick Updates

McCool: The deadline for IIWoT 2024 is 8th Oct

McCool: the requirement is 6-pages paper

McCool: Volunteers welcome

Sebastian: If there is a deadline extension we could have more time

Sebastian: We could prepare a presentation on the future 2.0 from the material we are already preparing

McCool: We have to make sure the content is new though

Ege: The workshops usually prefer scientific papers

McCool: I think describing Thing Model and Discovery should be new

McCool: Would be good if academics can be the authors since publication means points for them

Kaz: I'm confused, we do not have to submit research paper, the organiser might ask for a invited presentation though

Kaz: Let's discuss it off-meeting

Policies

McCool: We do not have an obvious place to find discussions for the proposals

Kaz: If everybody really wants to make a resolution today, it is fine, but would be good to go over and make sure everybody is fine

McCool: We can, but we should work more off-meeting

<McCool> proposal: Adopt the “Asynchronous Decisions” policy defined in https://github.com/w3c/wot/blob/main/proposals/policies/async-decision.md

Kaz: Since some policies are about off-meeting work, would be good to discuss it in-meeting to make sure it is consensus

McCool: The policies had been in draft for months

Kaz: I'd rather have a summary during the meeting to make sure all the participants are fully aware

Sebastian: I share the view of Michael, I think the policies got enough consensus already

McCool: we have 3 choices: we have the original plan, we could summarise now but the turnover makes it less satisfying,
... put it off until the next week and send an headsup to the mailing list

Kaz: Do we have a 2h call today?

McCool: We have 1h call

Kaz: Let's postpone and ask for a 2h call next week

Ege: Is the controversy on the async decision or all the policies?

<cris_> +1 for PRs

+1 for PRs

Luca: If we fail to have people aware of the policies, we have a bigger problem and we should do better

Schedule changes

<kaz> Cancellations

McCool: We should not have cancellations due to holidays

McCool: We can restart the USE-CASE activities, let's reach out the a11y group to find a slot that fits their schedule

Kaz: We can change the wiki title for this section to "Meeting Schedule Changes" or something like that to avoid confusion with the "Publication Schedule Changes".

<kaz> (McCool reorganizes the sections on the agenda wiki)

Schedule

<kaz> schedule.md

McCool: We should have Testimonials for a Press Release ready before the REC publication.

Charter Review Status

Kaz: I put some information on the wiki

Kaz: We have some feedback regarding the charter template

Kaz: I'll address the issue on the unintended removal of "all known" from the Charter template myself

McCool: We should have the charter ready by Oct 1st

Publication

McCool: subtopic: Specs ready?

Ege: There is a pending PR that requires Directors' approval

McCool: kaz, can you comment in the PR to record that those PRs have been approved?

<kaz> PR1858 - Remove mention of atrisk section

<kaz> PR1843 - Fix well known operation types only

Kaz: Agreed

McCool: Who is going to prepare the publication directories?

Ege: I did before, I can do it

Kaz: For the REC I can do it myself

McCool: There is a change in the Implementation Report, I can address it

Web Resource

McCool: We have two options, we could do both

Kaz: We need to respond to another comment in the Implementation Report

<Zakim> kaz, you wanted to react to kaz

McCool: I will take care of it

Ege: I'm a bit surprised on how it is done in the Discovery repo, maybe would be better to put the resources in a separate directory

McCool: We'll provide the frozen content in a separate location

Ege: We should set up redirection for them in a w3 server so we do not rely too much on github

Cristiano: Would be nice to use the same document format across all the TFs

<Ege> https://github.com/w3c/wot-thing-description/blob/main/NAMESPACES.md

Cristiano: We have a file with the mapping

<McCool> https://github.com/w3c/wot-thing-description/blob/main/NAMESPACES.md

Kaz: We have only 5 minutes left, let's postpone the discussion and ask people for Testimonials and TPAC minutes review instead.

McCool: (gives quick summarization of WoT resources, and then move forward to the Testimonials/TPAC mintues.)

Press Release

McCool: We are waiting for testimonials

McCool: Send testimonials to Sebastian

McCool: I'll send a reminder by email

TPAC Minutes

McCool: Would be great if the TD can read and confirm their minutes, same for the other TFs

<kaz> WoT WG/IG Day 1

<kaz> WoT WG/IG Day 2

<kaz> JSON-LD, WoT, RCH joint meeting

<kaz> APA WG

<kaz> Web Agent CG

Events

Ege: There is the next CG meeting, with Seam presenting their solution

Kaz: Thanks for handling those events on the CG side. In addition to that, we should make sure what to be done by the WG side, what to be done by the CG, and what to be done collaboratively. We've started discussion for that during TPAC, and should continue clarification discussion.

Cristiano: We can put in the agenda a discussion on the update of the Scripting API

McCool: We should coordinate the publication of Notes so they are published with the RECs

McCool: The Notes should be updated before the press release

Kaz: sorry for the delay, but working on that

[adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).