resources
47 rows where via = "didwebs-task-force" sorted by date descending
This data as json, CSV (advanced)
Suggested facets: last_checked (date), date (date)
| 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-09-15 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2026-09-15 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/1159004224 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2026-09-15 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Smith's review comments on v0.10.3 of the did:webs specification were discussed: an interoperability-bridge explanation, corrected Direct and Indirect Mode descriptions, a broader permitted AID (autonomic identifier) syntax covering self-addressing transferable and public-key-derived transferable and non-transferable AIDs, a recovery exception to the rule that divergent KERI event streams are invalid, a deactivation path for non-transferable AIDs, and an informative W3C VC (verifiable credential) example. On the open question of complex or nested fractionally weighted thresholds, the group discussed keeping the normative text trim with a worked example in an informative appendix, noting that ConditionalProof2022 supports recursive definitions. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/1159004224 | Agreed that the specification supports complex or nested fractionally weighted thresholds | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2026-08-18 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2026-08-18 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/1074331649 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2026-08-18 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The did:webs specification was reported ready for final review and approval, with the implementation needing to catch up. Discussion covered needed specification changes, restarting the DIF (Decentralized Identity Foundation) Recommended DID (decentralized identifier) Methods process (issue 212), and the history of the resolver's placement in Hyperledger Labs. Action items included a reconciliation of the normative specification language against the Python reference implementation and a version 2 example. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/1074331649 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2026-07-21 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2026-07-21 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/1002373121 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2026-07-21 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The Dossier segment pointed to an edge operators discussion on KERIpy. For did:webs, the final specification review was reported complete with significant revisions (pull request 209), and discussion turned to restarting the DIF (Decentralized Identity Foundation) Recommended DID (decentralized identifier) Methods process. Other business covered ToIP (Trust over IP) stages of development for working groups and task forces, a "Bite Sized Trust" paper on duplicity and impersonation, the Trust Tasks work oriented toward AI, and assigning DOIs (Digital Object Identifiers) to new versions of the KERI specifications. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/1002373121 | Resume the 60-day DIF Recommended DID Methods review period | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2026-06-16 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2026-06-16 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/914817026 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2026-06-16 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The Dossier segment discussed a pull request adding new group operators, and Smith and Hardman reported a working session on open items in the Dossier specification. For did:webs, a second implementation now exists (a minimal TypeScript implementation for the DIF (Decentralized Identity Foundation) Recommended DID Methods process), the editors were completing a final revision, and there was an update on the DIF process. Zenodo access was also noted. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/914817026 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2026-03-17 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2026-03-17 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/650608643 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2026-03-17 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | For did:webs, only a few open issues remained, the repository had been renamed, the did:web to did:webs transformation and resolution rules were clarified, and the editors had revised the specification; a second implementation was now needed for DIF (Decentralized Identity Foundation) Recommended DID (decentralized identifier) method status. The Dossier segment noted one pull request against the specification and the need for a formal way to bring foreign artifacts into ACDCs. The April 15 ToIP (Trust over IP) Steering Committee meeting remained the target. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/650608643 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2026-02-17 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2026-02-17 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/564068353 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2026-02-17 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | In the Dossier specification segment, Hardman reported a long-open pull request to be merged unless questions arose and work on joint issuance that is adding edge operators to the ACDC specification. For did:webs, the DIF (Decentralized Identity Foundation) Recommended DID (decentralized identifier) Methods 60-day formal review had begun, the editors reported a review of all normative language, an updated ABNF (Augmented Backus-Naur Form) and repository cleanup, and the specification was described as substantively complete. A pathway to 1.0 was laid out: subcommittee review to March 9 using the ToIP (Trust over IP) review checklist, approval of a final draft by the KSWG co-chairs at the March 10 KSWG meeting with a resolution, public review to April 14, and submission to the ToIP Steering Committee on April 15. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/564068353 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2026-01-20 | Meetings (one per entry) 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) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2026-01-20 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link 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 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2025-12-16 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2025-12-16 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/401113089 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-12-16 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Discussion of the alsoKnownAs default concluded that a did:web DID (decentralized identifier) should appear in the DID document only when the controller has placed it in a designated aliases ACDC, since only that commitment shows the controller authorized it, and the specification and implementation were to be changed accordingly. The meeting was split with a Dossier specification discussion, whose notes cite an article on evidence-based trust in telecommunications and the notion of preponderance of evidence. The next DID community tasks were restated: W3C registration, passing the W3C test suite and evaluation against the DID traits matrix. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/401113089 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2025-11-18 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2025-11-18 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/335052801 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-11-18 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The task force removed the whois section from the specification and adopted grey highlighted boxes to mark informative versus normative language, with excess informative text to move to an annex. Remaining coding tasks were identifier delegation in the DID (decentralized identifier) document services section and default did:keri and did:web entries in alsoKnownAs, and discussion covered referencing the KERI Suite Glossary instead of copying definitions, rewriting section 19.3 to name the five DID attacks, and the "decentralised-internet-identity" tag that links specifications and glossaries. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/335052801 | Removal of the whois section (section 12) from the specification, moved, seconded and passed (four yes, one abstention); use of grey highlighted boxes to indicate informative versus normative language, moved, seconded and passed (four votes) | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2025-09-16 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2025-09-16 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/249823297 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-09-16 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Discussion covered the DIF (Decentralized Identity Foundation) Recommended DID (decentralized identifier) method process: its rationale of narrowing more than 200 DID methods to a short list in web-based, ephemeral and fully decentralized categories, the methods in review (did:webvh first, then did:cheqd, did:web+ and did:scid), and that the process makes no quality or security judgment. Independent security audits of KERI (one by Cardano, one by healthKERI, both unpublished) and an eventual security comparison of did:webvh and did:webs were raised. Action items were to arrange the did:webs submission to DIF and to look at migrating to Spec-Up-T. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/249823297 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2025-08-19 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2025-08-19 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/239370241 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-08-19 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports noted the TODO list now at the root of the did:webs meeting pages, the did:webs resolver updated and integrated with the Universal Resolver, and a request to take down the Hyperledger Labs repository so the GLEIF IT repository becomes definitive. Discussion proposed tying the ABNF (Augmented Backus-Naur Form) for the method-specific identifier to the current KERI version and restricting the AID (autonomic identifier) to valid CESR digest strings, and named the next DID (decentralized identifier) community tasks: W3C registration, passing the W3C test suite and evaluation against the DID traits matrix. Formal submission of did:webs to the DIF (Decentralized Identity Foundation) DID Methods Working Group for DIF Recommended status was proposed. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/239370241 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2025-07-15 | Meetings (one per entry) 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) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-07-15 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link 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" | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2025-06-17 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2025-06-17 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/203784264 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-06-17 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | A reboot presentation on the did:webs specification reviewed the existing KERI-specific extensions: the provisional application/CESR media type registered at IANA (Internet Assigned Numbers Authority), with a note to wait until the CESR specification is final, and the ConditionalProof2022 verification method, which still needs registration as a DID (decentralized identifier) extension and an updated specification. Open issues listed were identifier delegation as a service, ACDC-based signing, service endpoints, DID document versioning against the KERI event stream, alignment with the ToIP (Trust over IP) glossary, updated examples and compliance with current KERI versions, together with the next steps for finalizing the specification and a request for commit rights on the specification repository. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/203784264 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2024-07-05 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-07-05 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22999891 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-07-05 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Discussion considered how did:webs could be used with web sites that have the Signify browser extension enabled to establish trust in both directions, noted as a promising use case, alongside open pull requests and issues. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22999891 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2024-05-10 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-05-10 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22999456 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-05-10 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports restated IIW (Internet Identity Workshop) Spring 2024 (April 16 to 18), the public review period past 120 days and extended until the 1.0 requirements are met, and the Elixir CESR parser work. Discussion repeated the diagrams directory and the remaining pre-review items: the whois pull request, the normative and informative split, service endpoint updates and the KERIpy release candidate. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22999456 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2024-04-26 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-04-26 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998413 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-04-26 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports restated IIW (Internet Identity Workshop) Spring 2024 (April 16 to 18), the public review period past 120 days and extended until the 1.0 requirements are met, and the Elixir CESR parser work. Discussion repeated the diagrams directory and the remaining pre-review items: the whois pull request, the normative and informative split, service endpoint updates and the KERIpy release candidate. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998413 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2024-04-12 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-04-12 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998582 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-04-12 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The public review period was reported past 120 days and still extended until the 1.0 requirements are met. Reports noted the Elixir CESR parser work and a hackathon that closed issues related to the specification's examples. Discussion repeated the diagrams directory and the remaining pre-review items: the whois pull request, the normative and informative split, service endpoint updates and the KERIpy release candidate. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998582 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2024-04-05 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-04-05 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995116 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-04-05 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The public review period was reported past 120 days and still extended until the 1.0 requirements are met. Reports noted the Elixir CESR parser work and a hackathon held that week to close the issues related to the specification's examples. Discussion repeated the diagrams directory and the remaining pre-review items: the whois pull request, the normative and informative split, service endpoint updates and the KERIpy release candidate. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995116 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2024-03-29 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-03-29 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997846 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-03-29 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The public review period was reported past 120 days and still extended until the 1.0 requirements are met. Reports noted the Elixir CESR parser work and a hackathon planned for the following week to close the issues related to the specification's examples. Discussion repeated the diagrams directory and the remaining pre-review items: the whois pull request, the normative and informative split, service endpoint updates and the KERIpy release candidate. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997846 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2024-03-15 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-03-15 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998639 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-03-15 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The public review period was reported past 90 days and still extended until the 1.0 requirements are met, and the next meeting (2024-03-22) was cancelled for travel. Reports noted the Elixir CESR parser work and the Python reference implementation's upgrade to KERI 1.1.4. Discussion pointed members to the decentralized diagrams and images directory for comment and repeated the implementers draft and remaining pre-review items. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998639 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2024-03-08 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-03-08 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995849 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-03-08 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports noted the Python reference implementation upgraded to KERI 1.1.4, failing unit tests and a walk-through of the getting-started guide, and continued work on an Elixir CESR parser. Discussion presented the fully automated approach to a decentralized diagrams and images directory: definitions of a diagram and a reference to one on the WebOfTrust and trustoverip repositories, references as a reputation signal, captured surrounding text as context, and a request for input on which repositories and image paths to include. The implementers draft and remaining pre-review items were repeated. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995849 | https://zoom.us/rec/share/3pRHl8rtVu7Up7PNCsUhz-rnCy8G31gMQibTJ9ZoyNVdXVtghu1o4BNVR9v-yyh9.j1NuiBZrh7_LfIgh | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2024-03-01 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-03-01 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997137 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-03-01 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports covered an Elixir CESR parser whose author has been filing pull requests and issues on the CESR specification, the wrap-up of the diagram list with simple rules (diagrams live in a /diagrams folder of their own repository and are referenced, not copied), and Switchchord going live with activity across several industries. Discussion repeated the implementers draft and interoperability goals and the remaining items before final public review: the whois pull request, the normative and informative split, service endpoint updates and the KERIpy release candidate. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997137 | https://zoom.us/rec/share/x2nCcuJaOPIv6MH415-n7YTrjOtPceOQUjkCK0ZaHPnGnZW0p8MCIOuMySnGOIc.YoBL-4WaIGH-BSFW | A minimal-effort version of the diagram list was adopted, with simple rules: the repository is on trustoverip, the diagram is in /diagrams, diagrams are referenced in a decentralized way, and copies are avoided | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||
| didwebs-tf-2024-02-23 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-02-23 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995987 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-02-23 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The public review period was reported past 60 days, and a report noted pull requests and issues filed on the CESR specification while implementing a CESR parser. Discussion covered a planned article on the reference implementation aimed at organizations that want the discoverability of did:web with stronger security, citing the LEI (Legal Entity Identifier) and vLEI (verifiable LEI) and the separation of identifier authorization from domain control, alongside the diagram index in KERISSE (the KERI Suite search engine) and the implementers draft. An action item was to add the CESR IANA (Internet Assigned Numbers Authority) provisional registration link to the IANA considerations. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995987 | https://zoom.us/rec/share/cKkCnsY7JGyzl-hHuDmqtwHbWbiNsqQ7oMJblfWHSXjXXsa5iHzXSPV1kztL_dc.b4Dnt2rkZ-US4z0g | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2024-02-16 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-02-16 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995119 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-02-16 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Discussion covered diagramming across ToIP (Trust over IP): a community index of diagrams as a metadata table, starting with KERISSE (the KERI Suite search engine), with diagrams kept close to their source repositories, an automated broken-link checker, and a decentralized model for judging which are current. The implementers draft and interoperability between implementations before final public review were revisited. Action items included updating the specification version with a call for additional implementations, defining a minimal interoperability profile with optional features such as whois in further profiles, and building a KERISSE-maintained list of diagrams and images. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995119 | https://zoom.us/rec/share/Wqu8x6j93SlM89vCCZzlCM6PVep6KzB5O-kaNYT_JsWCDwRUoeRdEEZtS640cSsi.ry0w28fM4Mhjxz7V | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2024-02-09 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-02-09 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22989306 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-02-09 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The action-item review reported the provisional IANA (Internet Assigned Numbers Authority) media type registration for CESR as complete, and a co-chair was announced as having stepped down. Discussion proposed an implementers draft so that multiple implementations can verify the steps and show interoperability before final public review, and noted the value of explaining to outside audiences that did:webs separates signing control from web administration control. Remaining items were the whois pull request, the normative and informative split, service endpoint updates and the KERIpy release candidate. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22989306 | https://zoom.us/rec/share/u3eWA837Yh0y5u3PIMlSlUVKu6CqJI3_BhMDqqBliRM0Ztz0TIuWptxNwc3FTnFX.pwq-TajnDDbzTyVW | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2024-02-02 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-02-02 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22990888 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-02-02 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Discussion of the remaining work before final public review added the whois review and clarified that the implementation guide and reference implementation are separate from the specification, with the graph diagram a candidate for the implementation guide. Other items were the normative versus informative breakdown (issue 120), service endpoint section updates and the KERIpy release candidate. Action items included cleaning up informative links and the old bracketing technique and reviewing a first pass at the normative and informative breakdown. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22990888 | https://zoom.us/rec/share/lCRFrO-640OzJGMw8U7rOvki42UXfji1UTGH0vw7JKRrpo-bt_Mxe0q-3a2OdZIJ.b4F5tu1pCJr5lit- | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2024-01-26 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-01-26 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995004 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-01-26 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | With the public review period past 30 days and extended until the 1.0 requirements are met, discussion covered how the specification should guide readers through only the KERI features did:webs needs, including updates to the diagram in pull request 124. Remaining items before final review included the normative versus informative breakdown (issue 120), service endpoint section updates, the KERIpy release candidate, and how contributors could help; a participant offered to work through the reference implementation's getting-started guide on an Apple M3 machine. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995004 | https://zoom.us/rec/share/r0Wsw2wtN-EeCO8lr0Evp8A2fSn4Lw9a4zYnc91vVbWe6sGpPLKTFDg1nzceRP58.ELOofmT8_iIhg5MY | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2024-01-19 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-01-19 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998106 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-01-19 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements noted the Technology Stack Working Group's new mailing list as part of accepting the new Open Web Foundation licensing, and that the public review period had passed 30 days. The ToIP (Trust over IP) specification template was reported, with its latest changes to be adopted into the did:webs repository. Discussion stressed that the specification must make clear what is optional so readers can see where to stop for their use case, and continued the normative versus informative breakdown of the specification. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998106 | https://zoom.us/rec/share/78XvGsQ2f5RX_VLHgD9Kfgd4Q6a2VWsD_bI2erWnJzYJj-LM4_somcesJAPrSMsw.K3krmc4e7JqVmrlW | Public review period extended until the 1.0 specification requirements are complete | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||
| didwebs-tf-2024-01-12 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-01-12 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998030 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-01-12 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Discussion focused on separating normative from informative material before release (issue 120): working back from the normative statements, keeping informative text to a minimum and moving the rest to an appendix, implementation guide or separate paper, following the ToIP (Trust over IP) specification template. A section-by-section review covered core characteristics, the method name, the method-specific identifier ABNF (Augmented Backus-Naur Form), whether statements about the KERI AID (autonomic identifier) should be normative and reference the KERI specifications, and the point that W3C does not allow non-normative references, so a SCID (self-certifying identifier) might be specified at bare minimum. The state of the Hyperledger Labs reference implementation was also on the agenda. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998030 | https://zoom.us/rec/share/s_IiwW9wOtlXHFfu3AlPy0O28zlvrDT-naKVPNX3DnRlvBGf8WxWr_SOSPt96zY.ZfYeUSPyHJDudA0R?startTime=1705071805000 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2024-01-05 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-01-05 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22994892 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-01-05 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements covered the Technology Stack Working Group's new mailing list under its new charter, IIW (Internet Identity Workshop) Spring 2024 on April 16 to 18, and a public review period expected to close at the January 19 meeting, following the ToIP (Trust over IP) blog post of December 15 announcing the review. Discussion repeated the public review preparation items: documented review changes, a review issue template, open to-do sections and the 1.0 milestone. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22994892 | https://drive.google.com/file/d/1APixTsCYPrse7rdP4zX8GKhEYoE1VhGC/view?usp=sharing | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2023-12-15 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2023-12-15 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997177 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-12-15 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The blog post announcing the public review period was reported as updated, and the task force would not meet again until January 5. Discussion covered what was needed to enter public review: documenting all review changes, a public review issue template modeled on the one used for the vLEI (verifiable Legal Entity Identifier) EGF (Ecosystem Governance Framework) review with a field for the quoted text, resolving open to-do sections, the 1.0 milestone, and an equivalentId and alsoKnownAs pull request to be revised so as not to change the subset and superset relationship. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997177 | https://zoom.us/rec/share/5BxR88cPQELxp3QgrKdkLWpQ_XGBEViS6zU7T6S7WxErqy4dGGpMK8hSFRu07Zb6.nYdSj3F9tMfdYRZm | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2023-12-08 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2023-12-08 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996410 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-12-08 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The December 15 target for a 1.0 specification, a Rubric podcast on December 11 and the blog post announcing the public review period were restated. Discussion caught up on the status of final changes: specification versions and dependencies, terminology and KERI fundamentals, the Designated Aliases public schema, the Hyperledger Labs reference implementation, and open pull requests and issues. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996410 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2023-12-01 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2023-12-01 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22993607 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-12-01 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The December 15 target for a 1.0 specification and the planned public review period, to be announced by blog post, were restated. Discussion covered terminology and KERI fundamentals, the Designated Aliases public schema, reference implementation work in the Hyperledger Labs did-webs-resolver, and open pull requests and issues. Action items included reviewing the IIW (Internet Identity Workshop) tutorial pull request and migrating that tutorial to Hyperledger Labs as a "did:webs Getting Started" guide. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22993607 | https://zoom.us/rec/share/_fXJAg_svEwHDZpCWwacdcLP_TFNjkLkfGtlKmLYIN-hLZyIsBSAC6agijaIMw4.YHOWnpzxloLKVcca | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2023-11-17 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2023-11-17 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995690 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-11-17 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements kept the December 15 target for a 1.0 specification, noted a Rubric podcast on December 11 and a BC Government did:webs VDR (verifiable data registry) registrar and resolver for Aries agents. The blog post was to be changed to announce a public review period starting with the December 15 completion, ahead of the December 13 all-members call. Discussion covered the Designated Aliases public schema and its example script. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995690 | https://zoom.us/rec/share/L7CZ3st7lzxwZAhK_JlNIxGxYRAfGpL0KEpfBpFKZMxIYFmGayqvgTVtO4gZ_rrx.qgZe4uRQ3X_B7g27 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2023-11-10 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2023-11-10 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995707 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-11-10 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements set a target of a 1.0 specification by December 15 and noted a did:webs VDR (verifiable data registry) registrar and resolver for Aries agents. Switchchord demonstrated a music-industry copyright management system that issues credentials to songwriters and publishers, currently on did:web with a planned move toward something like did:webs. Discussion proposed an authorized identifier list for secure rich discovery, under which equivalentId, redirection and authorized domains are satisfied by authorized did:webs identifiers and alsoKnownAs covers other DIDs (decentralized identifiers), and asked whether resolution must fail when that metadata is absent. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995707 | https://zoom.us/rec/share/CEasFYFDhwZlTx7j03YGIjsiy1eUfnkjcFMaFvopBJN8Limitn9qccupTZf4pHUA.ll7dSHAa1NtVO6tT | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2023-11-03 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2023-11-03 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996920 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-11-03 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements reported that the 60-day OWF (Open Web Foundation) IPR (intellectual property rights) period was complete and that did:webs is now listed in the W3C DID (decentralized identifier) specification registries. Discussion proposed completing a 1.0 specification by December 15 and worked through domain-related history and validation: the semantics of equivalentId versus alsoKnownAs, handling web redirection, authorized domains anchored to the KEL (key event log), whether domain control matters, and a matrix toward the simplest schema. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996920 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2023-10-27 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2023-10-27 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996196 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-10-27 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | A post-IIW (Internet Identity Workshop) report covered an X.509 VID (verifiable identifier) specification. Discussion covered how to show users that the DID (decentralized identifier) document was verified from the keri.cesr file, human readability (judged not yet a priority), did:plc handles, and the whois presentation: an optional did:webs feature published as a W3C Verifiable Presentation (v1.1 first), with JWT (JSON Web Token) and ACDC proof alternatives, media types to signal the presentation type, and a related DIF (Decentralized Identity Foundation) Linked Verifiable Presentations work item proposal. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996196 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2023-10-20 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2023-10-20 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996207 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-10-20 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Post-IIW (Internet Identity Workshop) review: the method-registration pull request awaited one more approval, the "did:webs for Muggles" slides and an IIW tutorial were shared, with a question about adding more KERI commands (rotation, earlier sequence numbers, multi-signature) to the tutorial. Discussion covered an X.509 VID (verifiable identifier) specification, how to signal to conventional DID (decentralized identifier) document users that the keri.cesr file is the basis for the document, human readability, and the whois presentation and the reputation of an AID (autonomic identifier). | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996207 | https://zoom.us/rec/share/2MMOrx2G-vmggGdM4vmjL58OW_6qkytEfEaaDxTnXagRUp7uNHQwilECvhTugWlX.VNdZEDfvekvnPKTR | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2023-10-06 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2023-10-06 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22991018 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-10-06 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Agenda only; no notes recorded: a report on the ToIP (Trust over IP) TSP (Trust Spanning Protocol) appraisability discussion, and the top priorities for preparing the specification for IIW (Internet Identity Workshop) through open pull requests and issues. The action-item review records the pull request to register the method in the W3C DID (decentralized identifier) specification registries as submitted and additional approvers added. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22991018 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2023-09-29 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2023-09-29 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996289 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-09-29 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | A report from the DIF (Decentralized Identity Foundation) identifiers discovery meeting covered did:plc, the centralized identifier for Bluesky users that keeps an event log with pre-rotation, and a did:web 2.0 proposal. Discussion set the top priorities for preparing the specification for IIW (Internet Identity Workshop): open pull requests and a "did:webs for Muggles" presentation. Action items recorded event documentation and an anchoring pull request as complete. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996289 | https://zoom.us/rec/share/S2HGYFQ5wa_5SNr1E-ywrefhyT5xvtSoFe9-Vqv6GdlrWIcL7rwh9Q59yplKkXH8.M-jbgvFVeFHkMpgI | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2023-09-22 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2023-09-22 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22993256 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-09-22 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The reference implementation moved to Hyperledger Labs (did-webs-resolver) and the original specification repository was donated to ToIP (Trust over IP). A report from a did:webplus meeting compared signed DID (decentralized identifier) documents, discovery versus control bound to the AID (autonomic identifier), backward hash links versus versionId, optional duplicity detection, and possible synergies between did:webplus and did:webs. Planning continued toward IIW (Internet Identity Workshop) October 2023 and a pending IANA CESR MIME type registration. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22993256 | New co-chairs voted in for the task force (names not preserved in the page text) | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2023-09-15 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2023-09-15 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22982303 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-09-15 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | First meeting as an official ToIP (Trust over IP) task force: the specification moved to the new trustoverip/tswg-did-method-webs-specification repository, with a new reference implementation repository to follow, and chairs and maintainers were to be appointed. Discussion revisited the resolver architecture and proposed treating verification data as a CESR stream, noting that the CESR MIME type is on the IANA (Internet Assigned Numbers Authority) roadmap and that a .cesr extension may fit better than .keri, which also aligns with the TSP (Trust Spanning Protocol). Plans for IIW (Internet Identity Workshop) October 2023 included a registered DID (decentralized identifier) method, a Universal Resolver implementation and a "did:webs for Muggles" session. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22982303 | https://drive.google.com/file/d/1YpX-GirifPdKaIuBZukO6ODB9WbTeDcM/view?usp=sharing | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-prov-2023-09-15 | Meetings (one per entry) meeting | did:webs Task Force provisional meeting, 2023-09-15 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995714 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-09-15 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements expected the task force to be officially approved under ToIP (Trust over IP) that Friday and set an IIW (Internet Identity Workshop) October 2023 goal of a registered DID (decentralized identifier) method with a Universal Resolver implementation, with a "did:webs for Muggles" session planned. Discussion revisited the architecture diagrams and proposed that the specification treat verification data as KERI resources delivered as a CESR stream, introducing the terms "KERI resource" (replacing the .kel and .oobi terms) and a CESR media type. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995714 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-prov-2023-09-08 | Meetings (one per entry) meeting | did:webs Task Force provisional meeting, 2023-09-08 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22987889 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-09-08 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements reported ToIP (Trust over IP) approval of the OWF (Open Web Foundation) IPR (intellectual property rights) license, the pending Technology Stack Working Group review and email vote on the proposed task force, acceptance of a Hyperledger Labs proposal for the resolver, and an IIW (Internet Identity Workshop) goal of a registered method with a Universal Resolver implementation. Discussion covered the simplified security-characteristics pull request based on KEL (key event log) backing, alternative resolver architectures (published DID document plus OOBI (out-of-band introduction) file versus watcher-based verification), and the cost of verifying and caching KELs. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22987889 | https://drive.google.com/file/d/1gSgG2jJHPhMJtcIlqAcMG1i8F4k2njcW/view?usp=sharing | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-prov-2023-09-01 | Meetings (one per entry) 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) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-09-01 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link 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 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-prov-2023-08-24 | Meetings (one per entry) meeting | did:webs Task Force provisional meeting, 2023-08-24 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22979862 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-08-24 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements covered the provisional task force's expected approval under ToIP (Trust over IP), a possible meeting-time change, and whether to amend the charter on where reference-implementation code should live (WebOfTrust, DIF (Decentralized Identity Foundation) Universal Resolver, or the Open Wallet Foundation), with IIW (Internet Identity Workshop) October 2023 proposed as a milestone for a coherent draft and a resolver implementation. Discussion reviewed recent specification issues and pull requests: alsoKnownAs versus equivalentId, whois, weighted-threshold multi-signature, TLS common name, and signed files. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22979862 | https://drive.google.com/file/d/1-rbXkkpTTbJhjoMPHxlDLLAZhYYlpLt4/view?usp=sharing | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-prov-2023-08-17 | Meetings (one per entry) 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) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-08-17 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link 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 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE resources (id TEXT PRIMARY KEY, type TEXT REFERENCES types(id), name TEXT, url TEXT, maintainer TEXT,
status TEXT REFERENCES statuses(id), last_checked TEXT, date TEXT, year INTEGER, level TEXT REFERENCES levels(id),
evidence TEXT REFERENCES evidence(id), access TEXT REFERENCES access(id), abstract TEXT, authors TEXT, series TEXT,
chair TEXT, minutes TEXT, recording TEXT, media TEXT, decisions TEXT, version TEXT, language TEXT, license TEXT,
release TEXT, pushed TEXT, depends TEXT, since TEXT, via TEXT REFERENCES resources(id),
summary TEXT REFERENCES notes(path), note TEXT, has_abstract INTEGER, has_summary INTEGER,
kind TEXT REFERENCES kinds(id), sector TEXT REFERENCES sectors(id), country TEXT, products TEXT);