Search results

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

Define generic datetime format for DID resolution and use throughout spec

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

Status: Open (in progress).

w3c/did-resolutionnumber 248

#248 In w3c/did-resolution;

· wip-abramson opened on Dec 1, 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

Define network based conformance classes for resolver and dereferencer

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

Status: Open (in progress).

w3c/did-resolutionnumber 243

#243 In w3c/did-resolution;

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

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

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

Rework the abstract to be more grounded

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.

#225 In w3c/did-resolution;

· wip-abramson opened on Oct 24, 2025

Reference either DID v1.0 or v1.1 throughout the specification

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

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.

#224 In w3c/did-resolution;

· wip-abramson opened on Oct 24, 2025

Prefer UTF-8 for DID Parameters

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

Status: Open (in progress).

w3c/did-resolutionnumber 217

#217 In w3c/did-resolution;

· ottomorac opened on Oct 19, 2025