TAG Review: Add examples of how to use DID resolution to solve the end-users' problems

[ottomorac]

• Adds an explanation of "How DID resolution is used to address the needs from Software Developers" in order to address Tag Review: Add examples of how to use DID resolution to solve the end-users' problems #187

---

Preview | Diff

[wip-abramson]

Hmm, reviewing this PR alongside the others for the TAG review #199 and #194, I am not sure your proposal to group them all under a Design Goals and Rationale makes sense.
To start with, I don't think the text in any of these PRs actually defines the design goals. E.g. look at the Design Goals section from DID core - https://www.w3.org/TR/did/upcoming/#design-goals.

Although, if this is the case it does raise the question of where this text you have proposed here goes. It reads more like an overview, which I think is what TAG are looking for really. An overview of how this Spec solves developer needs.

So maybe just a subsection called Overview? Then drop the question that TAG is asking?

I don't know, be great to get some additional thoughts on this so we can get it approved and merged ASAP

[ottomorac]

DID WG Discussion 2-Oct:

Wip: Also for the TAG we are now ready

Wip: I am not sure if it makes sense or not to have this "Design Goals and Rationale" section...

ottomorac: I'm trying to emulate other specs out there that had this explanation. There's always a relationship to other specs section. It need not be done this way, just seemed it was the sensible thing to do.

ottomorac: We're pressed for time, I'm open to moving us forward in whatever way works.

Wip: Yes, just concerned that the text from the other PRs doesn't fully address the Design Goals aspect...

Manu: We have this in other WGs, but not normally used for Horizontal Review....

Manu: I think we do need a "Design Goals and Rationale" section, the current content doesn't fully address it, but it is subset of what the TAG requires...

Manu: the PR seems useful, we need to figure out how incorporate it...

Manu: we might even retitle it to "Ecosystem Review" even....

Wip: Yes we can re-title and then add a separate issue to formally require design goals and rationale....

ottomorac: How explicit do we need to be about the text being for the TAG?

Wip: Or it could be called "Ecosystem Overview"

Manu: Yes, we don't need to write this for the TAG directly currently, maybe change the title...

Manu: The TAG wants just clarity on the usefulness of the spec

ottomorac: Ok, maybe ecosystem overview for now, change the title, then we can improve in future.

Wip: yes we can just change the title, and open a separate issue to add "Design Goals and Rationale".....

Wip: also please review these other PRs reviewed, I am keen to get this to the TAG

[ottomorac]

Thanks @wip-abramson . I agree "Implementer Overview" may be a better fit for now.

[TallTed]

Small stuff. Grammar, punctuation, and such.

[peacekeeper]

Looks good..

[peacekeeper]

Multiple approvals, suggestions applied, merging..