See the timezone table ...
| San Francisco (U.S.A. - California) | Thu, 25 January 2024 | 07:00 | UTC-8 hours |
| Boston (U.S.A. - Massachusetts) | Thu, 25 January 2024 | 10:00 | UTC-5 hours |
| London (United Kingdom - England) | Thu, 25 January 2024 | 15:00 | UTC+0 hours (adjusted for DST) |
| Berlin (Germany) | Thu, 25 January 2024 | 16:00 | UTC+1 hours (adjusted for DST) |
| Helsinki (Finland) | Thu, 25 January 2024 | 17:00 | UTC+2 hours (adjusted for DST) |
| Shanghai (China) | Thu, 25 January 2024 | 23:00 | UTC+8 hours (adjusted for DST) |
| Tokyo (Japan) | Fri, 26 January 2024 | 00:00 | UTC+9 hours (adjusted for DST) |
| Corresponding UTC (GMT) | Thu, 25 January 2024 | 15:00 UTC | |
Other locations: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240125T15
- Chair: Anssi
- Scribe: ? (see howto, volunteers welcome!)
- IRC: irc://irc.w3.org:6667/#webmachinelearning
- IRC web client: https://irc.w3.org/?channels=#webmachinelearning
- Joining instructions: https://lists.w3.org/Archives/Member/internal-webmachinelearning/2023Jun/0000.html
- Minutes: https://www.w3.org/2024/01/25-webmachinelearning-minutes.html
Review the proposed plan for delta wide review and refreshed CR Snapshot expected in Q1'24.
Proposal: Build upon the work done in Q1'23 for the initial CR to demonstrate changes since satisfy publication prerequisites:
- Wide review tracker webmachinelearning/webnn#240
- Proposal: refresh Arch/TAG and Privacy wide reviews, only inform other horizontal groups
- CR readiness tracker webmachinelearning/webnn#239
- Proposal: update implementation experience, test coverage, note significant new & removed features and spec conventions improvements, update use cases
References:
- WebNN publication history and diff between CR Snapshot 30 Mar 2023 and latest
- (Informative) Wide Review and CR Snapshot requirements
As we're approaching another spec milestone, discuss what are the most urgent and important issues for the group, practical steps we can take to help new contributors e.g. revise our issue labels and apply them in triage actively.
This practice also helps ensure we meet our wide review objective with gusto, the WG is expected to:
- Document the highest priority open issues or categories
- Ensure the spec remains in a cohesive state including for its informative parts e.g. use cases, programming model sections
Continue discussion on the proposal for a backend-agnostic storage type for WebNN operations informed by implementation experience.
- issue: webmachinelearning/webnn#482
- Chromium implementation: https://chromium-review.googlesource.com/c/chromium/src/+/5173676
Other open issues discussed subject to time based on your feedback during the issue prioritization exercise.