Skip to content

Commit

Permalink
Ruby (w3c#389)
Browse files Browse the repository at this point in the history 
* Complete the description of work on extension specifications

Include extensions in the scope, adjust existing phrasing meant to cover W3C
publication of WHATWG Living standards to scope it to that, and add
generic wording to handle work on extensions.

* Add Ruby Markup Extensions as a deliverable
  • Loading branch information
@frivoal
frivoal authored Mar 8, 2022
1 parent 8656ddc commit 195debe
Showing 1 changed file with 68 additions and 10 deletions.
78 changes: 68 additions & 10 deletions html-2021.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -148,6 +148,9 @@ <h2>Scope</h2>
workstreams,
and to bring WHATWG HTML and DOM Review Drafts to Recommendation. The Working Group also has the ability
to bring the Fetch review drafts to Recommendation.
The Working Group may also work on extension specifications for HTML features
in <a href='https://github.com/w3c/whatwg-coord/issues'>coordination with
the WHATWG Steering Group</a>.
</p>
<p>
The community (including users, implementers, and developers) and horizontal review groups are encouraged to
Expand Down Expand Up @@ -180,7 +183,7 @@ <h3>
Normative Specifications
</h3>
<p>
The Working Group will deliver the following W3C normative specifications:
The Working Group will deliver the following W3C normative specifications based on WHATWG Living Standards:
</p>
<dl>

Expand Down Expand Up @@ -221,14 +224,46 @@ <h3>
<p class="draft-status"><b>Draft state:</b> <a href="https://fetch.spec.whatwg.org/">WHATWG Living
Standard</a></p>
</dd>
</dl>

</dl>
<p>
The Working Group will work on the following extension specifications on the <a href="https://www.w3.org/Consortium/Process/#rec-track">Recommendation Track</a>:
</p>

<dl>
<dt id="ruby" class="spec"><a href="https://www.w3.org/TR/html-ruby-extensions/">W3C HTML Ruby Markup Extensions</a></dt>
<dd>
<p>
This specification extends and refines the facilities provided by HTML to support “Ruby”,
which is a form of interlinear annotations commonly used in East Asia,
primarily (but not exclusively) for phonetic assistance.
The minimal ruby markup model currently described in the HTML Living Standard
is insufficient to satisfy known ruby use cases and accessibility requirements.
This extension specification
(which may be split into multiple “levels” based on feature implementation status)
will describe a more complete model
based on prior work by the W3C HTML, i18n, and CSS Working Groups,
and consultation with the accessibility community in East Asia.
See <a href="https://github.com/whatwg/sg/issues/184">https://github.com/whatwg/sg/issues/184</a> for the rationale
leading to developing this as an extension specification.
</p>

<p><b>WHATWG coordination:</b> <a href="https://www.w3.org/2022/02/ruby-agreement">Agreement on HTML Ruby Markup</a></p>
<p class="draft-status"><b>Draft state:</b>
<a href="https://www.w3.org/TR/2014/NOTE-html-ruby-extensions-20140204/">W3C Working Group Note</a>
(See also related content in:
<a href="https://html.spec.whatwg.org/multipage/text-level-semantics.html#the-ruby-element">WHATWG Living Standard</a>,
<a href="https://github.com/whatwg/html/pull/6478">Pull Request</a>)</p>

<p class="draft-status"><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2013/WD-html-ruby-extensions-20131022/">https://www.w3.org/TR/2013/WD-html-ruby-extensions-20131022/</a></p>
<p class="draft-status"><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2013/WD-html-ruby-extensions-20131022/">https://www.w3.org/TR/2013/WD-html-ruby-extensions-20131022/</a>
<br>
Exclusion period began <a href="https://lists.w3.org/Archives/Member/member-cfe/2013Oct/0004.html">22 October 2013</a>; exclusion period ended 21 March 2014.
</p>
<p class="draft-status"><b>Exclusion Draft Charter:</b> <a href="https://www.w3.org/2007/03/HTML-WG-charter.html">https://www.w3.org/2007/03/HTML-WG-charter.html</a></p>
</dd>
</dl>

<p>
The Working Group may also work on extension specifications for HTML features
after <a href='https://github.com/w3c/whatwg-coord/issues'>coordination with
the WHATWG Steering Group</a>.
</p>
</section>

<section id="timeline">
Expand Down Expand Up @@ -294,6 +329,18 @@ <h2>Work Mode</h2>
<p>The HTML Working Group is expected to endorse a WHATWG HTML or DOM Review Draft to Candidate Recommendation
at least once per 12 month period.</p>

<p>
For extension specifications,
while coordination <a href="https://github.com/w3c/whatwg-coord/">as agreed with the WHATWG</a> is also expected,
the Working Group will follow the more standard approach
to <a href="https://www.w3.org/Consortium/Process/#Reports">technical report</a> development and publication:
the Working Group will appoint its own editors,
develop its own drafts,
accept and process feedback,
and progress the documents along the <a href="https://www.w3.org/Consortium/Process/#rec-track">Recommendation Track</a>
on the basis of its own consensus.
</p>

</section>

<section id="success-criteria">
Expand All @@ -302,16 +349,21 @@ <h2>Success Criteria</h2>
The Working Group will bring one or more WHATWG Review Drafts from W3C Candidate Recommendation to Proposed
Recommendation.
</p>
<p>In order to advance to <a href="https://www.w3.org/Consortium/Process/#RecsCR"
<p>In order to advance WHATWG Review Drafts to <a href="https://www.w3.org/Consortium/Process/#RecsCR"
title="Candidate Recommendation">Candidate Recommendation (CR)</a>, each feature is expected to be marked
with its implementation status. The CR will indicate that all features with fewer than two implementations are
at-risk.
</p>
<p>The <a href="https://www.w3.org/Consortium/Process/#RecsPR" title="Proposed Recommendation">Proposed
Recommendation (PR)</a> and <a href="https://www.w3.org/Consortium/Process/#RecsW3C"
title="Recommendation">Recommendation (REC)</a> endorsement will indicate that all features which do not
title="Recommendation">Recommendation (REC)</a> endorsement of WHATWG Review Drafts will indicate that all features which do not
have <a href="https://www.w3.org/Consortium/Process/#implementation-experience">at least two independent
implementations</a> are considered informative, not normative, for W3C purposes. </p>
<p>
In order to advance to <a href="https://www.w3.org/Consortium/Process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>,
each extension specification
is expected to have <a href="https://www.w3.org/Consortium/Process/#implementation-experience">at least two independent implementations</a> of every feature defined in the specification.
</p>
<p>Each specification is encouraged to contain or point to considerations detailing all known security and
privacy implications for implementers, Web authors, and end users.</p>
<p>
Expand Down Expand Up @@ -427,6 +479,12 @@ <h2>
the public mailing list <a id="public-name" href="mailto:[email protected]">[email protected]</a> (<a
href="https://lists.w3.org/Archives/Public/public-html/">archive</a>).
</p>
<p>
For extension specifications,
this group primarily conducts its technical work
through its own <a id="public-github-ext" href="https://github.com/w3c/htmlwg/">GitHub repositories</a>.
The public is invited to review, discuss and contribute to this work.
</p>
</section>


Expand Down Expand Up @@ -603,7 +661,7 @@ <h3>
@@ + 2 years
</td>
<td>
<p>Update to the WHATWG MOU. Added Fetch.</p>
<p>Update to the WHATWG MOU. Added Fetch and Ruby Markup Extensions.</p>
</td>
</tr>
</tbody>
Expand Down

0 comments on commit 195debe

Please sign in to comment.