-
Notifications
You must be signed in to change notification settings - Fork 19
Data authorization #59
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
Conversation
|
Very interesting direction! At least on first reading, I'm finding the multi-part AccessDecorator(Index/Series/etc) system to be really hard to understand. But maybe it'll get clearer on multiple readings. |
elf-pavlik
left a comment
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.
My two inline comments should explain why we may not need to define inverse counterpart for any property.
Will be adding text to explain that, but essentially the decorators allow us to add labels and descriptions to data without tying them directly to it. This allows us to have access needs that can be described in different languages, or (depending on the context) different ways |
Maybe this would be improved by a leading example UI which associates features (text comes from the AppDecorator) with their required resources (text comes from the ShapeTreeDecorator). (i miss email threads, quoting is a noisy substitute) |
Introduces Data Authorization workflows, with Access Needs, Access Grants, Access Receipts, and Remote Data Registration.