InCommon eduGain and release policies

[Peter Schober]

Not really a Shibboleth software discussion...

* Jeffrey Crawford <jeffreyc at ucsc.edu> [2016-01-29 21:18]:
> 3. The reason we've been able to open the service up to wider SP's has been
> the consent page. I have a pretty good handle on what can be "requested" on
> the incommon side, but it looks like eduGain has requested attributes are
> all over the map, does anyone have a list of "good to support" attributes
> not covered by InCommon that should be considered in eduGain?

While there are outliers I think the attributes I list in our
documentaton ("Make attributes available" on 
https://wiki.univie.ac.at/display/federation/Preparing+an+IDP+for+Interfederation )
are the only (widely) relevant attributs in federation -- or
interfederation -- space. (Sorry if I offended someone's pet attribute
by leaving it out).
That's a very small set of data indeed, with only 3 basic types of
attributes (personal names, identifiers, authZ stuff), so far from
"all over the map", IMO.
One could go even further and wonder what the big deal about attribute
release is, if the above (or something not very far from it) makes up
the union of all relevant attributes exchanged between members of
academic identitity federations.
-peter