-
Notifications
You must be signed in to change notification settings - Fork 34
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
4fd0b40
commit 1946acd
Showing
1 changed file
with
96 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,96 @@ | ||
| # Agenda for 24 April 2024 | ||
| 1. Logistics | ||
| 1. Plan | ||
| 1. Minutes review and discussion points | ||
| 1. Wrap-up "further discussion" on the Use Case Template | ||
|
|
||
| Any other topics for today? | ||
|
|
||
| Scribe list: | ||
| 1. Koster | ||
| 1. Kaz | ||
| 1. McCool | ||
| 1. Luca | ||
| 1. Ege | ||
|
|
||
| ## Logistics | ||
| Use Cases calls to be cancelled | ||
| * May-1 Golden Week Holday in Japan | ||
| * Mizushima will take a possible vacation at the end of May (to be confirmed) | ||
|
|
||
| ## Plan | ||
| ### Previous plan on 3 April 2024 | ||
| * Apr-3: Finalize basic Use Cases template; quickly skim the publication schedule | ||
| * Apr-24 / May-8: Fix basic Functional Requirements template based on a concrete eample | ||
| * May-15 and May-22: Fix basic Technical Requirements based on a concrete example | ||
|
|
||
| ### Updated plan on 24 April 2024 | ||
| * Apr-24: Wrap-up "further discussion" on the Use Case Template | ||
| * May-8: Initial discussion on Requirements Template | ||
| * May-15 and May-22: Fix basic Functional Requirements Template | ||
| * May-29 and June-12: Fix basic Technical Requirements Template | ||
|
|
||
| Any objections/opinions? | ||
|
|
||
| ## Minutes review and discussion points | ||
|
|
||
| ### Minutes | ||
|
|
||
| [Apr-03 minutes](https://www.w3.org/2024/04/03-wot-uc-minutes.html) | ||
|
|
||
| ### Discussion points | ||
| * [Proposed Use Case Template](https://github.com/w3c/wot-usecases/blob/main/USE-CASES/use-case-template-2024.md) was accepted as the basic template | ||
| * [RESOLUTION: Accept use-case-template-2024.md as the basic template](https://www.w3.org/2024/04/03-wot-uc-minutes.html#r01) | ||
| * Further Discussion on the Template | ||
| * Q1: How to let non-IG members submit their use cases? | ||
| * [Issue 281 - Mention Possibility of External Submissions via Issues #281 | ||
| ](https://github.com/w3c/wot-usecases/issues/281) | ||
| * Q2: What to be described by the README? | ||
| * [PR #280 - Update README.md](https://github.com/w3c/wot-usecases/pull/280) | ||
| * Q3: How to apply existing guidelines within the old template? | ||
| * Notes within the [old template](https://github.com/w3c/wot-usecases/blob/main/USE-CASES/use-case-template.md) | ||
|
|
||
| Any objections to the minutes and the discussion points above? | ||
|
|
||
| ## Wrap-up "further discussion" on the Use Case Template | ||
|
|
||
| ### Q1: How to let non-IG members submit their use cases? | ||
| * [Issue 281 - Mention Possibility of External Submissions via Issues #281 | ||
| ](https://github.com/w3c/wot-usecases/issues/281) | ||
| * would agree and propose we use [GitHub Issue mechanism](https://github.com/w3c/wot-usecases/issues/new/choose) to submit a Use Case | ||
| * We can embed the Use Case template within GitHub Issues like: | ||
| * [Strategy Issues](https://github.com/w3c/strategy/issues) | ||
| * [Transitions Issues](https://github.com/w3c/transitions/issues) | ||
|
|
||
| ### Q2: What to be described by the README? | ||
| * Describe the Use Case submission procedure | ||
| * would suggest we start with clarifying the procedure about submitting use cases via the GitHub Issue mechanism | ||
| * [PR #283 - Use GitHub Issues to submit Use Cases](https://github.com/w3c/wot-usecases/pull/283) | ||
|
|
||
| ### Q3: How to apply existing guidelines within the old template? | ||
| * Notes within the [old template](https://github.com/w3c/wot-usecases/blob/main/USE-CASES/use-case-template.md) to be recorded within the [README.md](https://github.com/w3c/wot-usecases/edit/main/USE-CASES/README.md) | ||
| * included in [PR #283 - Use GitHub Issues to submit Use Cases](https://github.com/w3c/wot-usecases/pull/283) | ||
|
|
||
| ## Functional Requirements | ||
| What kind of functionality is needed to implement the proposed use cases. | ||
|
|
||
| **NOTE:** We need to consider: | ||
| * Publication schedule, i.e., "September, 2024" as the publication date for the WoT Use Cases and Requirements Note" | ||
| * We'll discuss basic publication schedule during today's call later. | ||
| * Relationship with the existing discussion on the "work items" by the other TFs | ||
| * We'll start discussion on Fuctional Requirements during today's call later. | ||
|
|
||
| ## Technical Requirements | ||
| What kind of feature is needed (=to be added or improved) for each WoT specification, i.e., WoT Thing Description and WoT Discovery. | ||
|
|
||
| ## Basic Publication Schedule | ||
| * April/May: | ||
| * Use Cases TF clarifies use cases and requirements including the potential feedback from the WoT JP CG | ||
| * June: | ||
| * UCR Note publication 1 | ||
| * updates on the templates for use cases and requirements | ||
| * provides input to the WoT-WG TFs for spec updates | ||
| * WoT-WG TFs publish updated specs as WoT 2.0 FPWDs | ||
| * Interim updates, e.g., refactroing and basic direction for 2.0 versions | ||
| * September: | ||
| * UCR Note publication 2 |