Clarify informing a broader scope of technical and community reports #143
Conversation
There was a problem hiding this comment.
I think we should hold this a bit so that we can make the couple changes Angel's asking for as editorial changes, which don't require any review beyond the TAG, per https://www.w3.org/policies/process/#revising-memo. But as soon as we start on the next version, +1 for bringing this in.
| new technical and community reports, and | ||
| updates to published reports. |
There was a problem hiding this comment.
I think we ought to keep mentioning specifications and recommendations, since non-W3C readers might not realize that "reports" is a superset (they might also not realize that "standards" are included in "recommendations"), but +1 on broadening the purpose like this.
Perhaps:
the purpose of this document is to inform wide review of
charters and reports produced by the web community,
including specifications, W3C recommendations, and technical and non-technical reports.
(Apologies that Github doesn't let me make this a suggested change.)
The categories in that last line overlap, and I'm wondering if it'll be more confusing to list them as-is, or to use extra words to point out that they overlap.
Clarifies that the Statement is not limited to "specifications" but extends to all W3C technical or community reports, and updates to those reports.