Seek wide review

[tjwhalen]

Opening this now to highlight process steps, to be ready for wide review ahead of transition to CR.

This is a meta issue to track wide review steps for the specification.
See How to do wide review for details.

• the groups listed in the WG's charter, especially those who manage dependencies
• the groups jointly responsible for a particular document (if any).
• the horizontal groups:
  • Accessibility
    • Work through this questionnaire
    • request a review via GitHub from APA
  • Architecture
    • Ask the TAG for review; see how to work with the TAG
    • 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
  • Internationalization
    • Read the Request a review page
    • work through the Short Checklist
    • request a review via GitHub
  • 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
    • request a review via GitHub from the Privacy Working Group
  • Security
    • Write a "Security Considerations" section for your document, taking into account the Self-Review Questionnaire: Security and Privacy
    • request a review via GitHub
• Other outreach (if applicable)

[SebastianZimmeck]

@pes10k offered some concrete starting points, which I can take on.