Wide review tracker

[anssiko]

Note

This is a process issue to track wide review for the Vibration API.

An important part of wide review is horizontal review from W3C's key horizontal groups listed below in horizontal groups section. Also feedback from other stakeholders is equally important. Additional pointers are welcome via comments.

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

Horizontal groups

🟢 ♿ Accessibility (Accessible Platform Architectures Working Group)

• Work through the a11y checklist: Accessibility Checklist #37
• Request a review: Vibration API 2024-06-28 > 2024-09-20 a11y-request#87

🟢 📐 Architecture (Technical Architecture Group)

• See how to work with the TAG
• Request a review: Vibration API w3ctag/design-reviews#971 (draft staging issue archived at [DRAFT] TAG review request #40)

🟢 🌍 Internationalization (Internationalization Working Group)

• Read how to request a review
• Work through the i18n checklist: Internationalization Checklist #38
• Request a review: Vibration API 2024-06-28 > 2024-09-20 i18n-request#236

🟢 🔍 Privacy (Privacy Interest Group)

• 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
• Security and Privacy Self-review #36
• Request a review: Vibration API 2024-06-28 > 2024-09-20 w3cping/privacy-request#138

🟢 🔒 Security

• Write a "Security Considerations" section for your document, taking into account the Self-Review Questionnaire: Security and Privacy
• Security and Privacy Self-review #36
• Request a review: Vibration API 2024-06-28 > 2024-09-20 security-request#71

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.

• Mozilla position: Vibration API (Second Edition) mozilla/standards-positions#907
• WebKit position: Vibration API (Second Edition) WebKit/standards-positions#267

[anssiko]

The following supplementary materials have been made available for the WG participants to review and comment:

• Accessibility: Accessibility Checklist #37
• Internationalization: Internationalization Checklist #38
• Security and Privacy: Security and Privacy Self-review #36
• Architecture: [DRAFT] TAG review request #40

Accessibility, Internationalization and Security and Privacy issues will be linked from the respective horizontal review requests, so any comments provided in those issues will be brought to the attention of the horizontal groups.

[anssiko]

Thank you everyone for your feedback and comments that helped improve the supplementary materials significantly.

I have now submitted all the review request with a proposed deadline of 2024-09-20 to allow us discuss the wide review feedback at TPAC 2024.

Further improvements for Accessibility, Internationalization and Security and Privacy materials can be provided through respective issues in this repo. For Architecture/TAG review comments and improvements, please provide them directly in the upstream review request issue in the TAG repo.

You'll find pointers to all the review requests and materials from the first comment in this issue.

[anssiko]

Wide review has been completed.

Thank you everyone across all the horizontal groups for your diligent work in reviewing this specification! Your feedback improved the specification significantly.

What's next?

Following our Call for Consensus, we will execute the resolution we made at TPAC to publish this specification as a new Candidate Recommendation Snapshot, obsoleting the Second Edition Recommendation. This publication signals to the wider community the specification is both implemented and welcomes further implementation experience to inform improvements such as Permissions API integration (#42), security considerations (#49), and UI controls (#50).

@himorin thank you for handling the remaining logistics required to get this publication out.