Ah, good point. Yes, to the best of my understanding so far, entirely different projects in terms of motivations and technology choices.

Very unfortunate name collision, which we were planning to address once we know more what shape this takes.

For context, WebID's name inspiration/context come a lot more from OpenID ("OpenID built on the Web") and BrowserID (Mozilla Personas) than the WebID you are pointing to (which we only became aware much later in the process).

I spent a good 15 minutes trying to understand the relationship. W3C WebID is good technology, useful as heck. Used in Solid. In short, it's a way for users to have declared presence on the web. I kept looking for it's presence in this spec.

Current WebID draft.

WebID specifications: https://www.w3.org/2005/Incubator/webid/spec/

WebID Community Group: https://www.w3.org/community/webid/

We generally refer to WebID as an identifier (eg. HTTP URI) to denote an agent. WebID is central to authentication (eg. WebID-TLS, WebID/Solid-OIDC) and authorization (eg. Web Access Control / ACL).

WICG/WebID appears to share some problems, motivations, ... with the prior/ongoing WebID space but it may not be entirely aligned in terms of goals or technology choices.

The work using/extending WebID is also carried under the W3C Solid Community Group ( https://www.w3.org/community/solid/ ):

• Solid Ecosystem specification: https://github.com/solid/specification
• Authentication: https://github.com/solid/authentication-panel
• Authorization: https://github.com/solid/authorization-panel

I suggest that we identify areas where synergy may be possible.