Merge pull request #519 from w3c/simoneonofri-fedid-w3c-coordination

[wg/fedid] Update W3C Coordination

2024/wg-fedid.html

@@ -351,32 +351,27 @@ <h2>Coordination</h2>
 
       <section>
         <h3 id="w3c-coordination">W3C Groups</h3>
-<dl>
-        <dt><a href="https://www.w3.org/groups/cg/fed-id" rel="nofollow">Federated Identity Community Group</a></dt>
-<dd>This Working Group will work closely with FedIDCG. The expectation is
-that FedIDCG will incubate proposals which it then hands off to this
-Working Group for standardization. Most proposals in this Working Group
-should start in FedIDCG.</dd>
-<dt><a href="https://www.w3.org/Privacy/IG/" rel="nofollow">Privacy Interest Group (PING)</a></dt>
-<dd>This Working Group will coordinate with PING on the development of
-principles that will guide the development of privacy-preserving
-capabilities while still supporting federated authentication and
-authorization flows.</dd>
-<dt><a href="https://www.w3.org/2011/webappsec/" rel="nofollow">Web Application Security Working Group (WebAppSec)</a></dt>
-<dd>WebAppSec is both a potential venue for standardization of
-security-related capabilities and a source of expertise on web privacy.</dd>
-<dt><a href="https://privacycg.github.io/" rel="nofollow">Privacy Community Group</a></dt>
-<dd>The Privacy Community Group is developing privacy-focused features. This
-working group is expected to regularly coordinate with the Privacy CG to
-ensure that the work of the two groups is not in conflict.</dd>
-<dt><a href="https://www.w3.org/groups/wg/webauthn/" rel="nofollow">Web Authentication (WebAuthn) Working Group</a></dt>
-<dd>While we are not developing an authentication mechanism, this work must operate in conjunction with existing authentication mechanisms. The WebAuthn Working Group may provide input and guidance for this requirement.</dd>
-<dt><a href="https://www.w3.org/WAI/APA/" rel="nofollow">Accessible Platform Architectures (APA) Working Group</a></dt>
-<dd>The APA WG seeks to ensure that accessibility is kept front of mind, as authentication timing and the reliance on short term memory are known and thorny topics for people with disabilities. APA WG can represent these issues that have been raised in the Cognitive Accessibility (COGA) TF, and Accessibility Guidelines (AG) WG.
-<dt><a href="https://www.w3.org/groups/wg/vc/" rel="nofollow">Verifiable Credentials Working Group</a></dt>
-<dd>The VC WG is a likely venue for standardization of Data Model for Verifiable Credentials and they are an important stakeholder in the identity space to coordinate with.
-
-</dl>
+        <dl>
+          <dt><a href="https://www.w3.org/WAI/APA/" rel="nofollow">Accessible Platform Architectures Working Group</a></dt>
+          <dd>The Accessible Platform Architectures Working Group seeks to ensure that accessibility is kept front of mind, as authentication timing and the reliance on short term memory are known and thorny topics for people with disabilities. Our group is expected to regularly coordinate with them for accessibility-related issues.</dd>
+          <dt><a href="https://www.w3.org/2019/did-wg/" rel="nofollow">Decentralized Identifier Working Group</a></dt>
+          <dd>The Decentralized Identifier Working Group is the maintainer of Decentralized Identifiers, one of the core building blocks of Digital Identities. Our group is expected to communicate with them for Digital Identities related issues.</dd>
+          <dt><a href="https://www.w3.org/groups/cg/fed-id" rel="nofollow">Federated Identity Community Group</a></dt>
+          <dd>The Federated Identity Community Group is to provide a forum focused on incubating web features that will both support federated identity and prevent untransparent, uncontrollable tracking of users across the web. Our group is expected to regularly coordinate with them to put in the standardization track incubated proposals.</dd>
+          <dt><a href="https://privacycg.github.io/" rel="nofollow">Privacy Community Group</a></dt>
+          <dd>The Privacy Community Group is to incubate privacy-focused web features and APIs to improve user privacy on the web through enhanced browser behavior. Our group is expected to regularly coordinate with them for privacy-related issues.</dd>
+          <dt><a href="https://www.w3.org/Privacy/IG/" rel="nofollow">Privacy Interest Group</a></dt>
+          <dd>The Privacy Community Interest Group monitors ongoing privacy issues that affect the Web, investigates potential areas for new privacy work, and provides guidelines and advice for addressing privacy in standards development, including privacy considerations in specifications. Our group is expected to coordinate with them regularly on privacy-related issues.
+          </dd>
+          <dt><a href="https://www.w3.org/2011/webappsec/" rel="nofollow">Web Application Security Working Group</a></dt>
+          <dd>The Web Application Security Working Group develops mechanisms and best practices that improve the security of Web Applications. Our group is expected to coordinate with them for security-related issues.</dd>
+          <dt><a href="https://www.w3.org/groups/wg/vc/" rel="nofollow">Verifiable Credentials Working Group</a></dt>
+          <dd>The Verifiable Credentials Working Group is the venue for standardizing the Data Model for Verifiable Credentials. Our group is expected to coordinate with them for format and protocol-related issues.
+          </dd>
+          <dt><a href="https://www.w3.org/groups/wg/webauthn/" rel="nofollow">Web Authentication Working Group</a></dt>
+          <dd>The Web Authentication Working Group is to define a client-side API that provides strong authentication functionality to web applications. While we are not developing an authentication mechanism, our group is expected to coordinate with them to provide feedback on authentication-related issues.
+          </dd>
+        </dl>
       </section>
 
       <section>