- From: Sam Ruby via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 01 Oct 2012 15:43:37 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/decision-policy
In directory hutz:/tmp/cvs-serv3027
Modified Files:
html5-2014-plan.html
Log Message:
Update plan
Index: html5-2014-plan.html
===================================================================
RCS file: /sources/public/html5/decision-policy/html5-2014-plan.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- html5-2014-plan.html 19 Sep 2012 20:30:10 -0000 1.1
+++ html5-2014-plan.html 1 Oct 2012 15:43:35 -0000 1.2
@@ -232,7 +232,7 @@
5.1 Recommendation in 2016Q4</a>.</li>
<li>
Use
- <a href="http://lists.w3.org/Archives/Public/public-html/2012Sep/0215.html">Candidate
+ <a href="http://dev.w3.org/html5/decision-policy/public-permissive-exit-criteria.html">Candidate
Recommendation exit criteria</a>
to focus testing where it is advisable (e.g. new features), without
wasting time on testing where it is inappropriate (such as when
@@ -276,7 +276,7 @@
</p>
<p>As we <a href="http://lists.w3.org/Archives/Public/public-html/2012Apr/0204.html">announced
- on 23 April</a>, at Ian Hickson's request, we looked to change the
+ on 23 April</a>, at Ian Hickson’s request, we looked to change the
editorial team for HTML5. We've put together an effective editorial team
who are rapidly coming up to speed. We suffered a short term schedule
impact for doing so, but felt it was the right decision to allow us to
@@ -342,7 +342,7 @@
development is needed to move forward.</p>
<p>With all the above considered, we believe that if we were to introduce
- into this context a compressed schedule in response to the CEO's push for
+ into this context a compressed schedule in response to the CEO’s push for
a REC in 2014, this would inevitably lead to even more Formal Objections
and schedule risk.</p>
@@ -370,20 +370,28 @@
issues or can be addressed by a
non-<a href="http://www.w3.org/2005/10/Process-20051014/tr#substantive-change">substantive</a>
change to the specification.</li>
- <li>For <a href="http://www.w3.org/html/wg/tracker/issues/open">issues</a>:
+
+ <li id="plan-issues"><p>For
+ <a href="http://www.w3.org/html/wg/tracker/issues/open">issues</a>:
require actual specification text to be published in the form of
<a href="#extension-specs">extension specifications</a> first, and
- only after said text meets the <a href="http://lists.w3.org/Archives/Public/public-html/2012Sep/0215.html">exit
+ only after said text meets the <a href="http://dev.w3.org/html5/decision-policy/public-permissive-exit-criteria.html">exit
criteria for CR</a>, consider folding the result into the core
- specification. To prevent unnecessary confusion, drop explicit
- indications that any given extension is obsolete once an extension
- specification exists that has been published as a FPWD. Issues that
+ specification.</p>
+ <p>To prevent unnecessary confusion, the HTML5
+ specification will drop explicit indications that any given
+ extension is obsolete once an extension specification exists that
+ has been published as a FPWD. Additionally, the W3C staff will
+ watch for drafts being published and keep the
+ <a href="http://validator.w3.org/">W3C validator</a> up to date as
+ appropriate.</p>
+ <p>Issues that
are raised that concern <a href="http://www.w3.org/wiki/Spec_Advancement">interoperability</a>
issues will be considered during as a part of HTML5.0, all others
will be considered in the HTML 5.1 timeframe. As needed, split out
controversial or unstable text into extension specifications. A
detailed, issue by issue, list of proposals appears
- <a href="#issues">later in this document</a>.</li>
+ <a href="#issues">later in this document</a>.</p></li>
</ul>
</li>
<li>
@@ -402,7 +410,7 @@
<p>
Proceed immediately after these objections are processed to CR on
HTML 5.0 with
- <a href="http://lists.w3.org/Archives/Public/public-html/2012Sep/0215.html">Public
+ <a href="http://dev.w3.org/html5/decision-policy/public-permissive-exit-criteria.html">Public
Permissive proposed CR exit criteria</a>
</p>
</li>
@@ -457,7 +465,7 @@
<p>We also begin work on a systematic HTML5.0 Testing Plan, with the goals
being:</p>
<ul>
- <li>identifying areas that are known to be inter-operable and don't need
+ <li>identifying areas that are known to be interoperable and don't need
further tests.</li>
<li>identify areas that are known not to be interoperable, and to be
removed without the need for investing time in the creation of tests.</li>
@@ -526,36 +534,37 @@
<p>During the CR period for HTML5.0:</p>
<ul>
<li>we determine which features are likely to meet the
- <a href="http://lists.w3.org/Archives/Public/public-html/2012Sep/0215.html">“Public
+ <a href="http://dev.w3.org/html5/decision-policy/public-permissive-exit-criteria.html">“Public
Permissive” CR exit criteria</a>,
</li>
<li>we create a “stable HTML5.0” draft which includes just those
“stable” features, and which omits the remaining “unstable”
features</li>
- <li>we create an HTML 5.1 editor’s draft which is a superset of the
- stable HTML5.0 but with the “unstable” features included instead of
- omitted, and also with any new proposed features included</li>
+ <li id="unstable">we create an HTML 5.1 editor’s draft
+ which is a superset of the stable HTML5.0. “Unstable” features from
+ HTML 5.0 and proposed features may be included in the HTML 5.1
+ draft.</li>
</ul>
<p>... and the cycle repeats:</p>
<ul>
<li>we again determine which features are likely to meet the
- <a href="http://lists.w3.org/Archives/Public/public-html/2012Sep/0215.html">“Public
+ <a href="http://dev.w3.org/html5/decision-policy/public-permissive-exit-criteria.html">“Public
Permissive” CR exit criteria</a>,
</li>
<li>we create a “stable HTML5.1” draft which includes just those
“stable” features, and which omits the remaining “unstable”
features</li>
- <li>we create an HTML 5.2 editor’s draft which is superset of the
- stable HTML5.1 but with the “unstable” features included instead of
- omitted, and also with any new proposed features included. We
- estimate that the FPWD for HTML 5.2 would be in early 2015.</li>
+ <li>we create an HTML 5.2 editor’s draft which is a
+ superset of the stable HTML5.1. “Unstable” features from HTML 5.1 and
+ proposed features may be included in the HTML 5.2 draft. We estimate
+ that the FPWD for HTML 5.2 would be in early 2015.</li>
</ul>
<!-- ********************************************************************** -->
<h2 id="modularity">Modularity</h2>
<p>
Consistent with the
- <a href="www.w3.org/DesignIssues/Principles.html">W3C's Principles of
+ <a href="www.w3.org/DesignIssues/Principles.html">W3C’s Principles of
Design</a>
, we propose a greater reliance on
<a href="http://www.w3.org/DesignIssues/Principles.html#Modular">modularity</a>
@@ -569,14 +578,14 @@
<h3>HTML5 is good at modularity</h3>
- <p>There is a widespread belief that HTML5 is "bad at modularity". It's
+ <p>There is a widespread belief that HTML5 is “bad at modularity”. It’s
true that HTML5 originated is a large specification, and that it
- originated as a monolithic "kitchen-sink" spec with a grab bag of
+ originated as a monolithic “kitchen-sink” spec with a grab bag of
features. But HTML5 offers powerful hooks for
<a href="#extension-specs">extension specifications</a>. It allows
extension specs to define new elements, new attributes, new values for
attributes that accept defined sets of keywords, and new APIs. This
- extension capability has been widely used.”</p>
+ extension capability has been widely used.</p>
<p>Many technologies that were originally defined in HTML5 itself are now
defined in separate specifications, either in the HTML WG or in other
@@ -719,7 +728,7 @@
<h3>Extension specifications are first-class citizens</h3>
<p>Some believe that extension specifications are second-class citizens,
- or somehow "lesser" than the core HTML5 specification. On the contrary,
+ or somehow “lesser” than the core HTML5 specification. On the contrary,
the specifications in the list above are vibrant, active pieces of the Web
platform, with significant implementation traction and community
credibility. Many extensions recognized as having wide consensus are
@@ -758,7 +767,7 @@
the controversy calmed down, the spec resumed development in relative
calm.</p>
- <p>We also have a number of potential "HTML.next" efforts that are
+ <p>We also have a number of potential “HTML.next” efforts that are
actively proceeding along this direction:</p>
<ul>
@@ -814,30 +823,49 @@
</dd>
<dt id="dp">Decision Policy changes</dt>
<dd>
- <p>While some changes have already been proposed, the process of
- producing this plan has identified a small number of additional
- changes:</p>
+ <p>While
+ <a href="http://lists.w3.org/Archives/Public/public-html/2012Aug/0188.html">some
+ changes</a> have already been proposed, the process of producing
+ this plan has identified a number of additional changes:</p>
<ul>
<li>
Change the heading for the
- <a href="http://dev.w3.org/html5/decision-policy/decision-policy-v3.html#lc2">Second
+ <a href="http://dev.w3.org/html5/decision-policy/decision-policy-v3.html#cr">Second
Last Call Process Additions</a>
to one reflecting CR instead.
</li>
<li>
Extend the period of
- <a href="http://dev.w3.org/html5/decision-policy/decision-policy-v3.html#lc2-rtc">review</a>
+ <a href="http://dev.w3.org/html5/decision-policy/decision-policy-v3.html#cr-rtc">review</a>
for proposed changes from 72 hours to one week.
</li>
- <li>Open a bug to define a process for reincorporating extension
- specifications back into the core specification. This bug needs to
- be addressed before the first extension spec achieves CR exit
- criteria, and no later than the end of 2013. The process will
- require extension specs to meet CR exit criteria and to have HTML WG
- consensus for reintegration, but it will not categorically rule out
- extension specs that define new or additional features.</li>
+ <li id="cr-integration">
+ <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=18997">Define
+ a process for integrating extension specs during CR</a>.
+ </li>
+ <li id="cr-remove-early">
+ <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=18998">Define
+ a process for removing nominated at-risk features early in
+ CR</a>.
+ </li>
</ul>
</dd>
+ <dt id="status-section">HTML5 Specification
+ <a href="http://dev.w3.org/html5/spec/spec.html#status-of-this-document">status
+ section</a> changes</dt>
+ <dd>
+ <ul>
+ <li>Indicate that this specification is part of an Open Web
+ Platform Family of specifications, linking to a page (possibly on
+ a wiki) which more fully defines this relationship and links to an
+ evolving set of specifications.</li>
+ <li>Explicitly state that indications that a given construct is
+ obsolete will be dropped once an extension specification defining
+ that construct reaches FPWD</li>
+ <li>Indicate the status of the <a href="#issues">Open WG
+ Issues</a></li>
+ </ul>
+ </dd>
<dt>Lead test manager team role</dt>
<dd>
<p>A W3C staff position needs to be created, and filled, with the
@@ -886,11 +914,17 @@
participation and foster greater collaboration across different
perspectives. In addition, the chairing arrangement is under
review.</li>
- <li>
- Move responsibility for the
- <a href="http://dev.w3.org/html5/alt-techniques/">HTML5:
- Techniques for providing useful text alternatives</a>
- document from the HTML WG to the A11y TF.
+ <li id="alt-techniques">
+ Responsibility for the <a
+ href="http://dev.w3.org/html5/alt-techniques/">HTML5: Techniques
+ for providing useful text alternatives</a> document will remain
+ in the HTML WG. The A11y TF and the editor of the alt-techniques
+ document are encouraged to work directly with the editors of the
+ HTML5 document to reduce
+ <a href="http://www.davidmacd.com/WCAG/WAI/buggy.html">identified
+ differences</a>, filing new bug reports as appropriate. We will
+ revisit the responsibility of the document after the differences
+ have been resolved to the extent possible.
</li>
<li>
Update the
@@ -908,7 +942,7 @@
issues will be handled:</p>
<ul>
- <li>
+ <li id="issue-30">
<p>
<a href="http://dev.w3.org/html5/status/issue-status.html#ISSUE-030">30
longdesc</a>
@@ -933,7 +967,7 @@
</li>
</ul>
</li>
- <li>
+ <li id="issue-151">
<p>
<a href="http://dev.w3.org/html5/status/issue-status.html#ISSUE-151">151
whatwg references</a>
@@ -952,7 +986,7 @@
</li>
</ul>
</li>
- <li>
+ <li id="issue-164">
<p>
<a href="http://dev.w3.org/html5/status/issue-status.html#ISSUE-164">164
hgroup</a>
@@ -961,20 +995,28 @@
<ul>
<li>
- <p>Retain the current hgroup language in the spec. Note that a
- number of shipping browsers implement the syntax. Identify the
- semantics as an at risk feature.</p>
+ <p>Retain the current hgroup language in the
+ spec. Note that a number of shipping browsers implement the
+ syntax, but there is no currently known complete implementation
+ of the semantics. Therefore, hgroup will be marked as an
+ at-risk feature.</p>
- <p>Allow extension specs to be written that MAY define new
- document content, MAY prohibit certain otherwise conforming
- content (e.g. prohibit use of <hgroup>s), and MAY change the
- semantics of existing elements. If such a specification obtains
- consensus and meets the proposed CR exit criteria -- it could be
- folded back into the core HTML spec at that time.</p>
+ <p>The <a href="#cr-remove-early">procedure
+ for early dropping of at-risk features</a> may be applied to
+ hgroup. As a result, if no reasonably complete implementations
+ are available, it is likely that it will be dropped from the
+ core spec early in CR.</p>
+
+ <p>Allow extension specs to be written that MAY define new
+ document content, MAY prohibit certain otherwise conforming
+ content (e.g. prohibit use of <hgroup>s), and MAY change
+ the semantics of existing elements. If such a specification
+ obtains consensus and meets the proposed CR exit criteria -- it
+ could be folded back into the core HTML spec at that time.</p>
</li>
</ul>
</li>
- <li>
+ <li id="issue-185">
<p>
<a href="http://dev.w3.org/html5/status/issue-status.html#ISSUE-185">185
drop pubdate</a>
@@ -983,17 +1025,15 @@
<ul>
<li>
- <p>Retain the current pubdate attribute in the spec. Identify it
- as an at risk feature.</p>
-
- <p>Allow an extension spec to be written that defines a moddate
- attribute. If such a specification obtains consensus and meets
- the proposed CR exit criteria -- it could be folded back into the
- core HTML spec at that time.</p>
+ <p>Allow an extension spec to be written that
+ defines a moddate and/or a pubdate attribute. If such a
+ specification obtains consensus and meets the proposed CR exit
+ criteria -- it could be folded back into the core HTML spec at
+ that time.</p>
</li>
</ul>
</li>
- <li>
+ <li id="issue-194">
<p>
<a href="http://dev.w3.org/html5/status/issue-status.html#ISSUE-194">194
full-transcript</a>
@@ -1001,13 +1041,15 @@
</p>
<ul>
- <li>Allow the A11y TF the authority to produce an extension spec
- that includes full-transcript. If such a specification obtains
- consensus and meets the proposed CR exit criteria by 2014Q2 it could
- be folded back into the core HTML spec at that time.</li>
+ <li>Allow the A11y TF the authority to produce one
+ or more extension specs that includes a full-transcript attribute.
+ If any such a specification obtains consensus and meets the
+ proposed CR exit criteria by 2014Q2 it could be folded back into
+ the core HTML spec at that time. The A11y Task Force is
+ encouraged to converge onto a single solution.</li>
</ul>
</li>
- <li>
+ <li id="issue-195">
<p>
<a href="http://dev.w3.org/html5/status/issue-status.html#ISSUE-195">195
form http request</a>
@@ -1025,7 +1067,7 @@
</li>
</ul>
</li>
- <li>
+ <li id="issue-200">
<p>
<a href="http://dev.w3.org/html5/status/issue-status.html#ISSUE-200">200
legend placement</a>
@@ -1039,7 +1081,7 @@
time.</li>
</ul>
</li>
- <li>
+ <li id="issue-201">
<p>
<a href="http://dev.w3.org/html5/status/issue-status.html#ISSUE-201">201
canvas-fallback</a>
@@ -1052,7 +1094,7 @@
object and related alterations to the 2d Context API</a>.</li>
</ul>
</li>
- <li>
+ <li id="issue-203">
<p>
<a href="http://dev.w3.org/html5/status/issue-status.html#ISSUE-203">203
media descriptions</a>
@@ -1067,7 +1109,7 @@
core HTML spec at that time.</li>
</ul>
</li>
- <li>
+ <li id="issue-206">
<p>
<a href="http://dev.w3.org/html5/status/issue-status.html#ISSUE-206">206
meta generator</a>
@@ -1089,7 +1131,7 @@
<p>The following is an excerpt from section
<a href="http://dev.w3.org/html5/spec/infrastructure.html#extensibility">2.2.3
Extensibility</a> of the current <a href="http://dev.w3.org/html5/spec/spec.html">HTML5
- editor's draft</a>:</p>
+ editor’s draft</a>:</p>
<blockquote>
<p>When vendor-neutral extensions to this specification are needed,
@@ -1102,7 +1144,7 @@
specifications">applicable specification</dfn>.</p>
<p>The conformance terminology for documents depends on the nature of
- the changes introduced by such applicable specificactions, and on the
+ the changes introduced by such applicable specifications, and on the
content and intended interpretation of the document. Applicable
specifications MAY define new document content (e.g. a foobar
element), MAY prohibit certain otherwise conforming content (e.g.
@@ -1113,7 +1155,7 @@
HTML5 document</a> does not depend on the use of applicable
specifications: if the syntax and semantics of a given
<a href="http://dev.w3.org/html5/spec/infrastructure.html#conforming-documents">conforming
- HTML5 document</a> document is unchanged by the use of applicable
+ HTML5 document</a> is unchanged by the use of applicable
specification(s), then that document remains a
<a href="http://dev.w3.org/html5/spec/infrastructure.html#conforming-documents">conforming
HTML5 document</a>. If the semantics or processing of a given
@@ -1123,6 +1165,8 @@
HTML5 document</a>. For such cases, the applicable specifications
SHOULD define conformance terminology.</p>
</blockquote>
+ <p>A <a href="http://www.w3.org/html/wg/wiki/ExtensionSpecifications">list
+ of extension specifications</a> can be found on the HTML WG wiki.</p>
</div>
</body>
</html>
Received on Monday, 1 October 2012 15:43:41 UTC