Deal all,
in eduGAIN LexisNexis Advance SP request optionally eduPersonScopedAffiliation and eduPersonTargetedID attributes. [1] In Austrian eduID.at it requests these two attributes as required. [2] In French RENATER it requires eduPersonScopedAffiliation, eduPersonTargetedID, givenName, sn, mail attributes and supports Code of Conduct and Sirtfy entity categories. [3]
I am wondering whether everyone could be fine with following set of attributes along with CoCo and Sirtfy entity categories support: eduPersonScopedAffiliation (required) eduPersonTargetedID (optional) givenName (optional) sn (optional) mail (optional)
Universities/libraries may choose to release just eduPersonScopedAffiliation and be FIM4L privacy stars. It will correspond to the upcoming REFEDS Anonymous Authorisation entity category. [4]
Universities/libraries may also choose to release eduPersonScopedAffiliation and eduPersonTargetedID for enabling personalisation capabilities. It will correspond to the upcoming REFEDS Pseudonymous Authorisation entity category. [5]
And finally universities/libraries may also choose to release eduPersonScopedAffiliation, eduPersonTargetedID and let users decide about releasing name and e-mail address. [6]
Do you like this kind of approach?
Take care
Jiri Pavlik, techlib.cz
1. https://met.refeds.org/met/entity/https%253A%252F%252Fsignin.lexisnexis.com%...
2. https://met.refeds.org/met/entity/https%253A%252F%252Fsignin.lexisnexis.com%...
3. https://met.refeds.org/met/entity/https%253A%252F%252Fsignin.lexisnexis.com%...
4. https://wiki.refeds.org/display/CON/Entity+Category+Consultation+Anonymous+A...
5. https://wiki.refeds.org/display/CON/Entity+Category+Consultation+Pseudonymou...