-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[wg/did] Charter proposal: rechartering the Decentralized Identifier WG #376
Comments
memo for HR groups |
The following paragraph is currently in the charter, but @plh suggested that it should rather be (1) removed from the charter and (2) included in the email to the AC announcing the proposed charter:
|
No comment nor request from i18n |
I'm writing on behalf of the Accessible Platform Architectures (APA) WG. We have a question: one of our aspirations is to help the industry move away from CAPTCHAs, as they pose significant accessibility barriers (our document there proposes some alternatives, as well as describing the problems). We got the impression that a W3C group may be working towards replacing CAPTCHAs. Would that involve your group? If so, we'd love to see it mentioned in the charter. If not, we're happy to sign off on your charter. |
@matatk Though DIDs may be useful in some designs for replacing CAPTCHAs, I expect Verifiable Credentials to play a much more important role. |
Thanks @brentzundel, that makes sense. We have a long-running thread with Verifiable Credentials, so will pick it up. Meanwhile, I re-confirm that we're happy to sign off on your charter. @ruoxiran explained how I can do that by adjusting the labels, so I'll do that now. |
update: the Team is looking into a potential concern |
I'm happy to meet with the team to discuss |
update: the Team is looking to gather more information from the DiD Working Group. |
The latest attempt at resolving the formal objections failed. We started with 4 formal objections, resolved 2, and received an additional objection yesterday. A Council will need to look at the remaining formal objections. |
As background, charter sent for AC review on 7 August 2023 (public) |
For details, see referral to W3C Council. |
@plehegar I can't tell from that link -- will there be an announcement of the report, and will there be an opportunity for input to the council by the AC and/or public? |
Note that the Team Report, if it can be shared, is added to the Formal Objection Dashboard this is the place to track Formal Objections status. |
Thanks @ylafon. That dashboard is very hard to find unless you're 'in the know' -- perhaps it could be linked from https://www.w3.org/Member (although that page is already very crowded and hard to navigate)? |
@koalie ^ |
Council requested clarification and a 28 days review period. Deadline is 12 April 2024. Latest proposed charter. |
Hi @mnot I added a link to the formal objection dashboard in the right-hand side menu of the Member homepage. |
Thank you @koalie! |
The latest proposed charter did not receive formal objections and the Council was dissolved. |
Note this should be "did not receive Formal Objections". |
quite minor points (per recent template change)
|
The council approved the creation of the WG, and the call for participation was sent: https://lists.w3.org/Archives/Member/w3c-ac-members/2024AprJun/0016.html |
New charter proposal, reviewers please take note.
Charter Review
Charter: https://w3c.github.io/did-wg-charter/
What kind of charter is this? Check the relevant box / remove irrelevant branches.
Existing WG recharter
current charter at https://w3c.github.io/did-wg-charter/
Horizontal Reviews: apply the Github label "Horizontal review requested" to request reviews for accessibility (a11y), internationalization (i18n), privacy, and security. Also add a "card" for this issue to the Strategy Funnel.
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, ...)
Anything else we should think about as we review?
The text was updated successfully, but these errors were encountered: