-
Notifications
You must be signed in to change notification settings - Fork 20
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 use case for client to discover access privileges #136
Conversation
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.
Suggested some language adjustment where I think I could understand what was intended, and requested some more where I could not understand what was intended.
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
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.
Explains the need well 👍
|
||
For example, for user level permission, if the application is not granted | ||
[=write access=] on the resource that Guinan is currently editing, the user | ||
interface can disable the "Save" button in the menu. Guinan also wants to know |
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 would prefer to end this use case here and move "Guinan also wants to know ..." to a dedicated use case. I can make PR after merge.
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.
looks good :-)
Based off a number of existing discussions and work:
Certainly there are other issues lying around... and this is a fairly common. It also goes along with some of the other use cases.
Aside: solid/specification#210