/
2025-06-17 did:webs Meeting Notes

2025-06-17 did:webs Meeting Notes

Zoom Meeting Link / Recording

LFX Meetings

Attendees

@Sam Smith @Philip Feairheller @Jonathan Rayback @Kent Bull @Kevin Griffin arilieb

Agenda Items and Notes (including all relevant links)

Time

Agenda Item

Lead

Notes

5 min

  • Start recording

  • Welcome & antitrust notice

  • Introduction of new members

  • Agenda review

Chairs - TBD

  • Antitrust Policy Notice: Attendees are reminded to adhere to the meeting agenda and not participate in activities prohibited under antitrust and competition laws. Only members of ToIP who have signed the necessary agreements are permitted to participate in this activity beyond an observer role.

  • New Members:

5 mins

Review of action items from the previous meeting

Chairs

 

5 mins

Announcements

TF Leads

News or events of interest to members:

  • -

5 mins

Reports

Open

 

25 mins

Discussion

Open

 

5 mins

Any other business

Open

 

5 mins

  • Review decisions/action items

  • Planning for the next meeting 

Chairs

 

Reboot presentation by @Jonathan Rayback

 

DID:Webs

17 June 2025

Existing KERI-specific Extensions

Media Type

A provisional standard media type, application/CESR, has been registered at IANA. Is anything more needed to be done here?

[We want to wait until the CESR spec is finalized]

Verification Method

An extension to the DID Core Specification, ConditionalProof2022, has been developed and is defined here. It appears that it still needs to be registered in the DID Document Property Extensions registry as a known Verification Method type. Also, its specification is outdated and would benefit from being updated. For example, did:webs is not listed under ‘Known Implementations’.

To Do

Application/CESR

  • Anything?

Multi-sig

  • ConditionalProof2022 needs to be registered as a DID extension.

  • ConditionalProof2022 specification needs to be finalized.

    • What is status? Is it still being used elsewhere?

    • Could it be pulled into ToIP? To KSWG?

    • Could it move into the DID:Webs specification?

Identifier Delegation

  • Proposal to implement this concept as a service needs to be finalized.

  • If we extend the core data model, we’ll need to register a new Service Type as a DID extension (see here).

Other Issues

  • Using ACDCs to sign. Still a thing?

    • Would require another Verification Method type to be developed, specified somewhere, and registered as a DID extension.

  • DID:Webs Service Endpoints

    • Partially addressed by the delegation question (see below).

    • More analysis is needed. Likely additional work in the spec will be needed.

  • DID Document Versioning

    • More discussion is required around the relationship between the DID Document and the KERI Event Stream as it pertains to verification. If newer versions of the DID:Webs spec can make older DID Documents unverifiable, we need to devise a sufficient versioning strategy.

  • Terminology Alignment with ToIP Glossary

    • More analysis is needed. It’s possible this has all been completed.

  • Update example blocks

    • Various updates

      • Consistency

      • Compliance with latest KERI versions

      • Comprehensiveness

Next Steps for Finalizing DID:Webs Specification

  • Next steps in the approval process?

  • What pre-work is required?

Other

  • Can I have permission to commit changes in the DID:Webs Specification GitHub repo (close issues, merge PRs, etc.)?