From 195debed92332a447880cd450c35215009f0c76c Mon Sep 17 00:00:00 2001 From: Florian Rivoal Date: Tue, 8 Mar 2022 21:26:19 +0900 Subject: [PATCH] Ruby (#389) * 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 --- html-2021.html | 78 +++++++++++++++++++++++++++++++++++++++++++------- 1 file changed, 68 insertions(+), 10 deletions(-) diff --git a/html-2021.html b/html-2021.html index 366f35cc..24155c53 100644 --- a/html-2021.html +++ b/html-2021.html @@ -148,6 +148,9 @@

Scope

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 coordination with + the WHATWG Steering Group.

The community (including users, implementers, and developers) and horizontal review groups are encouraged to @@ -180,7 +183,7 @@

Normative Specifications

- 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:

@@ -221,14 +224,46 @@

Draft state: WHATWG Living Standard

+

- +

+ The Working Group will work on the following extension specifications on the Recommendation Track: +

+ +
+
W3C HTML Ruby Markup Extensions
+
+

+ 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 https://github.com/whatwg/sg/issues/184 for the rationale + leading to developing this as an extension specification. +

+ +

WHATWG coordination: Agreement on HTML Ruby Markup

+

Draft state: + W3C Working Group Note + (See also related content in: + WHATWG Living Standard, + Pull Request)

+ +

Adopted Draft: https://www.w3.org/TR/2013/WD-html-ruby-extensions-20131022/

+

Exclusion Draft: https://www.w3.org/TR/2013/WD-html-ruby-extensions-20131022/ +
+ Exclusion period began 22 October 2013; exclusion period ended 21 March 2014. +

+

Exclusion Draft Charter: https://www.w3.org/2007/03/HTML-WG-charter.html

+
+
-

- The Working Group may also work on extension specifications for HTML features - after coordination with - the WHATWG Steering Group. -

@@ -294,6 +329,18 @@

Work Mode

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.

+

+ For extension specifications, + while coordination as agreed with the WHATWG is also expected, + the Working Group will follow the more standard approach + to technical report 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 Recommendation Track + on the basis of its own consensus. +

+
@@ -302,16 +349,21 @@

Success Criteria

The Working Group will bring one or more WHATWG Review Drafts from W3C Candidate Recommendation to Proposed Recommendation.

-

In order to advance to In order to advance WHATWG Review Drafts to Candidate Recommendation (CR), 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.

The Proposed Recommendation (PR) and Recommendation (REC) endorsement will indicate that all features which do not + title="Recommendation">Recommendation (REC) endorsement of WHATWG Review Drafts will indicate that all features which do not have at least two independent implementations are considered informative, not normative, for W3C purposes.

+

+ In order to advance to Proposed Recommendation, + each extension specification + is expected to have at least two independent implementations of every feature defined in the specification. +

Each specification is encouraged to contain or point to considerations detailing all known security and privacy implications for implementers, Web authors, and end users.

@@ -427,6 +479,12 @@

the public mailing list public-html@w3.org (archive).

+

+ For extension specifications, + this group primarily conducts its technical work + through its own GitHub repositories. + The public is invited to review, discuss and contribute to this work. +

@@ -603,7 +661,7 @@

@@ + 2 years -

Update to the WHATWG MOU. Added Fetch.

+

Update to the WHATWG MOU. Added Fetch and Ruby Markup Extensions.