-
Notifications
You must be signed in to change notification settings - Fork 36
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
Add did:plc to the DID Method Registry #19
Comments
Sweet thanks for doing the search on this & getting some resources together! Unfortunately we did a refactor of PLC about a month ago & the README is not up to date (pretty sizable differences in the data model). It's a near term priority! As soon as we get the chance to update the documentation, we'll submit it to the registry |
I started this PR to help push this along, if this is something you want to do: #21 |
looks like I spoke too soon on the formatting issues 😅 |
Just to cross-reference, opened a PR last week over in the W3C DID method registry to add did:plc: w3c/did-extensions#515 |
I've written a "did:plc driver" for the Universal Resolver, but it can't be added until this DID Method is on the Registry.
Instructions for registering a new DID method are here: https://github.com/w3c/did-spec-registries#adding-a-did-method-to-this-registry
For obvious reasons, it's best if that PR is created by one the primary maintainers of this method.
Based on some feedback I received from one of the registry maintainers, it's likely that the registration would be accepted with the spec in its current state. There's some debate about how defined a DID Method spec should be before it is accepted, but the reality is that there are many "in progress" DID Methods registered. And considering that
did:plc
is currently being used by tens of thousands of people in a fairly public setting, I definitely think it'd be in the public interest to have it registered soon.If you'd like, I could also try to submit a PR to this repo to slightly reformat the spec to more closely align with how most other DID Methods are specified. There's no requirement for this format, it just might be a bit easier for people to read.
The text was updated successfully, but these errors were encountered: