This issue was created because the 'horizontal review requested' label was added to
§ w3c/strategy#534
This review is requested prior to the Advisory Committee Review.
New charter proposal, reviewers please take note.
Charter Review
WG Charter
diff from charter template for the WG
Expected end of charter refinement phase: unknown
If applicable:
diff from previous WG charter
chair dashboard for the WG
What kind of charter is this? Check the relevant box / remove irrelevant branches.
Horizontal Reviews: apply the Github label "Horizontal review requested" to request reviews for accessibility (a11y), internationalization (i18n), privacy, security, and TAG. Also add a "card" for this issue to the Strategy Funnel.
Communities suggested for outreach
Known or potential areas of concern
Currently, no browser vendors are involved in the editing of the W3C HTML Ruby Markup Extensions spec.
Where would charter proponents like to see issues raised? this strategy funnel issue
Anything else we should think about as we review?
The HTML Ruby Markup Extensions spec will be transferred from the HTML working group, and the Internationalization Glossary will change from a Note to REC-track (per w3c/i18n-glossary#78 ).
In addition, the group will incubate the Message Resources proposal, and it may continue to be developed in the WG in the future.
Charter facilitator(s)
cc @xfq
This issue was created because the 'horizontal review requested' label was added to
§ w3c/strategy#534
This review is requested prior to the Advisory Committee Review.
New charter proposal, reviewers please take note.
Charter Review
WG Charter
diff from charter template for the WG
Expected end of charter refinement phase: unknown
If applicable:
diff from previous WG charter
chair dashboard for the WG
What kind of charter is this? Check the relevant box / remove irrelevant branches.
Horizontal Reviews: apply the Github label "Horizontal review requested" to request reviews for accessibility (a11y), internationalization (i18n), privacy, security, and TAG. Also add a "card" for this issue to the Strategy Funnel.
Communities suggested for outreach
Known or potential areas of concern
Currently, no browser vendors are involved in the editing of the W3C HTML Ruby Markup Extensions spec.
Where would charter proponents like to see issues raised? this strategy funnel issue
Anything else we should think about as we review?
The HTML Ruby Markup Extensions spec will be transferred from the HTML working group, and the Internationalization Glossary will change from a Note to REC-track (per w3c/i18n-glossary#78 ).
In addition, the group will incubate the Message Resources proposal, and it may continue to be developed in the WG in the future.
Charter facilitator(s)
cc @xfq