Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: trying to make category distinctions clearer

...

REFEDS Research & Scholarship

Membership in this category https://refeds.org/category/research-and-scholarship/category REFEDS R&S is reserved to services "that support research and scholarship interaction, collaboration or management as an essential component.". This globally applicable category takes a risk-based approach to enabling access to high-benefit/low-risk services, releasing only low-risk personal data. Basically only the minimum personal data required for scientific collaboration and attribution of a person's work work is released (name, email address and an identifer) is released.

Info
iconfalse

REFEDS R&S is purpose- and attribute limited: Only services fitting the purpose requirements may apply, and those services may only request a very limited set of low-risk attributes. It is being used gobally.

...

GEANT EU/EEA Data Protection Code of Conduct

As part of the Code of Conduct Conduct Cookbook you'll find the Recipe for a Home Organisation, giving complete instructions on the necessary steps for deployment. This Service Category only applies when both the Service Provider and the Identity Provider are based in the EU/EEA (i.e., it does not help with services outside the EU/EEA) and takes a rather literal reading of uses the EU data protection directive ( as common frame for disparate implementations thereof throughout the EU). As such it is mostly meant as a reminder and a reassurance to both service owners and home organizations that the services covered are already subject to (national implementations of) EU data protection law.

Info
iconfalse

GEANT Data Protection Code of Conduct is legislation-limited: Only services from specific legislations (EU/EEA or "equivalent") may carry this category, and only if they correctly submit themselfs to the GEANT Data Protection Code of Conduct and all its requirements.

As this Category definition does not specify an attribute bundle (i.e., it doesn't reference specific attributes which should be released) the list of attributes to release is basically open-ended. As such you may need to adapt the attribute rules included within the example policy produced below, possibly including more (fewer or fewer) more attributes (depending on what attributes if you have those available in your IDP and whether the institution is willing to release them at all). The confguration below is an example based on the most commonly used attributes in Identity Federations today which most/all eduID.at Identity Providers should be able to generate.

...