Search results

DID Core has Informative terms that DID Resolution considers Normative

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

Status: Open.

#288 In w3c/did-resolution;

· ottomorac opened on Feb 3, 2026

DID Document Metadata properties that are timestamps should refer to Datetime definition

good first issueGood for newcomersGood for newcomers

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

Status: Open.

#287 In w3c/did-resolution;

· wip-abramson opened on Feb 3, 2026

Review references to DID Extensions throughout

good first issueGood for newcomersGood for newcomers

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

Status: Open.

#286 In w3c/did-resolution;

· wip-abramson opened on Feb 3, 2026

Clarify language about use of DID parameters

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

tag-trackerGroup bringing to attention of the TAG, or tracked by the TAG but not needing response.Group bringing to attention of the TAG, or tracked by the TAG but not needing response.

Status: Open.

#284 In w3c/did-resolution;

· wip-abramson opened on Jan 23, 2026

Should DID Document Properties Extensions mechanism use W3C or IANA registry mechanism

pending-closeIssue will be closed shortly if no objectionsIssue will be closed shortly if no objections

tag-trackerGroup bringing to attention of the TAG, or tracked by the TAG but not needing response.Group bringing to attention of the TAG, or tracked by the TAG but not needing response.

Status: Open.

#283 In w3c/did-resolution;

· wip-abramson opened on Jan 23, 2026

Should the spec address the non-handling of DID URL query parameters?

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

Status: Open.

#279 In w3c/did-resolution;

· swcurran opened on Jan 22, 2026

We probably want to remove proxying resolvers

during-cr

Status: Open.

#277 In w3c/did-resolution;

· jandrieu 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

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

tag-trackerGroup bringing to attention of the TAG, or tracked by the TAG but not needing response.Group bringing to attention of the TAG, or tracked by the TAG but not needing response.

Status: Open.

#274 In w3c/did-resolution;

· wip-abramson opened on Jan 22, 2026

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