search

w3c / webappsec

Web Application Security Working Group repo
https://www.w3.org/groups/wg/webappsec/
Other
605 stars 148 forks source link

Clarify that new feature limit applies only once a spec hits CR #588

Closed samuelweiler closed 3 years ago

samuelweiler commented 3 years ago

Per suggestion from @dontcallmedom

annevk commented 3 years ago

Doesn't this mean that everything that's in the initial CR might lack this? This seems like an incentive to not go to CR or instead of maintaining a CR, start a new document.

mikewest commented 3 years ago

My view is that shifting from WD to CR would imply the kind of commitments that we'd ask for when changing a CR. Assuming Mozilla, Apple, Google, Microsoft, Brave, etc. remain members of the WG, that seems possible. Perhaps we could make that explicit?

samuelweiler commented 3 years ago

How's this?

"In order to advance to Candidate Recommendation and to add features after reaching Candidate Recommendation, each feature is expected to be supported by at least two implementations, which may be judged by factors including existing implementations, expressions of interest, and lack of opposition."

And, as before:

In order to advance to Proposed Recommendation, each normative specification is expected to have at least two independent implementations of every feature defined in the specification.