suggested process for adding new features to HTML 5.1

Hi all,

on recent threads [1], the subject of how and what new features (in this
case I am referring to the addition of attributes or elements) get added to
HTML5.1, has arisen.

The current situation appears to be:


   - New features originating from the WHATWG spec can be added without a
   CFC from the working group
   - There is no clear path for features originating from other groups or
   from within the HTML WG to be added to HTML 5.1.


I suggest that for any new feature (addition of an attribute or element) or
major change in a current feature (removal or redefining of its
semantics/function) regardless of origin, that A CFC occur.
If a CFC passes without objection (objections are processed as per WG
process by the chairs), the addition may upon request be merged into HTML
5.1. If there are objections (upheld by the chairs) the feature may be
pursued as an extension spec subject to the usual WG process for extension
specs.

In the case where there are multiple overlapping new feature proposals
(example srcset and picture) that they be developed as extension specs
until consensus emerges on one of the proposals, which then may be added to
HTML 5.1

In the case where an extension spec is developed that competes with a
feature currently in HTML 5.1 and is published as a FPWD, the feature in
HTML 5.1 is pulled out of the spec and may be developed as an extension spec

In the case where there is a feature developed as an extension spec that
has reached FPWD and with no competing proposals, upon request, the
feature  be merged into HTML5.1
As for other features originating from the WHATWG, the editor of a merged
extension spec can continue to develop the feature via the spec and changes
are pulled into HTML 5.1 subject to usual WG oversight.


[1]
http://lists.w3.org/Archives/Public/public-html-admin/2012Dec/thread.html
-- 
with regards

Steve Faulkner
Technical Director - TPG