Search results

HTTP Bindings could be more tightly specified

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

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

Status: Open.

#294 In w3c/did-resolution;

· bvandersloot-mozilla opened on Feb 20, 2026

Tracking of resolutions and dereferences by downstream entities from the resolver

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

Status: Open.

#293 In w3c/did-resolution;

· bvandersloot-mozilla opened on Feb 20, 2026

Should support for DID Parameters be OPTIONAL?

during-cr

Status: Open.

#289 In w3c/did-resolution;

· wip-abramson opened on Feb 4, 2026

DID Core has Informative terms that DID Resolution considers Normative

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

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

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

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

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

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 the spec address the non-handling of DID URL query parameters?

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

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

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

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

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

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