How to do Wide Review

Getting early and wide review of a document is very important, yet in practice it can be challenging. This document provides some best practices for getting document review; it does not define explicit mandatory steps.

This page is linked to from The Guide.

Feedback on this document is welcome, preferably by raising an issue or a pull request.

Contents

  1. Introduction
  2. How to get horizontal review
  3. Considerations and Best Practices
    1. Who to ask for review?
    2. When should review be requested?
  4. Request for Comments (RfC) Template
    1. What to include
    2. Example Request for Comments
  5. Working with Horizontal Review Labels
    1. Day-to-day use of labels
    2. What happens to unresolved issues marked *-needs-resolution?
  6. Horizontal Review Boards
  7. FAQ
  8. Terminology and Abbreviations
  9. Enhancement Requests
  10. Resources

Introduction

Getting early review and feedback is important, especially reviews from those groups that have identified a document as a dependency and the horizontal groups. It is also important to get review from 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.

In Process-2019, the focus is on getting evidence that wide review has occurred.

How to get horizontal review

When you have published a First Public Working Draft, you should work through available "self-review" materials and request review of your results in at least the following areas. Long enough before you request a transition to CR, you should do the same again, identifying substantive specification changes since the first review.

The meaning of "Long enough" depends on how many changes there are, how clearly you have explained them, and how much discussion is needed to resolve issues. Pointing to 14 concise points for a small spec means a short time if they are simple fixes, pointing to 900 diffs from commits and hoping people understand them in a 300 page spec means it will take a long time to get review, and potentially a long time to also discuss and agree on how to solve the issues. If you have effectively identified issues for review during development and received feedback on them, the review time will probably be shorter. Horizontal review groups sometimes get bogged down; planning in advance is useful.

Accessibility
Work through this questionnaire then request a review via GitHub from APA
Show useful links
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.
Show useful links
Internationalisation
Read the Request a review page, then work through the Short Checklist, then request a review via GitHub.
Show useful links
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.
Show useful links
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
Show useful links
Groups listed in your charter
If there are groups listed in your charter as depending on some specification, you should ask them too.
General announcement
Use public-review-announce@w3.org for general announcements regarding wide and horizontal reviews. (Sending an email to this list alone is not sufficient to trigger horizontal reviews. You will still need to formally request review from the Horizontal Groups, as described above.)

You should familiarize yourself with the rest of this document. This section is just a quick reminder for when you are in the middle of doing the work.

Considerations and best practices

Among the considerations and best practices, regardless of the type of review (early, thorough wide review, etc.) are:

Who to ask for review?

When should review be requested?

Recognize that horizontal review groups may be resource limited and may only be able to do one review or may have difficulty scheduling your review quickly. Give them as much time as you can, consistent with asking for review while it is still reasonable to change the technology to accommodate the issues they find.

Request for Comments (RfC) Template

The Internationalization WG has a series of issue templates that guide you through the information you need to provide when requesting a review. The information that follows is for other HR groups that don't use that approach.

What to include

Example Request for Comments

Here are some example RfCs:

Working with Horizontal Review labels

Applying these labels doesn't replace the need to schedule a review of your spec at an appropriate time. (See How to Get Horizontal Review above.) Horizontal groups participants can find detailed process information here.

Day-to-day use of labels

Apply the *-tracker label in your own repository to draw a horizontal review group’s attention to an issue in one of your own repositories. Horizontal review groups may also apply the label if they are interested in tracking a particular issue. Tooling will automatically notify the horizontal group that you attached the label.

If you want some specific advice from the horizontal group, describe that request in the issue thread.

Horizontal review groups may apply the *-needs-resolution label to issues they expect to be resolved before the specification moves to a new maturity level. Working Groups must not remove or add this label (not even when you close your issue).

If the horizontal group believes that an issue with a *-tracker label needs to be resolved before a transition, they may apply a *-needs-resolution label to the issue. Automatic tooling will later remove the *-tracker label.

If you close an issue with a *-tracker or *-needs-resolution label attached, do not remove the label. Keeping the label maintains the tracking if the issue is reopened, but also provides potentially useful information about what was tracked. (Closed issues in your repository have no effect on tools that check for unresolved issues.)

At the end of a review, and before attempting to transition the spec, you should clarify that a resolution is described for all of the issues with a *-needs-resolution label, and check that the horizontal group is aware of those resolutions. You don't have to do this for issues with the *-tracker label. (The horizontal group was only tracking those issues, not expecting a particular resolution.)

What happens to unresolved issues marked *-needs-resolution?

As lead technical architect, the W3C Director is tasked (among many things) to assess consensus within W3C for architectural issues and to decide on the outcome of Formal Objections. When a horizontal issue gets flagged as *-needs-resolution and a Group chooses to request a new Maturity level despite the lack of consensus with the horizontal group, it is the task of the Director to assess the issue and the outcome of the request. A horizontal group MAY choose to elevate an horizontal issue as a Formal Objection to elevate further the importance of an issue per the W3C Process.

In the case where an horizontal issue hasn’t been addressed and the document was allowed to move forward, it is recommended that the issue remains open in the horizontal group repository (it MAY get closed in the specification repository unless the Director requests otherwise). Some issues may take years to get resolved, but that doesn’t mean those should be forgotten.

Horizontal review boards

The horizontal groups maintain repositories containing issues that track those raised in the WG repos. Key information about the current state of those tracker repositories is reflected in a set of tracker boards, one per horizontal function. The board points to WG issues and the corresponding tracker issues, and groups issues by specification.

Horizontal groups participants can find detailed process information here.

FAQ

Q: Is security and/or privacy review mandatory before a First Public Working Draft is published?
  • A: Strictly speaking, no. However, getting early review for documents with features that might have security and/or privacy implications is strongly encouraged - security and privacy issues can require significant changes in specs, and it helps to identify them early.
Q: Does a group need to prove its documents have had wide review before proceeding to CR?
  • A: Yes, since Process-2019.
Q: How does a group prove its documents have had wide review before proceeding to CR?
  • A: See How to work with (experiment with) Wide Review -SNZ
  • A: Keep a Disposition of Comments (DoC) Document that shows review comments and acknowledgements that have been received. It is the distribution of the reviewers that shows the review has been wide.-SNZ
  • A: Ask the W3C Team if your proposed approach is likely to meet the requirements. -SNZ
Q: Is there such a thing as too many reviews?
  • A: Not really
Q: Is it possible to make too many requests for review?
  • A: unfortunately, yes there is. Multiple requests for reviews can quickly result in a situation of diminishing returns. To help address this, subsequent review requests should clearly identify the exact differences between the last review and current review.
  • A: This is also the reason that the Process clearly suggests there should be (TR) Working Drafts published when there are "significant changes that would benefit from review beyond the Working Group", rather than every day or only twice in the life of a spec…
  • A: TR Working Drafts are also useful for reviews since they provide a dated snapshot which can be recovered when the review comments are being discussed. Trying to discuss review comments against a document which has changed out of all recognition can be a frustrating and inefficient experience.

Terminology and abbreviations

Abbreviations:

Enhancement Requests

Resources

Last updated 31 Jul 2020. See the commit history.