- From: himorin / Atsushi Shimono via GitHub <noreply@w3.org>
- Date: Thu, 29 Jan 2026 05:14:16 +0000
- To: public-privacy@w3.org
himorin has just labeled an issue for https://github.com/w3c/strategy as "Horizontal review requested": == [wg/das] Devices and Sensors Working Group 2026 Charter == New charter proposal, reviewers please take note. # Charter Review [Charter](https://w3c.github.io/charter-drafts/2026/das-wg-charter.html) [diff from charter template](https://services.w3.org/htmldiff?doc1=https://w3c.github.io/charter-drafts/charter-template.html&doc2=https://w3c.github.io/charter-drafts/2026/das-wg-charter.html) Expected end of charter refinement phase: [2026-02-12](https://lists.w3.org/Archives/Member/w3c-ac-members/2026JanMar/0010.html) If applicable: [diff from previous charter](https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2F2024%2F02%2Fdas-wg-charter.html&doc2=https%3A%2F%2Fw3c.github.io%2Fcharter-drafts%2F2026%2Fdas-wg-charter.html) [chair dashboard](https://www.w3.org/PM/Groups/chairboard.html?gid=wg/das) 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 ## Known or potential areas of concern Where would charter proponents like to see issues raised? (this strategy funnel issue, a different github repo, email, ...) * [Recommendation from "W3C Council Report on the Formal Objection Against Vibration API Obsoletion (Round 2)"](https://www.w3.org/2025/08/vibration2-council-report.html#recommendations) ## Anything else we should think about as we review? Note: proposed chairs should be copied @... on this issue. /cc @anssiko @reillyeon Note: The Technical Strategy Team Lead or Project & Process Team Lead will assign the issue to a [Charter Facilitator](https://www.w3.org/guide/process/charter.html#cr-acceptance) for new charters. For rechartering, the team contact is the Charter Facilitator by default, please assign the issue to them directly. See https://github.com/w3c/strategy/issues/530 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 29 January 2026 05:14:17 UTC