Horizontal Review preparation

[wseltzer]

Per the W3C Process, we are required to get horizontal review: Accessibility, Architecture, Internationalization, Privacy, and Security. W3C Guidance: How to Get Horizontal Review.

This issue is meant to help us track overall progress.

Accessibility

• Work through this questionnaire then 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 [email protected], a technical discussion list shared by W3C and ECMA's TC 39.

Internationalization

• Read the Request a review page, then work through the Short Checklist, then 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 then request a review via GitHub from the Privacy Interest Group.

Security

• Write a "Security Considerations" section for your document, taking into account the Self-Review Questionnaire: Security and Privacy, then request a review via GitHub

[wseltzer]

For each review area, I suggest the group find an internal champion to work with the relevant questionnaires and github issues to coordinate with the horizontal review group.

[wseltzer]

Thanks for volunteering!

• i18n: @hlflanagan
• privacy: @npm1
• security: @philsmart

[hlflanagan]

The i18n review request has been submitted. Results will be posted here: w3c/i18n-request#246

[philsmart]

@npm1 and I are going to take a pass at the existing security and privacy questionnaire answers which I put into a Google Doc for easy editing: https://docs.google.com/document/d/1f-PUqW2uwxC4XQLtebhOixeRx3XShf5BzZ1ll3jLAOI/edit?usp=sharing

[philsmart]

@npm1 and I are now happy with the answers in that Google Docs. @wseltzer I guess the next steps are to check through the Security section of the spec, and then we can request a review on GitHub.