Date: Fri, 29 Mar 2024 11:05:39 +0000 (UTC)
Message-ID: <187150368.7875.1711710339585@ip-10-10-7-29.ec2.internal>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_7874_66160100.1711710339584"
------=_Part_7874_66160100.1711710339584
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
In the decade since the release of the first version of the eduP=
erson specification, divergences in usage emerged and grew. The cause=
s were varied, but the result is that the eduPerson{Scoped}Affiliation attr=
ibute(s) and values are interpreted and used in multiple and sometimes inco=
mpatible ways across sites.
There is no practical way to bring current practices back to some ideal =
and well-defined state. It may, however, be possible to profile the u=
se of eduPerson{Scoped}Affiliation for use in federated access control scen=
arios. This wiki page is devoted to exploring that possibility, working tow=
ard consensus across the global community of eduPerson implementations and =
promoting the adoption and adherence to this eduPerson profile, specificall=
y in the federated usage scenario.
Approaches to Profiling eduPerson
- Recommend exclusive use of a well-defined and commonly understood subse=
t of the controlled vocabulary for eduPerson{Scoped}Affiliation; Initial dr=
aft proposal:=20
- "faculty",
- "student",
- "staff" (when distinguished from "faculty"),
- "member" (as "all faculty, students and staff plus other persons who ar=
e considered to be full members of the institutional community as regards a=
ccess to resources and services"),
- "alum" and
- "affiliate" (defined to be anyone affiliated with the university who is=
NOT a "member" or "alum"
- NOTE: This does not depend on all parties agreeing to a single strict, =
detailed and precise definition of these named affiliations. To the degree =
that eduPerson{Scoped}Affiliation has proven useful, it has done so while a=
llowing for reasonable variation in definitions across institutions.
- Acknowledge that many sites have created their own values for ePSA to s=
uit their need for a local set of affiliation values.
- Adopt a live and let live attitude to the above practice of extending t=
he value space for ePSA--PROVIDED THAT in federated and more generally inte=
r-institutional scenarios, institutional use of eduPerson{Scoped}Affiliatio=
n does not violate the community-blessed profile that emerges from this wor=
k.
------=_Part_7874_66160100.1711710339584--