Consider adding "Design Goals and Rationale" section

[ottomorac]

During discussion of this PR #207 the WG agreed that adding a "Design Goals and Rationale" would be useful. We might potentially re-purpose the "Implementer Overview" section for that purpose and also bring in some other editorial changes.

This is a low priority issue for the moment.

For reference, here other specs that have a similar "Design Goals and Rationale" section:

• DID core: https://www.w3.org/TR/did/upcoming/#design-goals
• VCALM: https://w3c-ccg.github.io/vcalm/#design-goals-and-rationale

[msporny]

The group discussed this at W3C TPAC and decided that we didn't need the section -- it's clear what the DID Resolution specification is trying to do.

[w3cbot]

This was discussed during the #did meeting on 11 November 2025.

View the transcript

w3c/did-resolution#208

wip: Should we add a design goals section?

manu: Uh... no.
… we shouldn't do this. I don't think TAG requires it.
… The reason we sometimes put it in is because it's not clear what we are trying to do.

JoeAndrieu: Yes, +1, for VCs and DIDs, people wanted to know, for this spec, probably not.

manu: I don't think we need to add that unless someone is asking

---