Issues

• post-344: Problematic definitions of “client” and “DID-enabled application”

  discuss
  w3c/did-resolution#387 · Filter by author peacekeeper opened on Oct 24, 2026
  1

• post-344: Open questions about did:ex:123?service=DIDCommMessaging example

  w3c/did-resolution#385 · Filter by author peacekeeper opened on Oct 24, 2026
  2

• post-344: Open questions about did:ex:123#key-1 example

  w3c/did-resolution#384 · Filter by author peacekeeper opened on Oct 24, 2026
  1

• post-344: Open questions about relativeRef, PathHandler, PathService

  w3c/did-resolution#383 · Filter by author peacekeeper opened on Oct 24, 2026
  1

• post-344: Unclear how “serviceType” could be supported

  w3c/did-resolution#382 · Filter by author peacekeeper opened on Oct 24, 2026
  1

• post-344: Dereferencing algorithm should not depend on configuration of its implementation

  w3c/did-resolution#381 · Filter by author peacekeeper opened on Oct 24, 2026

• post-344: Dereferencing algorithm should not depend on context in which it is executed

  w3c/did-resolution#380 · Filter by author peacekeeper opened on Oct 24, 2026

• post-344: Unclear why dereferencing metadata was removed

  w3c/did-resolution#379 · Filter by author peacekeeper opened on Oct 24, 2026

• post-344: Unclear why dereferencing options were removed

  w3c/did-resolution#378 · Filter by author peacekeeper opened on Oct 24, 2026

• post-344: Dereferencing algorithm defines no results

  w3c/did-resolution#377 · Filter by author peacekeeper opened on Oct 24, 2026

• MUST implement the exact function signature for DID Resolution?

  pr-exists
  w3c/did-resolution#363 · Filter by author peacekeeper opened on Sep 23, 2026
  2

• How to express inputs and results of the algorithms?

  w3c/did-resolution#361 · Filter by author peacekeeper opened on Sep 15, 2026
  6

• HTTP(S) Binding's GET and TLS requirements apply to all conforming DID resolvers, not only network-based ones

  ready for pr
  w3c/did-resolution#360 · Filter by author fabianekc opened on Sep 1, 2026
  4

• Provide a normative reference for VC Recognized Entities discovery (WhoisService / PathService / LinkedVP)

  future
  w3c/did-resolution#357 · Filter by author ottomorac opened on Aug 20, 2026

• Treat deactivated DID resolution state as an error code

  w3c/did-resolution#353 · Filter by author filip26 opened on Jul 30, 2026
  7

• Consider revising / removing DID Resolution Architecture

  during-cr
  w3c/did-resolution#347 · Filter by author jandrieu opened on Jul 9, 2026
  6

• Charter Success Criteria Implications? DID Resolvers must support at least 2 DID methods

  discuss
  w3c/did-resolution#343 · Filter by author wip-abramson opened on Jun 24, 2026

• Experiments with service, serviceType, relativeRef vs. PathService

  during-cr
  w3c/did-resolution#332 · Filter by author peacekeeper opened on May 14, 2026
  14

• Fix language suggesting that optional parameters "function the same way for all DIDs"

  discussduring-cr
  w3c/did-resolution#323 · Filter by author jandrieu opened on Apr 12, 2026
  6

• Remove Guidance suggestion that resolvers validate against the test suite

  during-crready for pr
  w3c/did-resolution#322 · Filter by author jandrieu opened on Apr 12, 2026
  2

  

• Add warnings to the DID Resolution specification

  future
  w3c/did-resolution#308 · Filter by author wip-abramson opened on Mar 20, 2026
  1

• Reconsider expandRelativeURLs as part of dereferencing instead of resolution

  during-crready for pr
  w3c/did-resolution#302 · Filter by author jandrieu opened on Mar 7, 2026
  5

• We probably want to remove proxying resolvers

  during-cr
  w3c/did-resolution#277 · Filter by author jandrieu opened on Jan 22, 2026
  9

• Change references to RFC3986 to the WHATWG URL Spec

  future
  w3c/did-resolution#275 · Filter by author swcurran opened on Jan 22, 2026
  12

  

• Clarify the distinction between DID Resolution and DID URL Dereferencing

  during-crready for pr
  w3c/did-resolution#246 · Filter by author wip-abramson opened on Nov 11, 2025