Skip to content

Conversation

@wip-abramson
Copy link
Contributor

@wip-abramson wip-abramson commented Jan 6, 2026

This attempts to address #247.

I have added some steps to the DID Resolution Algorithm to throw the FEATURE_NOT_SUPPORTED and INVALID_OPTIONS errors. Additionally I added a paragraph at the end of the algorithm about throwing INTERNAL_ERROR on unexpected errors.

There may be a better way to handle this, wanted to get something in a PR folks could see and argue over.


Preview | Diff

@wip-abramson wip-abramson force-pushed the iss247-unthrown-errors branch from 8616a0a to 3119434 Compare January 6, 2026 15:23
@w3cbot
Copy link

w3cbot commented Jan 8, 2026

This was discussed during the #did meeting on 08 January 2026.

View the transcript

w3c/did-resolution#265

Wip: I wanted to go back to the PRs, actually

Wip: this one needs a review
… it's about errors
… I've removed a bunch
… but how do we handle where errors defined in the spec weren't used anywhere
… I've added sections to use them
… but I do need reviews
… and we can discuss it if/as needed on a future call
… it is a relatively substantial change

ottomorac: yeah, reviews are really the main thing
… if there are no other concerns, we'll see you next week!
… thanks all


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants