-
Notifications
You must be signed in to change notification settings - Fork 99
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
Editorial updates #86
Conversation
index.html
Outdated
This document specifies a common data model, format, and operations that | ||
all <a>DIDs</a> support. | ||
This document specifies a common data model, a URL format, and a set of operations for | ||
<a>DIDs</a> and related components. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"DIDs and related components" doesn't make much sense to me; what are those "related components"? Syntax components like DID path or DID query? Or architectural components like DID registry and DID resolver?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I meant like DID documents and DID methods. I can change it to that.
@rhiaro can you make the changes please, I don't have commit rights to your branch. @iherman, @brentzundel, @burnburn -- can we give @rhiaro and @grantnoble permission to open/edit PRs in the repo... it's going to be difficult for the editors to coordinate with them w/o this (and I expect a fair number of PRs from both of them over the next two years). |
Co-Authored-By: Ted Thibodeau Jr <[email protected]>
Editorial, multiple positive reviews, comments addressed, merging. |
@msporny, although this is moot as far as this repo is concerned, I have made some changes and @rhiaro, as well as @grantnoble have now the right to create a PR in this repo. However, only the editors should have 'merge' rights. At least that is the intention... see if it works next time, @rhiaro ! |
Great, thank you @iherman! :) |
Solves most of #48, and should close #38 and #40.
Preview | Diff