Search results

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

Status: Open.

#259 In w3c/did-resolution;

· swcurran opened on Dec 17, 2025

Untestable normative requirement for proof

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

Status: Open.

#252 In w3c/did-resolution;

· wip-abramson opened on Dec 2, 2025

Remove untestable normative requirement on the DID Resolution Extensions

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

Status: Open.

#251 In w3c/did-resolution;

· wip-abramson opened on Dec 2, 2025

Identify unthrown errors in the spec.

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

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

Reference DID Core Security and Privacy considerations sections

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

Status: Open.

#241 In w3c/did-resolution;

· wip-abramson opened on Oct 30, 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

Duplicate normative requirements around implementing DID resolution algorithm

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

test suite

Status: Open.

#239 In w3c/did-resolution;

· wip-abramson opened on Oct 29, 2025

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

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

Conflicting normative statements about conformant representation of DID document and the accept input

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.

#237 In w3c/did-resolution;

· wip-abramson opened on Oct 27, 2025

Remove unnecessary text "against the input verifiable data registry" from DID Resolution Algorithm

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.

#236 In w3c/did-resolution;

· wip-abramson opened on Oct 27, 2025