Address concern around finality of use cases #24
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
brentzundel
approved these changes
Apr 19, 2019
msporny
approved these changes
May 4, 2019
ken-ebert
approved these changes
May 13, 2019
Incorporate Manu's feedback
|
@msporny my latest change incorporated your feedback in "scope". I also noticed in section 2.2 "Other Deliverables", we already called out this deliverable |
|
@msporny @ken-ebert @brentzundel are you ok with the changes I made to address Manu's comments? If so, this editorial PR can be merged. |
brentzundel
approved these changes
May 30, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an attempt to address #9.
We believe the concern is that the current set of DID use cases is final and inflexible.
The language change in this PR is intended to address this concern by clarifying that the referenced DID use cases are only meant to be a starting point.
We understand and agree that use cases are an output of the DID WG (we confirmed they are listed as such in the draft charter.)
(Created during working session with @burnburn and @talltree.)