resources: didwebs-tf-prov-2023-08-17
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-08-17 | meeting | did:webs Task Force provisional meeting, 2023-08-17 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22979075 | Trust over IP (did:webs Task Force) | quiet | 2026-10-15 | 2023-08-17 | 2023 | practitioner | official | public | First provisional meeting: the open artifacts were reviewed (the temporary did:webs specification repository, with the earlier HackMD draft folded into it, and the did-keri-resolver reference implementation). Discussion covered whether did:webs and did:keri should be separate specifications, the resolver and service architecture, how KEL (key event log) and TEL (transaction event log) data relate to the DID (decentralized identifier) document, OOBI (out-of-band introduction) based KEL retrieval from witnesses, and follow-on points from the keri-dev meeting on watchers, duplicity detection and co-locating the DID document with its KEL. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22979075 | https://drive.google.com/file/d/1a2vIyx3Ab_FC3TpefSSoWqYAKXAK9-RC/view?usp=sharing | didwebs-task-force | 1 | 0 |