v3 consent to attribute release : half-thoughts on UIs

[Tom Zeller]

> Virginia Tech is very much interested in the management page. Here's a
> minimal version of what we imagined:
>
> https://www.middleware.vt.edu/pubs/shib/uapprove-mock/prefs.html

Thanks.

> I thought that the notion of per-attribute release control was ruled
> out in a recent discussion. Maybe I'm remembering wrong.

Probably the UI, but I'd like the flow to be able to support it, so
that the UI can be figured out later, and be customizable by
deployers.

Mostly I'm hoping to get the serialization of consent "right", so that
it can be stored client-side, maybe passed as request parameters, and
extensible.