resources: didwebs-tf-prov-2023-09-01
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-prov-2023-09-01 | meeting | did:webs Task Force provisional meeting, 2023-09-01 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22982371 | Trust over IP (did:webs Task Force) | quiet | 2026-10-15 | 2023-09-01 | 2023 | practitioner | official | public | Discussion weighed where the reference implementation repository should live (DIF (Decentralized Identity Foundation), Open Wallet Foundation, WebOfTrust, Hyperledger Labs or ToIP (Trust over IP)) and whether did:webs should include less secure familiar mechanisms such as bare JWS (JSON Web Signature) or require KEL (key event log) anchoring, with a proposed bright-line rule that features not secured by KERI belong in did:web. A comparison of did:webs and did:keri was presented, with the recommendation that they be separate, independent specifications, and the need for a mechanism to move a did:webs identifier between domains was raised. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22982371 | https://drive.google.com/file/d/1B6YN6jxVwnTDB39cjuRs5dwCjsY6a7nc/view?usp=sharing | didwebs-task-force | 1 | 0 |