Wide review tracker

[anssiko]

About

This is a meta issue to track wide review for the Web Neural Network API.

An important part of wide review is horizontal review from W3C's key horizontal groups listed below. Also feedback from other stakeholders is equally important and we're documenting some of such signals in this issue too. Additional pointers are welcome via comments.

Legend:
🔴 Review request not submitted
🟡 Review request submitted
🔵 Review feedback received
🟢 Review closed as completed

Horizontal groups

🟢 ♿ Accessibility

• Work through this questionnaire - Accessibility Checklist #261
  • request a review via GitHub from APA - Web Neural Network API 2022-05-10 > 2022-09-01 w3c/a11y-request#26
  • Review confirmed completed Web Neural Network API 2022-05-10 > 2022-09-01 w3c/a11y-request#26 (comment)

🟢 📐 Architecture

• Ask the TAG for review; see how to work with the TAG
  • full review Web Neural Network API w3ctag/design-reviews#570 completed
  • delta review Delta review (to CR) of Web Neural Network API w3ctag/design-reviews#771 (Oct'21-Sep'22)
  • delta review 2 Updated review of WebNN API w3ctag/design-reviews#933 (Mar'23-Mar'24) - NB: any additional off-cycle feedback is also considered by the group as per our commitment for close coordination with horizontal groups
  • If you are developing javascript APIs you may also want to ask public-script-coord@w3.org, a technical discussion list shared by W3C and ECMA's TC 39

🟢 🌍 Internationalisation

• Read the Request a review page
• work through the Short Checklist Internationalization Checklist #262
• request a review via GitHub - Web Neural Network API 2022-05-10 > 2022-09-01 w3c/i18n-request#179 Web Neural Network API 2024-01-29 > 2024-02-29 w3c/i18n-request#223

🟢 🔍 Privacy

• Write a "Privacy Considerations" section for your document, taking into account the Self-Review Questionnaire: Security and Privacy, Mitigating Browser Fingerprinting in Web Specifications, and RFC6973
  • Completed Self-Review Questionnaire: Security and Privacy #119
  • Privacy Considerations refresh #271
  • Consider privacy-tracker issues
• request a review via GitHub from the Privacy Interest Group
  • Early Privacy Review Request submitted and response received with comments addressed
  • Submit a new Review Request for any privacy-impacting changes since the early request, if any Web Neural Network API 2022-06-30 > 2022-09-30 w3cping/privacy-request#96
  • PING feedback integrated Items from privacy review  #280
  • Review confirmed completed Web Neural Network API 2022-06-30 > 2022-09-30 w3cping/privacy-request#96 (comment)

🟢 🔒 Security

• Write a "Security Considerations" section for your document, taking into account the Self-Review Questionnaire: Security and Privacy
  • Consider security-tracker issues
• request a review via GitHub Web Neural Network API 2022-03-25 > 2022-06-30 w3c/security-request#22
• Review closed as completed Web Neural Network API 2022-03-25 > 2022-06-30 w3c/security-request#22 (comment)

Other stakeholders

From who to ask for review:

Horizontal reviews [...] are only a subset of a full wide review, which must also include other stakeholders including Web developers, technology providers and implementers not active in the Working Group, external groups and standards organizations working on related areas, etc.

🟢 WebGPU Working Group gpuweb/gpuweb#2500

• Positive feedback received at the GPU Web F2F meeting 2023-02-16 (Member-only), see also WebML WG 2023-03-02 meeting minutes

🟢 Web developers: TensorFlow.js support, Microsoft DevRel positive signals

🟢 Broader community: workshop recommendation

🟢 Implementers: positive signals, Chromium Intent to Prototype

[anssiko]

Closed as completed.

[anssiko]

Per our discussion in https://www.w3.org/2024/01/25-webmachinelearning-minutes.html#t01 I have initiated Architecture/TAG and Privacy delta wide reviews highlighting relevant new information since their previous review and informed also other horizontal groups (a11y, i18n, Security) of our plan to publish a new CR Snapshot during Q1'24.

I piggypacked on the existing review issues, links below. Thanks to the WG for inputs reflected in these requests. I will bring concrete feedback from these reviews to the attention of the WG for deliberation.

Delta wide reviews in flight:
🟢 ♿ Accessibility w3c/a11y-request#26 (comment)
🟢 📐 Architecture w3ctag/design-reviews#933 - any additional off-cycle feedback to be considered in the most recent version of the spec
🟢 🌍 Internationalisation w3c/i18n-request#223
🟢 🔍 Privacy w3cping/privacy-request#96 (comment)
🟢 🔒 Security w3c/security-request#22 (comment)

[anssiko]

The latest TAG delta review request refiled as a new issue to hopefully bump its priority in triage w3ctag/design-reviews#933 over the earlier review request we initially appended (thanks @dontcallmedom!).

[anssiko]

I have informed the TAG of our recent CR Snapshot publication and that any additional off-cycle feedback is welcome and will be considered by the group in the most recent version of the spec. With that, I'll close this issue. We'll re-open this tracker when we do another coordinated wide review for a future version as appropriate.

On behalf of the entire group, I want to thank the horizontal groups for their review, contributions and partnership.

[anssiko]

I'm reopening this wide review tracker for a new round of review requests that are in flight now:

🔵 ♿ Accessibility w3c/a11y-request#105

• (draft) Review feedback WebNN Review (APA thread) w3c/apa#350

🟡 📐 Architecture w3ctag/design-reviews#1072

🟢 🌍 Internationalisation w3c/i18n-request#258

• Review feedback String metadata and localization for operator labels #837
• Response Add notes regarding label usage, provided by i18n review #841

🔵 🔍 Privacy w3cping/privacy-request#156

• Comments Web Neural Network API 2025-03-20 > 2025-06-20 w3cping/privacy-request#156 (comment)
• On the Privacy WG agenda [agenda] 2025-05-15 w3c/privacywg#11

🟡 🔒 Security w3c/security-request#85

It may take a while for the horizontal groups to pick up the reviews. To that end, fine-tuning of the review requests is possible and welcome. We've asked review feedback to be delivered within the next three months. Meanwhile, the work on the API spec continues as usual.

Edit: Updated with the latest.