Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Google Formal Objection to CR Transition of DOM4.1 #177
Google raises a Formal Objection to the transition of DOM4.1 to Candidate Recommendation.
We would like to reiterate our statement on the CfC that this is particularly bad timing for this transition. W3C has noted before that two specs covering the same subject with normative differences between them is a design flaw. Given that there is an opportunity to change this design flaw, it is not appropriate to advance the DOM4.1 spec at this time. The argument provided by the chairs was that the charter was approved, hence this transition is justified. However, there are several dependencies that have changed since the charter was approved, and those should be reported and considered by the chairs, as per W3C Process.
As per the W3C Process document, the following are some of W3C’s requirements for advancement to candidate recommendation. Our concerns on those inline.
With these concerns in mind, Google formally objects to this Candidate Recommendation Transition. Our biggest concern is the lack of engagement and discussion, and the absence of any attempts to resolve major differences in the Working Group from several participants.
referenced this issue
Apr 11, 2018
@henceproved thank you for these comments.
They outline technical areas of concern that Wide Review is intended to uncover, and which we will indeed consider carefully before making any request for transition.
We will likewise publish the proposed exit criteria. As is our working practice, they are materially the same as for the DOM 4 specification.
For reference: DOM 4 apparently didn't have a CR, and thus no CR. exit criteria.
The DOM 4 PR draft said this:
It seems unlikely DOM 4.1 could meet the equivalent of those criteria as written.