moving UCR from auth panel #41
Conversation
|
Great kick off! I suggest changing the order; Use Cases normally precede Requirements. If you can connect the UCs to the User Stories at https://github.com/solid/user-stories (see issues), that'd be very helpful. We also need some kind of feedback from the community (survey). See the first comment in solid/specification#9 for general direction and also links to example UCRs from W3C TR. |
|
@elf-pavlik I had a discussion with @csarven on friday about putting these directly into the solid/specification repo. For myself I think this is a good idea. I think we can tune it up a bit in here (get the structure right, etc), and then submit it into the specification repo as a proposal. IMO we should try to get that done quickly in here, and then operate on it directly under the solid/specification repo moving forward |
| Introduction {#intro} | ||
| ===================== | ||
|
|
||
| Issue: Needs explaination how proposals should clearly reference requirements which they satisfy. As well as requirements they do not satisfy due to some limitations. |
There was a problem hiding this comment.
I think it's also important to provide some expectations around use case scope. We should focus mostly on lean and easy to understand use cases and requirement that don't drift too far away from practical use, so they can be as informative and referenceable as possible.
|
|
||
| Requirements {#requirements} | ||
| ============================ | ||
|
|
There was a problem hiding this comment.
I feel like requirements should be categorized (e.g. authentication, authorization, identity, validation, resource access, security), but use cases should specifically not be, since good ones should span categories.
|
|
||
| Use Cases {#use-cases} | ||
| ====================== | ||
|
|
There was a problem hiding this comment.
It feels like the use cases should be organized more based on the unique pattern that they're demonstrating, so they can be found and navigated more intuitively.
|
Instead of trying to address all the ideas in this PR I would prefer to merge it and invite everyone to submit following up PRs with amendments. In case anyone sees problem but doesn't feel ready to submit PR we can open an issue and have preliminary discussion there.
SGTM let's iterate via multiple PRs |
|
I've no objection to moving any changes to a different PR but I'm not sure if a review here serves much purpose. Go for it I guess. |
|
Merging this in - will iterate in successive PRs to incorporate some of the feedback left in this one. |
This suppose to provide starting point for Use Cases and Requirements document. Current content comes directly from https://github.com/solid/authorization-and-access-control-panel/pull/66/files
EDIT rendered HTML preview