resources: didwebs-tf-2026-01-20
This data as json
| id | type | name | url | maintainer | status | last_checked | date | year | level | evidence | access | abstract | authors | series | chair | minutes | recording | media | decisions | version | language | license | release | pushed | depends | since | via | summary | note | has_abstract | has_summary | kind | sector | country | products |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| didwebs-tf-2026-01-20 | meeting | did:webs Task Force meeting, 2026-01-20 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/477233177 | Trust over IP (did:webs Task Force) | quiet | 2026-10-15 | 2026-01-20 | 2026 | practitioner | official | public | A Dossier specification discussion led by Hardman covered how to express arity for group operators (MGRP, RMGRP) and qualifications for QGRP via an edge pointing to a required credential such as a vLEI (verifiable Legal Entity Identifier), with Smith noting that properties can be added to edges in a labeled property graph. The did:webs portion confirmed the whois section was removed, opened issue 168, and explained that a did:web DID (decentralized identifier) can be trusted only when a designated aliases ACDC in the keri.cesr stream commits to it, with proposed language highlighting that this lets a did:web DID be revoked after a DNS (Domain Name System) hijack. Next steps included listing ConditionalProof2022 as a DID extension and scheduling a second deep dive with the DIF (Decentralized Identity Foundation) Recommended DID Methods Working Group. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/477233177 | didwebs-task-force | 1 | 0 |