W3C

– DRAFT –
WoT Use Cases

06 August 2025

Attendees

Present
Josh_Thomas, Michael_McCool, Tomoaki_MIzushima
Regrets
-
Chair
McCool
Scribe
jthomas

Meeting minutes

Minutes

July-30

McCool: looked at PR 374 and merged
… Looking at 372 today
… cleaned up 372 as well as added some links. Added status
… Call of publishing the minutes with no objections

PR

<McCool> w3c/wot-usecases#372

McCool: Looking at PR w3c/wot-usecases#372
… No reviews to the changes, call for resolution today.
… Status of Work in Progress on a lot of them
… Did not add anything from capability vs condition
… ... Added related issues and risks under Why section for consistency
… Added colons to each of the tags for uniformity
… Might be some other things to fix, but its in a really good place.
… Will not merge, but we ask for a resolution of this to be merged.
… After this merge I want to do some restructuring
… Adding notes to w3c/wot-usecases#373 to Reverse the order of the userstories for better readability
… Once the PR for the Security user stories is merged

<McCool> proposal: Implement a PR to resolve Issue #373 and merge it immediately after PR #372 is merged (assuming the resolution passes today in the main call).

Josh: the merge is so there are less conflicts?

McCool: Yes since there are lot of changes

RESOLUTION: Implement a PR to resolve Issue #373 and merge it immediately after PR #372 is merged (assuming the resolution passes today in the main call).

McCool: Added labels of fix in progress to both 373 and 372

<McCool> close w3c/wot-usecases#364 - currently no broken links

McCool: Looking at PR https://github.com/w3c/wot-usecases/pull/376, it's completed. Any objections to closing?
… none voiced so closing pr
… Looking at PR w3c/wot-usecases#360
… I think Ben was referring to the old template which we moved past. We made some of the fields as optional. I don't see a issue for fixing the discovery section
… In issues we have a lot of discovery and security that we can retire once we
… Creating a new issue for this since the others might be closed out with our changes.
… A lot of issues will be resolved with the recent changes.
… I feel we are almost ready for a note once this is closed. I think we need to do one more thing where we do formatting on the stakeholders
… Can we make this change this to use the dfn tags to make it an official definition
… Mizushima if you can get this done by next week we can review?

<McCool> w3c/wot-usecases#366

Mizushima: I'll try to get it completed

McCool: w3c/wot-usecases#365
… Once we fix the DFN tags in 366 we can make a PR to fix 365
… After one more pass and the other PRs and Issues discussed we can be ready to publish a note
… Lets create a new issue to update the Abstract and Intro
… Then we need to cleanup dead issues since a lot will be rosolved.
… Using the "in work" label to indicate what we need to get done.

Mizushima: I should update the editors

McCool: we probably need a resolution to do this
… We need to bring up in the main call to add editors if we want. But for now we need a PR to remove editors that are no longer working on it
… Call for meeting close

Summary of resolutions

  1. Implement a PR to resolve Issue #373 and merge it immediately after PR #372 is merged (assuming the resolution passes today in the main call).
Minutes manually created (not a transcript), formatted by scribe.perl version 244 (Thu Feb 27 01:23:09 2025 UTC).