Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PROPOSAL: Ability to submit multiple DID method applications when the underlying specifications are identical with a single PR #608

Closed
mwherman2000 opened this issue Dec 10, 2024 · 7 comments

Comments

@mwherman2000
Copy link
Contributor

mwherman2000 commented Dec 10, 2024

Ability to submit multiple DID method applications when the underlying specifications are identical with a single PR

@mwherman2000 mwherman2000 changed the title Ability to submit multiple DIF method applications when the underlying specifications are identical PROPOSAL: Ability to submit multiple DIF method applications when the underlying specifications are identical with a single PR Dec 10, 2024
@mwherman2000
Copy link
Contributor Author

ALTERNATE: can a single PR include multiple tightly coupled DID method names pointing to a single unified specification.

@mwherman2000 mwherman2000 changed the title PROPOSAL: Ability to submit multiple DIF method applications when the underlying specifications are identical with a single PR PROPOSAL: Ability to submit multiple DID method applications when the underlying specifications are identical with a single PR Dec 10, 2024
@TallTed
Copy link
Member

TallTed commented Dec 11, 2024

What is the point of multiple DID methods with identical specifications?

@mwherman2000
Copy link
Contributor Author

What is the point of multiple DID methods with identical specifications?

They are for a new Web 7.0 Sharded DID Registry architecture we're deploying.

image

@peacekeeper
Copy link
Contributor

I have the same question as @TallTed , I don't understand what's the point of having multiple DID methods with the same specifications. Also see my comment #603 (review).

@mwherman2000
Copy link
Contributor Author

@peacekeeper Read #608 (comment)

@TallTed
Copy link
Member

TallTed commented Dec 11, 2024

Please don't use screenshots to communicate textual information. Among other things, this makes participation more difficult if not impossible for people with various visual impairments.

@davidlehn
Copy link
Contributor

What is the actionable proposal? Is there text that restricts the content of a request? Regardless of instructions, people can request what they want. Acceptance of requests, simple or complex, depends on the request content, the explanation, and discussion, similar to any other change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants