-
Notifications
You must be signed in to change notification settings - Fork 206
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
Split the DID Specification Registries into separate documents #568
Comments
So clearly there is a need to at least split out §14: DID Methods from the rest. I could make an argument that that is the only split needed. But if we do more, it is not as clear to me where the other dividing lines are. At first glance, splitting out every section into a separate registry document probably overkill. One possible organization is to split into 5 portions:
My only reservation about this is that some smaller lists within a section might be more (or less) security sensitive, and thus have different registration and review requirements compared to the rest of the section. For instance, in §5: Property Names, there is §5.4.1: Service Endpoints, which probably should be much less restrictive to add to then adding new §5.2 Verification Relationships. |
I agree with @ChristopherA's proposal above. Regarding the mechanics of how that could work, we could:
At a minimum, I believe that's all we need to do to enact @ChristopherA's proposal above. |
I would also like us to consider:
|
Wondering if this can be closed now, given the migration to did-extensions is complete |
@msporny ? |
This is complete. |
There was a suggestion on the last telecon to split the registries into separate documents. This issue is intended to track that request and create a proposal that could achieve consensus and be acted upon by the Editors. Options include:
This is related to #565.
The text was updated successfully, but these errors were encountered: