resources: didwebs-tf-2025-07-15
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-2025-07-15 | meeting | did:webs Task Force meeting, 2025-07-15 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/220069952 | Trust over IP (did:webs Task Force) | quiet | 2026-10-15 | 2025-07-15 | 2025 | practitioner | official | public | The task backlog was reviewed and is to be moved to a published did:webs TODO page, with plans to have the Python implementation pass the W3C DID (decentralized identifier) test suite in continuous integration and to make the Universal Resolver driver work correctly. Discussion covered archiving the Hyperledger Labs resolver repository, what it means to resolve a did:webs DID (full resolution requires handling identifier delegation and multi-signature), and difficulties with the restricted meeting link. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/220069952 | Archive the Hyperledger Labs resolver repository; do not return DID resolution metadata in did.json; use GLEIF-IT/did-webs-resolver as the source of truth for the did:webs resolver; rename the package from "dkr" to "dws" | didwebs-task-force | 1 | 0 |