The Incommon Federation wiki has moved.

Please visit the new InCommon Federation Library wiki for updated content. Remember to update your bookmarks.

Click in the link above if you are not automatically redirected in 15 seconds.



You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This page is not yet public!

Change in Requirements to Become a Member of the Research & Scholarship Category

  1. The human subjects requirement was removed from the R&S definition on Dec 1, 2014 (an accounting of the governance process that led to this change is documented elsewhere in this wiki)
  2. The current R&S requirements have been aligned with the new REFEDS R&S specification (see the gap analysis to understand the differences between InCommon R&S and the new REFEDS R&S specification)
  3. Except for the human subjects requirement, the new R&S requirements (as shown on the new R&S application form) are backwards compatible with the previous set of R&S requirements. Thus every R&S SP that submits the new application form will receive two R&S entity attribute values in metadata, one denoting InCommon R&S and another signifying compliance with the REFEDS R&S specification. The legacy InCommon R&S entity attribute value is for backwards compatibility only, so that IdPs continue to release attributes to the same set of R&S SPs.

Note to SP Owners

Nothing will change at your SP as a result of submitting the new R&S application form. When you are ready to interoperate with global R&S IdPs, let us know (admin@incommon.org) and we will make arrangements to export your SP’s metadata to eduGAIN.

Note to IdP Operators

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, that is, to release the R&S attribute bundle to all R&S SPs, globally.

#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels