Re: CfC to publish DeviceOrientation Event CR Snapshot - review by 11 March

> On 14 Mar 2024, at 3:45 AM, Kostiainen, Anssi <anssi.kostiainen@intel.com> wrote:
> 
> Hi Marcos, 
> 
> I observe the specification satisfies Candidate Recommendation transition requirements [1], no "at risk" features [2] were brought to the attention of the Working Groups during Call for Consensus.

Right, but you only gave WebApps a week. That’s not long enough. 

> Based on your comments, you have Proposed Recommendation requirements in mind. That’s a higher bar than what is required now. A comprehensive implementation report is not expected for this Candidate Recommendation Snapshot, neither is 100% pass rate nor a complete test suite. After this CRS we start working toward the milestone you had in mind.

WebApps charter explicitly states that, "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.”

We added that on purpose, to prevent single engine specs going to CR. If we want the spec to go to CR, then we should get multiple implementers onboard for every feature (and either lobby for or drop the ones that don’t have consensus) - and no opposition. 

> Considering the above, using the W3C Process as a guide, my recommendation is to initiate the transition request.

WebApp's Charter specifically prevents stuff going to CR that’s not supported by multiple engines. If we want to get this to CR, we need to work together on getting features supported in browser engines, not just following the W3C Process (which would not allow us to proceed out of CR regardless, due to lack of second implementation on various things). 

[1] “Success Criteria” of  https://www.w3.org/2022/04/webapps-wg-charter.html

Received on Friday, 22 March 2024 07:53:50 UTC