resources: acdc-tf-2021-11-08
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| acdc-tf-2021-11-08 | meeting | ACDC Task Force meeting, 2021-11-08 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22993868 | Trust over IP (ACDC Task Force) | quiet | 2026-10-15 | 2021-11-08 | 2021 | practitioner | official | public | Announcements noted the Own Your Own DID (did:oyd) method specification, which appears to be a simple form of a KERI event log. Zundel reported on the W3C (World Wide Web Consortium) VC (verifiable credential) version 2 charter: ACDC is in scope and participation is needed, but the uncertain DID (decentralized identifier) specification approval makes the VC timeline uncertain. The deliverables table gained new specification entries, and the ACDC specification was reviewed. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22993868 | acdc-task-force | 1 | 0 |