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

Compare with Current View Page History

« Previous Version 9 Next »

Overview

The REFEDS Steering Committee has approved the launch of a consultation on the adoption of the Academic Institution Entity Category by REFEDS.  This updates and improves on a previous proposal for an Academia Entity Category

The Consultation starts on 24th November 2017 and closes on 8th January 2018 (17:00 CET).  Participants are invited to review the full text and make change proposals in the table below, via issues on the github repository or by email to the REFEDS Coordinators and to express their support / dissension for the category.  It is recommended that you also read the prepared notes on the original proposal and the previous consultation. Discussion is invited at: consultations@lists.refeds.org. 

The main changes in the new proposal are:

  • Definition as Academic Institution rather than Academia.
  • Lower ISCED to level 5.
  • Introduced research hospitals.
  • Introduced a registration criteria section.
  • Better linking to affiliation statements.


The proposed text for the category is available at: https://github.com/leifj/academia-category/blob/master/academia-entity-category.md.

The notes are available at: Academic-Academia.

All comments should be made on: consultations@lists.refeds.org or added to the change log below.  Comments posted to other lists will not be included in the consultation review.

Statements of Support / Dissension


As this category has been contentious in the community, we are asking for organisations to express their support or dissension below to allow us to gauge the appropriateness of REFEDS adopting this approach. 

NameOrganisationReason






Change Log

Change Log for the Consultation on the Academia Entity Category.  The Consultation starts on 20th November 2017 and closes on 8th January 2018 (17:00 CET).  Please fill in your proposed changes to Academia Category below or add them as issues on the github repository.

Number

Current Text

Proposed Text / Query

Proposer

Action

#1Existing TextYour Change ProposalNamePlease leave blank
1

5.3.3 The Identity Provider releases the eduPersonScopedAffiliation attribute.

Should this imply to release this attribute *always* to *all SPs*, including to publishers that are happy with only 'common-lib-terms'? Why should just the IdPs need to do something and not the SPs?
SPs that want to get the scopedAffiliation should either require this attribute in metadata or include a new (to-be-defined in this spec) EC value in metadata. 

Thomas Lenggenhager (SWITCH)
2http://refeds.org/category/academic-institutionGiven that the REFEDS website now does https by default, should this be https://refeds.org/category/academic-institutionGuy Halse (SAFIRE)
35.3.3 The Identity Provider releases the eduPersonScopedAffiliation attribute.How should the Identity Provider’s registrar perform this mandatory check? Would a statement by the IdP administrator be sufficient ?Thomas Lenggenhager (SWITCH)
43. The following URI is used as the attribute value for the Entity Category...Under section 5 only requirements for Identity Providers are defined but normally an IdP uses Entity Support Category not Entity Category. Is this per design or only a mistake?Pål Axelsson (SWAMID)
55.3.3 The Identity Provider releases the eduPersonScopedAffiliation attribute.I would say that the behaviour of releasing euPersonScopedAffliliation to all SPs is not privacy by design as described in GDPR. It's a step away from data minimisation.Pål Axelsson (SWAMID)

Other Comments / Observations

 



  • No labels