Guidelines for
...
expressing affiliation information
...
across infrastructures
Summary
This document describes the semantics associated with the use of the affiliation attributes eduPersonAffiliation and/or eduPersonScopedAffiliation when these are asserted by an Infrastructure Proxy when communiting to connected service providers and other Infrastructure Proxies.
DavidG: as I cannot edit or suggest in the Google doc: please fix/write this one quickly and - my preempting the discussion outcome - it should conclude by saying for the value of the ePSA/ePA: the semantics of eduPerson(Scoped)Affiliation changes for the Infrastructure Proxy .The value SHALL reflect the affiliation of the identity with the Infrastructure.The goal of this document is to define how affiliation information should be expressed when transported across AARC BPA-compliant AAIs. Two different types of affiliation have been identified, namely Affiliation within the Home Organisation, such as a university, research institution or private company; and Affiliation within the Community, such as cross-organisation collaborations. Both affiliation types should be communicated to the service providers that rely on affiliation information in order to control access to resources.
Links
Working docs
Google doc: https://docs.google.com/document/d/1o6uLlUW59F61mdImPGMCAwBR4KH4lfQIaLMfaqhOW3Q
Final PDF
...
View file | ||||||
---|---|---|---|---|---|---|
|
Meetings schedule and Minutes
Date | Location | Agenda | Minutes |
---|---|---|---|
YYYY-MM-DD HH-MM TIME-COORDINATES (UTC/CEST/...) | link to webconf platform/room | IMPORTANT insert link to PUBLIC PAGE | IMPORTANT insert link to PUBLIC PAGE |
...