Attendees 

Agenda

  1. Open Actions
  2. Administrivia
    1. Board membership
  3. Subcommittee Status
    1. voPerson (Benn)
    2. eduPersonAffiliation
    3. SCIM schema extension for eduPerson (Peter Gietz)
  4. Status of schema
    1. eduCourse
  5. Next steps for eduPerson
    1. https://github.com/REFEDS/eduperson/tree/documentation-hf
      1. OK to merge?
    2. handling of errata
      1. Regarding orcid, this is a fairly straightforward item - need to discuss, though, on the next call to discuss if/how to update narrative text and whether that requires a new release
  6. Creating persistent references to SEB documents?
    1. See, eg, Zenodo (REFEDS Community) or the I2 T&I Document Repository
  7. Note on Core Schema project (I2 TAP activity)
  8. AOB

Notes

  1. Open Actions

    1. Miro has sent the update to Heather for review; there are a few questions to be discussed, and then we’ll bring it back to the group (e.g., historical references)

    2. isMemberOf and hasMember; OBE

    3. OIDs - this is done; Heather to make sure information has been shared outside of Nicole, Niels; action item to close

    4. One Roster and eduCourse - "Since IMS Global is currently working on EduAPI, it is probably premature to spend a lot of time on IMS's OneRoster 1.1 specification: http://www.imsglobal.org/oneroster-v11-final-specification”. Keith to pass info on to the discuss list; action item to close

    5. Handling multiple nominations - Benn has posted something to the list. There is no rush on this, so conversation will be continued there. Close action item.

    6. eduPersonAffiliation subcommittee - definitely interest, Heather will create the appropriate space and mailing list as soon as she has access again

    7. Building automatically - nothing found yet; will continue to look

  2. Administrivia
    1. Board membership
  3. Subcommittee Status
    1. voPerson (Benn) - she work in drafting the 2.0 work. Now that the OID is assigned, a new version of the doc should be ready sooner rather than later (see https://wiki.geant.org/display/URN/OID+Repository for the OID assignment). 
    2. eduPersonAffiliation - subcommittee will be spun up shortly
      1. The Global Alliance for Genomics and Health (GA4GH) is a policy-framing and technical standards-setting organization, seeking to enable responsible genomic data sharing within a human rights framework is interested. In particular, the Data Use and Researcher Identity (DURI) workstream. This is also of significant interest to EOSC.
    3. SCIM schema extension for eduPerson (Peter Gietz) - Peter indicated willingness, and has added it to his sprint, but no additional action see. Heather to follow up again.
  4. Status of schema
    1. eduCourse - see action item re: OneRoster
  5. Next steps for eduPerson
    1. https://github.com/REFEDS/eduperson/tree/documentation-hf
      1. OK to merge? - Done
    2. handling of errata.
      1. Regarding orcid, this is a fairly straightforward item - need to discuss, though, on the next call to discuss if/how to update narrative text and whether that requires a new release
    3. How do we want to handle protocol specific info in eduPerson? Create a draft companion document for a protocol specific implementation
  6. Creating persistent references to SEB documents? This ties back to how to handle errata
    1. See, eg, Zenodo or the I2 T&I Document Repository
    2. To start, we need to tag the GitHub copy with a tag only; not actually put a version number in the file. Then we should also create a PDF file and upload it to Zenodo so we have a DOI, referenceable copy. 
    3. We could differentiate between semantically important changes and shift to following https://semver.org changes. All previously published versions would have an implied major number, which would make 2020-01 to be v7.0.0. Alternatively, look back to consider if there has been any breaking changes in the past. Maybe we’re still at v1?
    4. About having a permanent reference, could have the reference point to a repository which points down to GitHub/markdown. Git as a mechanism to create referenceable material should work, and if/when the item is tagged, you have something specific you can reference.
      1. See also https://guides.github.com/activities/citable-code/

        • Heather Flanagan to review how Zenodo can interact with GitHub, and also look at how this might be used to provide DOIs for the earlier specification

  7. Note on Core Schema project (I2 TAP activity)

    1. There have been various efforts to put together a core schema for campus identity management. This has come up in relation to some work on APIs within I2. Should this be something for the REFEDS Schema Board? Suggest all SEB members take a look and consider if they’d like to get involved, and also to think about if this is something that we would welcome should they ever suggest we take it on. See https://github.internet2.edu/api-schema/person

  8. AOB