decentralized-identity / decentralized-identity/did-methods

BEFORE REQUIREMENTS

Open
#11 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
21
Forks
20
PR merge metrics
No merged PRs in 30d

Description

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:
- https://github.com/decentralized-identity/did-methods/issues/3 Notes for the Overall Solution Concept
- https://github.com/decentralized-identity/did-methods/issues/7 Intended Target Audience
- https://github.com/decentralized-identity/did-methods/issues/1 Glossary
- https://github.com/decentralized-identity/did-methods/issues/2 Taxonomy
- https://github.com/decentralized-identity/did-methods/issues/5 DID Method Clusters

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

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the linked issues on the overall solution concept, intended target audience, glossary, taxonomy, and DID method clusters. This issue is complete when the project’s North Star, goals, audience, glossary, taxonomy, cluster structure, and exemplar-selection requirements are discussed and agreed.

Written by the indexing model from the issue text.

Assessment

Domain
design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.