...
This definition is written in compliance with the Entity Category SAML Entity Metadata Attribute Types specification [EntityCatTypes]; this specification may be extended to reference other protocol-specific formulations as circumstances warrant. An FAQ for the Entity Category has been made available to help deployments [R&SFAQ]. This specification may be extended to reference other protocol-specific formulations as circumstances warrant.
1. Definition
Candidates for the Research and Scholarship (R&S) Category are Service Providers that are operated for the purpose of supporting research and scholarship interaction, collaboration or management, at least in part.
...
Identity Providers may indicate support for Service Providers in this category to facilitate discovery and improve the user experience at Service Providers. Self-assertion is the typical approach used by but this is not the only acceptable method.
...
All of the above attributes are defined or referenced in the [eduPerson] specification. The specific naming and format of these attributes is guided by the protocol in use. In the case of For SAML 2.0 the [SAMLAttr] profile MUST be used. This specification may be extended to reference other protocol-specific formulations as circumstances warrant.
...
An Identity Provider that does not release all of the required elements of the R&S attribute bundle (shared user identifier, person name, email addressdefined in section 5), for any reason, SHALL NOT exhibit the R&S entity attribute in its metadata. Exceptions that limit the release of attributes to specific R&S Service Providers may be permitted in the event of a security incident or other isolated circumstances.
A persistent, non-reassigned, non-targeted identifier is REQUIRED. If the Identity Provider’s deployment of eduPersonPrincipalName is non-reassigned, and the organization believes in good faith that it will remain so, it will suffice. Otherwise the Identity Provider MUST release eduPersonTargetedID (which is non-reassigned by definition) in addition to eduPersonPrincipalName. In any case, release of both shared user identifiers is RECOMMENDED.
...