Versions Compared

Old Version 1

changes.mady.by.user Heather Flanagan

Saved on

compared with

New Version Current

changes.mady.by.user Heather Flanagan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: added notes

Attendees:

Agenda:

Affiliation and Entitlement Use Cases

  1. Recap of last call
    1. This committee will not consider removing any existing affiliation values

    2. This committee cannot provide a definition for a researcher affiliation that would be globally accepted. The scope of an entitlement, however, can be as broad or as narrow as necessary; if the requirement is global, can’t do it, but if we can work locally with just a handful of definitions, then we can guide the use of entitlements. 

      • Renter.fr.researcher = local entitlement

      • InCommon.org.researcher = local entitlement

    3. If definitions converge over time, the discussion regarding a definition for an affiliation value of "researcher" may be reopened
  2. Discussion: defining "sponsored" (and possibly coming up with a better name)
  3. AOB


Notes:

V/C information

Topic: eduPersonAffiliation subcommittee
Time: Sep 8, 2020 09:00 AM Pacific Time (US and Canada)
Every 2 weeks on Tue, until Dec 15, 2020, 8 occurrence(s)
Sep 8, 2020 09:00 AM
Sep 22, 2020 09:00 AM
Oct 6, 2020 09:00 AM
Oct 20, 2020 09:00 AM
Nov 3, 2020 09:00 AM
Nov 17, 2020 09:00 AM
Dec 1, 2020 09:00 AM
Dec 15, 2020 09:00 AM
Please download and import the following iCalendar (.ics) files to your calendar system.
Weekly: https://us02web.zoom.us/meeting/tZMrcu-vrTojHdJijGoD-iRTEoWTjrxc_6FK/ics?icsToken=98tyKuGvqD4sHdeUuR6BRpwEBI_4M-3ztn5Egqd3lRXCDAQeazHCE-11BrhtCNvv

Join Zoom Meeting
https://us02web.zoom.us/j/87656731976?pwd=NG03WWFkUXV3UG1CbnV5OFZwRjhGUT09

Meeting ID: 876 5673 1976
Passcode: 843387
One tap mobile
+12532158782,,87656731976#,,,,,,0#,,843387# US (Tacoma)
+13462487799,,87656731976#,,,,,,0#,,843387# US (Houston)

Dial by your location
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
+1 669 900 6833 US (San Jose)
+1 312 626 6799 US (Chicago)
+1 929 205 6099 US (New York)
+1 301 715 8592 US (Germantown)
Meeting ID: 876 5673 1976
Passcode: 843387
Find your local number: https://us02web.zoom.us/u/kcuYpbdyT1

Join by Skype for Business
https://us02web.zoom.us/skype/87656731976

Agenda:

Affiliation and Entitlement Use Cases

  1. Recap of last call

  2. This committee will not consider removing any existing affiliation values

  3. This committee cannot provide a definition for a researcher affiliation that would be globally accepted. The scope of an entitlement, however, can be as broad or as narrow as necessary; if the requirement is global, can’t do it, but if we can work locally with just a handful of definitions, then we can guide the use of entitlements. 

    • Renter.fr.researcher = local entitlement

    • InCommon.org.researcher = local entitlement

  4. If definitions converge over time, the discussion regarding a definition for an affiliation value of "researcher" may be reopened

  5. Discussion: defining "sponsored" (and possibly coming up with a better name)

    1. The Ohio State uses this term for all their guest accounts; “sponsored” just means someone is sponsoring their account

    2. Not sure that contractors/temp accounts are considered a classification more broadly

    3. Reminder that eduPersonAffiliation was intended to be a search value; it was not intended for access control. Access control should be covered by entitlements. Entitlements can be used as a broad basis that acts as one piece of information for access control decisions.

    4. If there is licensed online-only software, and the licensing contract is for staff only, is there any benefit to moving from an affiliation to an entitlement? If two vendors decide to disagree about what “staff” means for the purposes of their contract, then the policy decisions that define the relationship (the affiliation) then there is a significant problem. Better to automate an entitlement for that application that may use the “staff” affiliation as part of its assignment so if the policy changes with that vendor, then that does not impact the institution-wide policy that defines the staff affiliation.

    5. Can we create a centralized location for organizations to register their definition of an entitlement value? Would this be used? Do vendors have enough information and use the tools (e.g., Ping Federate, Shibboleth)

    AOB

    1. that could support this?

      1. We could update the spec to point to a wiki page where people could put in information about their definitions for values and policies.

Conclusion

We don’t seem to have a clear set of applications that would be able to consume “sponsored”. This would likely be something more internally focused within an institution. We do not have consensus nor a broad enough set of stakeholders from the interested communities to add anything to the controlled vocabulary for eduPersonAffiliation. Entitlement is open for organizations to use as they feel necessary, and we will work on creating a place for organizations to register the entitlement values and policies if they so choose. Given that, we will cancel future calls for this subcommittee; Alan, Heather, and Christos will report back to the Schema Board

For future work, a more concrete proposal needs to be initiated before a subcommittee is formed to discuss.  The subcommittee is not the right place to create the definition.