v3 consent to attribute release : more than per entity ID ?

[Tom Zeller]

On Fri, Sep 5, 2014 at 3:27 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 9/5/14, 4:15 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>>So, I guess my question is, should consent storage be keyed by entity
>>ID, or something else ? My assumption is that storage should be
>>per-entity ID, and applying consent to more-than-one entity would be
>>done by a configured predicate of some sort.
>
> I don't think a predicate by itself really works because of the lookup
> step. You have to know how to look up the previous decision.
>
> But a more general design would be a Function injected to map from
> ProfileRequestContext to the storage key. Then it's possible to default to
> the RelyingPartyId function but plug in anything else, including my
> suggestion above.

Oh great. So, restating, the attribute consent flow descriptor would
provide a function to map from PRC to storage key and a function to
map from PRC to user identifier.