This consultation is now closed. (Opened on 4 April 2022 and closed on 2 May 2022 at 17:00 CEST)
The SCHema for ACademia, SCHAC <https://wiki.refeds.org/display/STAN/SCHAC>, aims to define and promote common schemas in the field of higher education to facilitate inter-institutional data exchange. This schema is originally the result of the work in the area of attributes coordination carried out within the now-discontinued TERENA Task Force on Middleware, TF-EMC2, and is now being maintained under the auspices of REFEDS <https://refeds.org> and the Schema Editorial Board.
As per the changelog in the document, SCHAC 1.6.0 deprecates the schacGender attribute and updates links from TERENA to GÉANT.
Participants are invited:
- to consider the proposed changes to the SCHAC schema; and
- to propose appropriate changes / challenges to the proposed document via the form below.
The PDF for the consultation is available. Background on SCHAC is available. All comments should be made on: firstname.lastname@example.org or added to the changelog below. Comments posted to other channels will not be included in the consultation review.
Following consultation, the Schema Editorial Board will reconvene to discuss the actions and decisions on the proposals and feedback given.
|comment #||Line/Reference #||Proposed Change or Query||Proposer / Affiliation||Action / Decision (please leave blank)|
|1||161||Thomas Lenggenhager / SWITCH|
We will adjust the references and address several of the 1.5.0 issues. We're not clear on what to do with urn:schac:homeOrganizationType:eu:higherEducationalInstitution and urn:schac:homeOrganizationType:eu:educationalInstitution as those examples do match what's in the spec.
|2||-||Better than referring to ||Thomas Lenggenhager / SWITCH||This makes sense. Will fix.|
|3||185||Adding a European Student Identifier example for ||Thomas Lenggenhager / SWITCH||This makes sense. Will fix.|
|4||7,28,235,615 and page footer(s)||Does deprecating an unused attribute and updating references to the TERENA website justify going from 1.5.0 to 1.6.0? To me that feels more like a 1.5.1, at least going by gut feeling (not by seriously trying to apply semver). The fact that plenty of other issues that were reported years ago (e.g. those mentioned in comment #1 above) have not been dealt with makes this release even less convincing.||Deprecating an attribute, while not a breaking change, is a significant enough action to require a minor number change. If we were introducing a breaking change (i.e., removing the attribute entirely) then we'd want to change this to 2.0. If we were only changing references to the TERENA website, that would be just the patch number update.|