Add NO_CACHE_DISALLOWED error

[ottomorac]

This pr addresses #174 , creates the new NO_CACHE_DISALLOWED error and references the error back in the Caching section of the spec.

---

Preview | Diff

[w3cbot]

This was discussed during the #did meeting on 04 September 2025.

View the transcript

DID Resolution PR Processing

<ottomorac> Add NO_CACHE_DISALLOWED error #183

<ottomorac> Add direct links to did extensions #184

ottomorac: we have 2 new PRs from my side
… these are both fairly simple
… one is just a reference fix

<TallTed> is stuck in previous meeting running over...

ottomorac: both should be easy

---

[w3cbot]

This was discussed during the #did meeting on 18 September 2025.

View the transcript

w3c/did-resolution#183

Wip: anyone having concerns about this PR?

---

[wip-abramson]

Wondering if this NO_CACHE_DISALLOWED error could also be bundled into a more generic FEATURE_NOT_SUPPORTED error. See #190

[ottomorac]

During WG meeting on 25-Sept we discussed to keep a more generic error message, whilst still providing an explanation about the specific missing feature (the cache in this case). https://www.w3.org/2025/09/25-did-minutes.html#c127

[wip-abramson]

@ottomorac are you okay to rework this PR to introduce and use the more generic FEATURE_NOT_SUPPORTED error? Or we could close and open a different PR

[ottomorac]

@wip-abramson I will re-work it. Thanks.