Wide review tracker

[anssiko]

About

This is a process issue to track wide review for the Device Posture 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

• Work through the a11y checklist
• Request a review via GitHub from APA: Device Posture API 2024-05-31 > 2024-08-31 a11y-request#84 completed Device Posture API 2024-05-31 > 2024-08-31 a11y-request#84 (comment)
  • Spec: Accessibility considerations based on APA WG contributions Requesting Accessibility Considerations section  #70
  • Accessibility checklist #147

🟢 📐 Architecture

• Ask the TAG for review; see how to work with the TAG
  • Device Posture API [formerly Screen Fold API] w3ctag/design-reviews#575 completed Sep 2021
• See also related reviews:
  • Viewport Segments Property w3ctag/design-reviews#689 completed Jun 2022
  • Foldable Device CSS Primitives w3ctag/design-reviews#690 completed Mar 2022

🟢 🌍 Internationalisation

• Read the Request a review page
• Work through the i18n checklist
• Request a review via GitHub: Device Posture API 2024-05-31 > 2024-08-31 i18n-request#233
  • Internationalization checklist #148
  • Device posture and direction interaction #151

🟢 🔍 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
  • Self-Review Questionnaire self-assessment
  • Spec: Privacy considerations
• Request a review via GitHub from the Privacy Interest Group: Device Posture API 2024-05-31 > 2024-08-31 w3cping/privacy-request#136

🟢 🔒 Security

• Write a "Security Considerations" section for your document, taking into account the Self-Review Questionnaire: Security and Privacy
  • Spec: Security considerations status: no known security considerations, no security issues reported
  • Self-Review Questionnaire self-assessment
• Request a review via GitHub: Device Posture API 2024-05-31 > 2024-08-31 security-request#69
  • No concerns raised by 2024-08-31 deadline for comments

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: Device Posture API mozilla/standards-positions#882
• WebKit position: Device Posture API WebKit/standards-positions#328

Other resources

• Origin trial for Foldable APIs - explains how this JS API and CSS primitives work together
• foldable-devices/demos - demos of various use cases for the API

[anssiko]

@darktears can you produce a first stab of the responses to the a11y checklist and i18n checklist mentioned in this wide review tracker? We'll then review your first stabs with the WG, and I'll formally request respective reviews from horizontal groups when satisfied.

A good best practice has been to create a separate GH issue for each to allow reviewers follow-up as appropriate. See the recently completed wide reviews e.g. this one and the another one to get an idea of expectations. Please also reuse and refer to the existing accessibility considerations in your a11y checklist responses as appropriate.

Please let me know if you have any questions.

[darktears]

@anssiko done, please look.

[anssiko]

Thank you @darktears. I consider your a11y and i18n checklist contributions appropriate and note both already received comments. I have thus formally requested both the Accessibility and Internationalisation reviews to seek horizontal review from respective groups. Please be prepared to answer any questions from any of the horizontal groups in a timely manner.

I have also reflected this status in #146 (comment)

[anssiko]

I observed we also have all the materials expected by privacy and security reviewers, so I've also initiated both the Privacy and Security reviews today.

With that, all reviews are now either in flight or completed as reflected in #146 (comment)

I've asked reviewers to respond by the end of August 2024 latest. I'm expecting the editors to respond to any feedback, and as appropriate, attend focused sessions with horizontal groups to discuss specific considerations.

Thank you for your contributions, everyone.

[anssiko]

Accessibility review was just confirmed completed in w3c/a11y-request#84 (comment) 🥳

I've updated the tracker #146 (comment) accordingly.

[anssiko]

As discussed at TPAC, @himorin will check with the privacy colleague to confirm PING review status w3cping/privacy-request#136, after which we'll start a CfC to publish CR of Device Posture API.

@darktears @diekus @kenchris @rakuco and all the other contributors, thank you for your continued efforts in nudging this specification forward!

[himorin]

@darktears @diekus @kenchris @rakuco privacy-needs-resolution has been cleared : #152
@anssiko Ready for CfC to publish as CRS (I don't think we have one before, e.g. to start this WR/HR, but please point if I missed something.)

[anssiko]

CfC to publish Device Posture API Candidate Recommendation Snapshot - review by 8 Nov 2024

@himorin thank you for your support in making this publication happen.

[anssiko]

This CfC passes.

We will now proceed with the Device Posture API Candidate Recommendation Snapshot publication at the earliest opportunity. Congratulations to the group for this milestone. 🚀

Thank you everyone for your contributions and to all the horizontal groups for careful review and comments.

@himorin will take care of the publication logistics, thank you!

I will close this wide review tracker to signal completion.