Community Review
This consultation is open from Monday, May 7, 2018 to Monday, June 4, 2018
Background
The InCommon federation has three standing committees that help guide federation operations and activities: The InCommon Steering Committee, The Technical Advisory Committee (TAC), and the Community Trust and Assurance Board (CTAB). Sponsored by all three of those committees, the Attributes for Collaboration and Federation Working Group was formed to research and examine the low adoption rate of the Research and Scholarship Entity Category (R&S) by InCommon members and develop recommendations to increase participation.
Through surveys and interviews, the Attributes for Collaboration and Federation Working Group reached over 130 organizations, examining participation and planned participation in R&S. As a result of this process, the Working Group has drafted a report of its findings and developed a set of recommendations. The Working Group is now soliciting additional feedback through the community consultation process.
Document for review/consultation
For more information about the working group, please see the Attributes for Collaboration and Federation wiki space.
Change Proposals and Feedback - We welcome your feedback/suggestions here
If you have comments that do not lend themselves well to the tabular format below, please create a new Google doc and link to it in the suggestion section below.
| Number | Current Text | Proposed Text / Query / Suggestion | Proposer | +1 (add your name here if you agree with the proposal) | Action (please leave this column blank) |
|---|---|---|---|---|---|
| 1 | Rebrand R&S | "Rebrand InCommon's R&S efforts" to avoid giving the impression to the rest of the eduGAIN community that the recommendation is to change the name of the entity categroy. | Scott Koranda | +1 please don't open that rathole again! | |
| 2 | "less secure alternatives to federation" | Page 5. "less secure and more privacy-invasive alternatives". It's ironic that SPs and IdPs that create incentives to use them "because privacy" are actually driving users to share more personal data! | Andrew Cormack | ||
| 3 | "practical examples" | Page 7. You may cover this later, and it may not apply to InCommon members but I suspect a lot of IdPs would be greatly helped by providing detailed instructions on how to configure their software to support R&S... | Andrew Cormack | ||
| 4 | "bigger tent" | Page 10-11. Can you use the existing R&S SPs as a channel, to explain to researchers how they could make their, and their institutions', lives easier? We've been trying to close the loop between researchers' needs and central IT provision for a long time  | Andrew Cormack | ||
See Also