Search results

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

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

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

Status: Open.

#236 In w3c/did-resolution;

· wip-abramson opened on Oct 27, 2025

Confusing proof property in metadata returned by DID Resolver

Status: Open.

#235 In w3c/did-resolution;

· wip-abramson opened on Oct 24, 2025

Conflicting normative statements about didDocument representation

Status: Open.

#234 In w3c/did-resolution;

· wip-abramson opened on Oct 24, 2025

Avoid ambiguous use of 'match' in specification

Status: Open.

#233 In w3c/did-resolution;

· wip-abramson opened on Oct 24, 2025

Can we avoid term definition duplication across DID specs?

Status: Open.

#232 In w3c/did-resolution;

· wip-abramson opened on Oct 24, 2025

didDocument definition should refer to DID Data Model

Status: Open.

#231 In w3c/did-resolution;

· wip-abramson opened on Oct 24, 2025

Unclear definition of "Read" operation for DID methods

Status: Open.

#230 In w3c/did-resolution;

· wip-abramson opened on Oct 24, 2025

Address reference to internet draft [HASHLINK]

Status: Open.

#229 In w3c/did-resolution;

· wip-abramson opened on Oct 24, 2025

Fix bug in implementer overview description

Status: Open.

#228 In w3c/did-resolution;

· wip-abramson opened on Oct 24, 2025

Address confusing note about the difference between "resolving" a DID and "dereferencing" a DID URL

Status: Open.

#227 In w3c/did-resolution;

· wip-abramson opened on Oct 24, 2025