Add DID Resolution error conditions to vocabulary (Fixes #922)

[valerodev]

Add DID Resolution error conditions to vocabulary. Fixes #922

[iherman]

You were quicker than me by 15 minutes :-) I had a yml file on my machine...

1. My changes rely on the existence of an (internal) class:

  - id: ResolutionError
    label: DID Resolution error
    defined_by: https://www.w3.org/TR/did-resolution/#errors
    context: none

added to the class section in the yml file. (Alas!, github does not let me add this through the review process.) This addition gives a proper categorization to the terms in the vocabulary. (I follow the same structure that we did in the DI vocabulary.)

2. The defined_by fields have been all changed:

• The URL should go to the final publication (on /TR) and not to the editor's draft
• As far as I could see, each entry on the spec has its own ID (which is great) that defines the term; that is the URL that should be used, imho.

[valerodev]

@iherman Done. I'm new to this so thanks for the guidance.

[iherman]

@iherman Done. I'm new to this so thanks for the guidance.

Happy to help!

[iherman]

Actually... you may have missed a spot:-)

In the https://github.com/w3c/did-resolution/blob/main/index.html#L2259 section I see 9 error conditions, and this PR has only 7. It may well be that your list the latest agreement on the WG for the error conditions and the file on the repo is out of date, but I thought it is better to warn you...

[valerodev]

You're absolutely right. Done.

[w3cbot]

This was discussed during the #did meeting on 12 March 2026.

View the transcript

DID Path PR \[1\] (10 min)

<ottomorac> w3c/did#923

joe: was trying to think through this

otto: manu have you checked this out yet? looks approved already

manu: i haven't run the linter/checker but if that passes looks right semantically
… yeah looks good

---