v3 consent to attribute release : ask-again ?
Cantor, Scott
cantor.2 at osu.edu
Wed Aug 20 19:29:27 EDT 2014
On 8/20/14, 6:24 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>Given per-attribute release consent, rather than "accept" or "reject"
>as possible user choices, how about "ask-me-again : never | always |
>in one year | ... ? "
I don't know how that maps to the main toggle of whether to release
something or not.
My intuition would be that you don't ant to overload the UI with choices
that have to scale with the number of attributes.
I would think the per-attribute decision is "include/exclude", with the
"ask-me-again" decision being a macro choice applying to the whole
decision.
Maybe "each time | in a year/month/whatever unless anything changes | in a
year/month/whatever regardless of changes".
But I'm inclined to believe that fewer choices is best, and that the "if
anything changes" part should just be a deployment choice, or maybe not
even a choice, just baked in. Not clear what consent could really mean if
it doesn't even prompt for a different set of data.
-- Scott
More information about the dev
mailing list