Attendees


Regrets

Agenda

  1. Administrivia
    1. SC membership
    2. Status of MET
    3. R&S 2.0 update
    4. Fixing the REFEDS Participant's Agreement to require Creative Commons Attribution-ShareAlike 4.0 International License instead of CC BY 3.0.
  2. Future home for CoCo
  3. REFEDS Strategic Plan
  4. REFEDS Meeting (30 September 2021)
    1. Propose to make this a discussion based session.
    2. Current proposed topics: Strategy, R&S 2.0, deprecating identifiers.
  5. AOB
    1. macedir.org domain?

Notes

  1. Administrivia
    1. SC membership
      1. Hannah will be stepping down; need to consider a replacement that can represent a research infrastructure lens. Nicole will reach out to REFEDS, FIM4R, FIM4L, and sponsors to encourage nominations.
      2. Nicole will reach out to Rhys directly to see if JISC has anyone able to fill in.
      3. Pål and Maarten have both agreed to stay on.
    2. Status of MET
      1. Work is churning along. It doesn't look like anything as the focus is on refactoring the code, not on new features. They are behind on our original schedule, but that's fair given the contract itself was delayed.
      2. Need to consider what our next development phase will look like. Would like for fedops to edit and maintain their own pages, and also use it so fedops can signal things like support for a given entity category or RAF (REFEDS standards).
    3. R&S 2.0 update
      1. The group has one more call expected before we make a call re: working group consensus and starting the consultation process.
      2. Note that we will have to be very careful to indicate we are explicitly NOT trying to define what research & scholarship is as part of the entity category. The question of categorization is one we may want to tackle another time.
    4. Fixing the REFEDS Participant's Agreement to require Creative Commons Attribution-ShareAlike 4.0 International License instead of CC BY 3.0.
      1. Will go ahead and update the Participants Agreement
  2. Future home for CoCo
    1. We have collectively given up on a formally GDPR-ratified Code of Conduct because it is essentialy impossible to meet the requirements. So, instead we're going to publish this as a best practice guideline and indicate by following these guidelines will help you comply with privacy regulation around the world.
    2. The current URI is an old geant URI that regularly fails to resolve. Given we have no control over that domain, suggest we publish it under a REFEDS URI (as with SIRTFI, entity categories). The process would be to reach out to the community for feedback and send it through a consultation process.
  3. REFEDS Strategic Plan
    1. Generally supportive; would like to develop strategic KPIs out of the Critical Success Factors. Want to be particularly careful, though, to make sure the KPIs are meaningful (example: not just how many people attended, but that we had diverse participation)
    2. We do further want to consider if and how we would enforce our standards and best practices at (at least) a fedop level.
    3. We have implied, though not explicitly stated, that we're accepting that we are a defacto standards organization. It would be helpful to document how all the standards and standards orgs used by our standards and best practices relate to each other; this would be part of the curation aspect of the strategic plan.
  4. REFEDS Meeting (30 September 2021)
    1. Propose to make this a discussion-based session.
    2. Current proposed topics: Strategy, R&S 2.0, deprecating identifiers.
      1. Nicole will take Strategy, Heather will take R&S; Heather and Nicole will figure out who should run the identifiers conversation
  5. AOB
    1. macedir.org domain?
      1. macedir.org no longer resolves to anything; everything in that space was handed over to REFEDS. The URL, though, is referenced in several entity categories and the entity category RFC itself. If the domain lapses, we could have a problem. Unclear who owns the domain; Albert to follow up.

Action items