BEFORE REQUIREMENTS

[mwherman2000]

BEFORE REQUIREMENTS
cc: @peacekeeper @kimdhamilton

Before trying to nail down into "requirements" we need to discuss and agree on (IMO):

1. the "North Star" for this project
2. project goals and objectives
3. intended audience for the outputs

The previous "requirements lists" are loaded with unstated assumptions. It's impossible to properly validate the previous lists without first discussing and agreeing on 1, 2, 3, 5, and 6.

Then from a requirements perspective, we need to discuss and agree on (IMO):

4. reference glossary
5. reference taxonomy for classification
6. structure of the classification (aka clusters)
7. classification/assignment of the DID methods themselves into the (classification) clusters
8. selection of a model DID Method for each cluster (the exemplar) for each cluster
9. etc. etc.

Here is a list of existing related issues/topics/requirements:

• STRAWMAN: Web 7.0/TDW DID Method Clusters Model 0.1 (Solution Concept) #3 Notes for the Overall Solution Concept
• PROPOSAL: Target Audience for a Particular DID Method Specification #7 Intended Target Audience
• Referencible Glossary of DID Terms and Definitions? #1 Glossary
• Any existing DID method (subject) taxonomies besides what appears in the DID Use Case document? #2 Taxonomy
• Let's refer to a DID Method category as a _cluster of DID Methods_ #5 DID Method Clusters

Other Notes

• https://hyperonomy.com/2024/11/11/catergories-of-decentralized-identifiers-dids