Search results

We probably want to remove proxying resolvers

Status: Open.

#277 In w3c/did-resolution;

· jandrieu opened on Jan 22, 2026

Clarify data types for values of maps and lists

Status: Open.

#276 In w3c/did-resolution;

· wip-abramson opened on Jan 22, 2026

Change references to RFC3986 to the WHATWG URL Spec

Status: Open.

#275 In w3c/did-resolution;

· swcurran opened on Jan 22, 2026

Unclear statement about verifiability of results of DID Resolution

tag-needs-resolutionIssue the Technical Architecture Group has raised and looks for a response on.Issue the Technical Architecture Group has raised and looks for a response on.

Status: Open.

#274 In w3c/did-resolution;

· wip-abramson opened on Jan 22, 2026

DID URL Derefencing and Fragments: The role of a DID Resolver

discussNeeds further discussion before a pull request can be createdNeeds further discussion before a pull request can be created

Status: Open.

#259 In w3c/did-resolution;

· swcurran opened on Dec 17, 2025

Identify unthrown errors in the spec.

pr-existsThere is an open PR to address this issue.There is an open PR to address this issue.

Status: Open.

#247 In w3c/did-resolution;

· wip-abramson opened on Nov 11, 2025

Clarify the distinction between DID Resolution and DID URL Dereferencing

ready for prIssue is ready for a PRIssue is ready for a PR

Status: Open.

#246 In w3c/did-resolution;

· wip-abramson opened on Nov 11, 2025

Remove "client" from identifying an error in the path handling

ready for prIssue is ready for a PRIssue is ready for a PR

Status: Open.

#244 In w3c/did-resolution;

· swcurran opened on Nov 6, 2025

Confusing error language in algorithms leading to misimplementation

ready for prIssue is ready for a PRIssue is ready for a PR

Status: Open.

#240 In w3c/did-resolution;

· wip-abramson opened on Oct 29, 2025

Do we need to include iterating over extensions in the DID resolution algorithm?

discussNeeds further discussion before a pull request can be createdNeeds further discussion before a pull request can be created

ready for prIssue is ready for a PRIssue is ready for a PR

tag-needs-resolutionIssue the Technical Architecture Group has raised and looks for a response on.Issue the Technical Architecture Group has raised and looks for a response on.

Status: Open.

#238 In w3c/did-resolution;

· wip-abramson opened on Oct 27, 2025

Can we avoid term definition duplication across DID specs?

good first issueGood for newcomersGood for newcomers

ready for prIssue is ready for a PRIssue is ready for a PR

tag-needs-resolutionIssue the Technical Architecture Group has raised and looks for a response on.Issue the Technical Architecture Group has raised and looks for a response on.

Status: Open.

#232 In w3c/did-resolution;

· wip-abramson opened on Oct 24, 2025

Unclear definition of "Read" operation for DID methods

discussNeeds further discussion before a pull request can be createdNeeds further discussion before a pull request can be created

pr-existsThere is an open PR to address this issue.There is an open PR to address this issue.

tag-needs-resolutionIssue the Technical Architecture Group has raised and looks for a response on.Issue the Technical Architecture Group has raised and looks for a response on.

Status: Open.

#230 In w3c/did-resolution;

· wip-abramson opened on Oct 24, 2025