...
| Advanced Tables - Table Plus |
|---|
| columnAttributes | style="vertical-align:middle;",style="width:60%;vertical-align:middle;",style="width:40%;vertical-align:middle;" |
|---|
|
| InCommon R&S Requirement | REFEDs R&S Requirement |
|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="9e98bd44a14abe76-ad5a8786-41574fa1-bd32aa3e-5e1bffc79e873388c5e34526"><ac:plain-text-body><![CDATA[ | 1 | [[Participation Agreement | http://www.incommon.org/docs/policies/participationagreement.pdf], section 9] Participant agrees to respect the privacy of and any other constraints placed on identity information that it might receive from other InCommon Participants as agreed upon between Participant and the InCommon Participant(s). In particular, Participant understands that it may not permanently store nor share or disclose or use for any purpose other than its intended purpose any identity information that it receives from another InCommon Participant without express written permission of the other InCommon Participant. Participant understands that the storing and sharing of resources is between the Participant and the InCommon Participant(s) and is not the responsibility of InCommon. | A "Service Provider claims that it will not use attributes for purposes that fall outside of the service definition." | ]]></ac:plain-text-body></ac:structured-macro> | 2 | "Whether an SP operator is commercial or non-commercial is not relevant to eligibility for the R&S Category, nor are any other aspects of how the service is implemented or operated, beyond the specific requirements noted below. It's all about purpose." | "This Entity Category should not be used for access to licensed content such as e-journals." | 3 | "...because of the risk involved, a Service Provider that engages subjects in experiments that require specific oversight is not eligible for the R&S Category." | NA | 4 | "The SP provides an mdui:DisplayName in metadata..." | "The Service Provider provides an mdui:DisplayName and mdui:InformationURL in metadata." | 5 | "The SP provides Technical and Administrative contacts in metadata." | "The Service Provider provides one or more technical contacts in metadata." | 6 | "R&S category SPs may request other attributes, but IdP operators will likely require a prior agreement before releasing additional attributes." "It is therefore highly recommended that SPs use a minimalist approach to attributes, only requesting those attributes that they absolutely need." | "Service Providers SHOULD request a subset of R&S Category Attributes that represent only those attributes that the Service Provider requires to operate its service." | 7 | http://id.incommon.org/category/research-and-scholarship | http://refeds.org/category/research-and-scholarship |
|
...
For clarity, these two requirements are broken into three parts on the R&S application form:
| Wiki Markup |
|---|
\[True/False\] My service provides requested attributes in metadata. |
| Wiki Markup |
|---|
\[Yes/No\] Are the requested attributes in metadata a subset of the R&S attribute bundle? (Note: This is highly RECOMMENDED otherwise a bilateral agreement with each IdP may be required.) |
| Wiki Markup |
|---|
\[True/False\] My service requests only those attributes required to operate the service. |
The second requirement above is framed as a yes/no question while the others are strict requirements In particular, the latter is a strict requirement for all InCommon R&S SPs, which goes beyond the REFEDS R&S requirements.
Entity Attributes
The Obviously, the entity attribute value for InCommon R&S is different than the entity attribute value for REFEDS R&S. In the short term, the goal is for all InCommon R&S SPs to have a multivalued entity attribute in metadata, that is, each SP will satisfy the requirements of both InCommon R&S and REFEDS R&S (which is possible since the gap between them is small). Once all R&S SPs have a multivalued entity attribute in metadata, all InCommon R&S IdPs will be encouraged to migrate their configurations to the REFEDS R&S entity attribute value, that is, to release the R&S attribute bundle to all R&S SPs, globally.
...