Meeting minutes
Logistics
Mizushima: no cancellations planned for July
… however, cancellations Aug 21 and 28
Mizushima: updates to meeting plan; July 17 and 24, adding github issue template, internal trial and refactoring
Kaz: no objections, but you might want to quickly go through all the logistics information including both the cancellation and meeting plan rather than having two separate sections within the agenda MD.
Minutes
Mizushima: last meeting was July 10
Mizushima: https://
Mizushima: main discussion points: WoT-JP reuse of template, translation to/from Japanese
Mizushima: closed some issues and PRs related to template
… then discussed issue of real names and emails
… and proposal that we should have a policy to delete UC (proposals) if we can't contact the submitters
McCool: suggest delete "proposals" in summary
Kaz: in minutes should be accurate
McCool: and we really should officially discuss the policy at the WG level at some point
Kaz: right. so it would be better to quickly review the important points based on the minutes themselves rather than re-generating "summaries" on the agenda. Then we should confirm the potential policy today based on the discussion last week.
Mizushima: any objections to approving minutes?
… none, approved
Fix the YAML-based Use Case template
Mizushima: have several issues and PRs...
Mizushima: w3c/
Mizushima: this PR changes the order of "What to be done?"
… however, Ege created another PR to remove some of the similar/duplicate template to remove them
Mizushima: w3c/
… and PR 293 is against an old file; will close MZ's PR against old file (without merging), will merge Ege's, and then create a new PR
Kaz: suggest we just look at the PRs in order
McCool: if we merge the change and then delete the file it will have the same result in the end; we'll still need to create a new PR to implement the fix
Mizushima: propose merging #294 - Ege's PR to delete files
McCool: suggest close #293 without merging otherwise history will be confused
PR 293
<kaz> PR 293 - Change the order of items of sample-usecase-template.yml based Issue …
Mizushima: (closes 293 without merging)
PR 294
<kaz> PR 294 - Delete old issue templates
Mizushima: next, let's discuss #294
… this PR deletes some old templates
McCool: agree with merging #294 and deleting these files
Kaz: are we sure these are the right files?
McCool: even if we delete the wrong file, still in github history, so no problem
Mizushima: (merges #294)
PR #295
Mizushima: this is applying some fixes to the correct template file
Mizushima: also renames filename
<kaz> [ WoT-UseCases-Template-20240710.yml => WoT-UseCases-Template.yml ]
McCool: agree with merging this PR; seems to also fix a cut-and-paste error
Mizushima: (merges #295)
Discussion
Real Names and emails
Mizushima: have summarized previous discussion in agenda
McCool: my main point last time was that if we can't contact submitters in the future (somehow - may or may not be email) then we reserve the right to delete a use case
McCool: think we should propose a resolution here
… also, Ege is not here but he had a slightly different opinion
McCool: I think though personally that we should have clear "authorship" for uses cases, and not allow anonymous use cases
Kaz: agree. let's see if people here can make a basic resolution for today.
Luca: if we don't have enough information provided, someone could also "take over" a use case
McCool: so that is an alternative approach, letting the UC TF modify use cases, taking over authorship
… but I personally think UC are a way for stakeholders to request support, so it would be odd to modify them
Mizushima: Jan, do you agree?
Jan: no strong opinion
McCool: how should we proceed? Should we have a resolution now, or write up a policy proposal?
McCool: my opinion is we need a policy proposal; a bit too much to fit into a single resolution
Mizushima: would like to get started with accepting use cases
McCool: I think the policy relates to publication; but we can still start accepting submissions - we should clarify the policy before publication.
McCool: I did say that I wanted to write up a proposal; I had not gotten to it, but can do so by next week. suggest we move on
McCool: my intention is to follow the "authorship" and "right to delete" path
Mizushima: agree with that direction
Security and Privacy Categories
Mizushima: PR #290
Mizushima: w3c/
Kaz: issue 290 may be too big for the time
McCool: sure, let's discuss next time
<kaz> w3c/
Stakeholders
<kaz> Issue 289 - [UC Template] Stakeholders
<kaz> w3c/
McCool: problem is we have three different lists of stakeholders. Only S&PG has definitions. Propose we consolidate, add any missing definitions to S&PG list, and use that as the master.
Kaz: before that, there is an other problem, the YAML is broken
… added PR #297 to fix a missing field
… let's continue the discussion next time
[adjourned]