Meeting minutes
Agenda review
<kaz> (some discussion about potential guests)
Minutes review from January 29th
<kaz> Jan-29
McCool: any objections to the minutes?
… no objections, accepted
<kaz> (typos fixed)
Quick Items
Breakouts
<kaz> Breakouts Day 2025 repo
McCool: there is a call for breakout sessions for W3C Breakout Day
… do we want to propose a breakout session?
… we have about a month to submit a proposal
… we would need volunteers if we decide to participate
… any comments?
Kaz: if we want to respond as a whole group, we should create issues
McCool: yes, we can create an issue and a draft for review
Inclusiveness Discussion
<kaz> wot-binding-templates issue 393 - Registry Inclusiveness
McCool: no discussion today but please look at the github issue
Notices
McCool: anything?
Meetups
McCool: any new meetups:
Smart Cities IG
McCool: is there a slot for the Smart City IG
Kaz: there is a slot for JP 10PM JST February 17
Kaz: still working on US-EU friendly slot. also inviting the Chair of the Nordic Smart Cities CG Chair.
Cloud-Edge-Client CG
McCool: trying to find a calendar slot that works
McCool: any other meetup announcements?
Liaisons
McCool: are there any updates on liaisons?
ETSI
McCool: we met with ETSI, went through the presentation, and are getting an idea of how they fit in
… February 10th ETSI call is cancelled
<kaz> Feb-3 minutes
<McCool> w3c/
McCool: (reviewing minutes from the February 3rd meeting)
Holidays
<kaz> Holidays
McCool: I will be unavailable the entire month of May
McCool: will we take May 5-9 off for Golden Week?
Kaz: yes, people will be off that week
mizushima: March 3rd is not a holiday in Japan
McCool: OK, right (removes)
McCool: we may decide to cancel during Golden Week
Schedule
McCool: any changes to the schedule?
… no changes
dape: the Scripting API schedule update is in the calendar
Policies
<kaz> Policy issues
IE Policy
<kaz> wot PR 1224 - Create invited-expert.md
McCool: are there any updates to the IE policy?
Koster: no updates, all changes should be merged
McCool: let's make a proposal to adopt the IE policy
<McCool> proposal: adopt the proposed Invited Expert policy as stated in https://
McCool: the policy policy needs to be updated for how to merge PRs
McCool: any objections to the resolution?
RESOLUTION: adopt the proposed Invited Expert policy as stated in https://
McCool: no objections, resolved to adopt and will merge the PR after cleanup
<kaz> policy-adoption.md
McCool: we have 2 weeks to reverse this if there is a problem
Kaz: you mean the above privacy-adoption.md by "policy policy", and we need to update that too. Right?
McCool: yeah, it's about which directory to put drafts in
Moderator policy
<kaz> wot issue 1208 - [Policy Proposal] Managing moderator policy
McCool: what is the status of the moderator policy?
Koster: we need to look into the roles and responsibilities document
McCool: specifically we need to decide how selection works and the co-moderator policy
Koster: is there a W3C policy for moderators?
McCool: the W3C doesn't say much about task forces
… TF leads are often document editors, as are our moderators
<kaz> wot issue 1117 - [Policy Proposal] Roles and responsibilities within the WG/IG
McCool: open issue #1117 for Roles and Responsibility
<McCool> https://
Koster: there is a document Ege created we need to move
Koster: we could update the R&R document with more bullets and then create a new .md document for TF moderators
McCool: selection is a separate topic from Roles and Responsibilities
Kaz: we need to include Ege in the discussion for next time
McCool: we need to clean up the issue list at the next chairs call
<kaz> wot issues in general
McCool: the selection procedure really isn't part of Roles and Responsibilities
Koster: it will go in the .md document
TF Leads
Use Case backlog
<kaz> wot-usecases remaining issues
McCool: how can we make progress when other TFs are inactive?
… we have work on TD Templates use cases which needs to be aligned with ThingModel work
McCool: four cases...
... 1. user story from an inactive TF. We reactivate it temporarily to generate these.
... makes sense for discovery and security
... 2. active TFs can generate user stories (focus on new things...)
... 3. UC TF could draft user stories and ask for review and confirmation from relevant TFs (for older, existing features)
... 4. We could just close old issues asking for use cases and user stories in UC TF.
McCool: does anyone object to #3, having the Use Case TF draft the user stories?
Kaz: not objecting, but does the UC TF have resources to generate new user stories?
McCool: we could extract user stories from existing issues and have the TF work on them, for example the Thing Template use cases
Kaz: we should rather have the TD TF do the draft and the UC TF can join that discussion.
McCool: Option 2 is preferred but might not be practical in all cases
… we want to get a good document with a lot of use cases this year
… when is it appropriate for the UC TF draft new stories and ask for review from the feature TF?
McCool: they are short and there are a lot of them
… I think it's reasonable to propose some user stories from the UC TF
Kaz: the concern is about resources. let's ask Ege also about his opinions as well.
McCool: volunteers would help
<McCool> proposal: UC TF can generate drafts of user stories, use cases, and use case categories but must ask the relevant TF for review and approval before merging. If the TF is inactive approval can be requested in the main call and via email with a 2-week review period.
McCool: does anyone object to making this a resolution?
… it gives us the ability to make progress
RESOLUTION: UC TF can generate drafts of user stories, use cases, and use case categories but must ask the relevant TF for review and approval before merging. If the TF is inactive approval can be requested in the main call and via email with a 2-week review period.
McCool: hearing no objections, this is resolved
TF reports
McCool: any TF reports?
… none
Adjourn
McCool: any other business or topics?
… none, adjourned