v3 consent to attribute release : half-thoughts on UIs

[Cantor, Scott]

On 9/18/14, 11:22 AM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>
>The class yes, public, the fields, of course, no, private. While
>sketching, I skipped accessor methods.

Yes, I just meant the class. Like I said, I would suggest we avoid making
anything public when it comes to the implementation of the flows, but we
might want to (now or later) have a base class or interface that has
sufficient common fields across all "decision" objects so that there's
commonality and fields in the serialized JSON that can be read and
understood by a management page, but only enough to dispatch the result to
another subflow to actually parse/report/manipulate.

-- Scott