Skip to Content.

edugain-discuss - Re: [eduGAIN-discuss] eduGAIN and non "academic" IdPs

edugain-discuss AT lists.geant.org

Subject: An open discussion list for topics related to the eduGAIN interfederation service.

List archive


Re: [eduGAIN-discuss] eduGAIN and non "academic" IdPs


Chronological Thread 
  • From: Martin Matthiesen <martin.matthiesen AT csc.fi>
  • To: edugain-discuss AT geant.net
  • Subject: Re: [eduGAIN-discuss] eduGAIN and non "academic" IdPs
  • Date: Mon, 1 Dec 2014 13:18:27 +0200 (EET)
  • List-archive: <https://mail.geant.net/mailman/private/edugain-discuss/>
  • List-id: eduGAIN discussion list <edugain-discuss.geant.net>

Hi,

----- Original Message -----
> From: "Leif Johansson" <leifj AT sunet.se>
> To: edugain-discuss AT geant.net
> Sent: Monday, 1 December, 2014 13:00:25
> Subject: Re: [eduGAIN-discuss] eduGAIN and non "academic" IdPs

>>
>> That is also my experience. The question is, should it stay that way. It
>> might
>> be enough and then it might be helpful to stress that in official
>> documents.
>> This is yet another reason for me to concentrate on attributes and not
>> make up a
>> second front on entity categories.
>>
>
> This is a more interesting discussion. Basically its what Fredrik Åslund
> just proposed: introduce a new affiliation which has no 'baggage'

To make it clear, I did not suggest a new affiliation value. In my view an
"eduPerson*" attribute implies "academic". I argued for reliable
implementation of attributes, one first step could indeed be to agree on the
semantics of eduPersonAffiliation. "employee" vs "student" as the lowest
common denominator would certainly work for me, if "employee" is only given
to academic staff and thus would be compatible with Clarin ACA.

Martin





Archive powered by MHonArc 2.6.19.

Top of Page