Search results

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

Status: Open.

#244 In w3c/did-resolution;

· swcurran opened on Nov 6, 2025

Reference DID Core Security and Privacy considerations sections

Status: Open.

#241 In w3c/did-resolution;

· wip-abramson opened on Oct 30, 2025

Confusing error language in algorithms leading to misimplementation

Status: Open.

#240 In w3c/did-resolution;

· wip-abramson opened on Oct 29, 2025

Duplicate normative requirements around implementing DID resolution algorithm

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?

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

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

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

Confusing proof property in metadata returned by DID Resolver

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.

#235 In w3c/did-resolution;

· wip-abramson opened on Oct 24, 2025

Conflicting normative statements about didDocument representation

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.

#234 In w3c/did-resolution;

· wip-abramson opened on Oct 24, 2025

Avoid ambiguous use of 'match' in specification

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.

#233 In w3c/did-resolution;

· wip-abramson opened on Oct 24, 2025

Can we avoid term definition duplication across DID specs?

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

didDocument definition should refer to DID Data Model

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.

#231 In w3c/did-resolution;

· wip-abramson opened on Oct 24, 2025