[w3ctag/design-reviews] [wg/i18n-core] i18n WG rechartering 2025 (Issue #1180)

w3cbot created an issue (w3ctag/design-reviews#1180)

This issue was created because the 'horizontal review requested' label was added to
§ https://github.com/w3c/strategy/issues/534

This review is requested prior to the [Advisory Committee Review](https://www.w3.org/guide/process/charter.html#ac-review).

New charter proposal, reviewers please take note.

# Charter Review

[WG Charter](https://w3c.github.io/i18n-activity/i18n-wg/charter.html)

[diff from charter template for the WG](https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fw3c.github.io%2Fcharter-drafts%2Fcharter-template.html&doc2=https%3A%2F%2Fw3c.github.io%2Fi18n-activity%2Fi18n-wg%2Fcharter.html)

Expected end of charter refinement phase: unknown

If applicable:

[diff from previous WG charter](https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FInternational%2Fgroups%2Fwg%2Fcharter.html&doc2=https%3A%2F%2Fw3c.github.io%2Fi18n-activity%2Fi18n-wg%2Fcharter.html)

[chair dashboard for the WG](https://www.w3.org/PM/Groups/chairboard.html?gid=wg/i18n-core)

What kind of charter is this? Check the relevant box / remove irrelevant branches. 

 
* Existing 
 - [x] Existing WG recharter 
 
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](https://github.com/orgs/w3c/projects/97/views/2).**

## Communities suggested for outreach

- HTML
- Browser vendors

## 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](https://www.w3.org/TR/html-ruby-extensions/) spec will be transferred from the HTML working group, and the [Internationalization Glossary](https://www.w3.org/TR/i18n-glossary/) will change from a Note to REC-track (per https://github.com/w3c/i18n-glossary/issues/78 ).

In addition, the group will incubate the [Message Resources](https://github.com/w3c/i18n-discuss/blob/gh-pages/explainers/message-resources.md) proposal, and it may continue to be developed in the WG in the future.

## Charter facilitator(s)

cc @xfq

<!-- Content below this is maintained by @w3c-tag-bot -->
---

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1180


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1180
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1180@github.com>