Evolving Attribute Release Policies for campuses

[Tom Zeller]

> On Apr 5, 2016, at 4:36 PM, Wessel, Keith <kwessel at illinois.edu> wrote:
> 
> It might not be enough to tell a user that an attribute is optional; it'd be better to tell them what the SP plans to do with that attribute so they can make an informed decision: is the intended use a feature that the user care about enough to release that piece of their information? That, obviously, involves changes to metadata to allow SPs a place to say what each attribute will be used for. Other registries such as the AAF's federation registry require the SP operator to record the reason for wanting the attribute, but there's currently no place in metadata (that I know of) to pass that text along.

FWIW uApproveJP has extensions which provide a description of requested attributes, see section A "Notification of the using purpose of attributes on SP”.

https://meatwiki.nii.ac.jp/confluence/display/GakuNinShibInstall/Installation+and+configuration+of+uApprove+Jet+Pack+2.5.0