v3 consent to attribute release : half-thoughts on UIs

[Tom Zeller]

>>I've done a little sketching of what the Java consent object would
>>look like, here is what I've got so far, obviously the fields should
>>not be public :
>
> What does the object here model? A decision? Or something to do with the
> logic of the subflow?
>
>>and the fields of a default impl would look like the current uApprove
>>AttributeReleaseConsent object or PrivacyLens' AttributeReleaseChoice:
>
> So this is really the object that's modeling a decision outcome?

Yes.

> My feeling is that we want to avoid making that public at all, provide an
> example in what we're implementing, and then we can copy or evolve that
> later, including making it public.
>
> I think we'll waste too much time trying to get it "right" now, and we
> won't get it right.

> I need some help understanding its role, and whether it's meant to be
> public or not.

The class yes, public, the fields, of course, no, private. While
sketching, I skipped accessor methods.