Versions Compared

Old Version 1

changes.mady.by.user Heather Flanagan

Saved on

compared with

New Version 2

changes.mady.by.user Heather Flanagan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: added meeting notes

V/C info

Topic: REFEDS Schema Editorial Board - May 2021
Time: May 24, 2021 13:00 Pacific Time (US and Canada), 22:00 CEST, 06:00 25 May AEST

Join Zoom Meeting
https://us02web.zoom.us/j/82018075711?pwd=MHh6ZkhKTTF3ZHRjYXZBblhJTlpkUT09

Meeting ID: 820 1807 5711
Passcode: 419675
One tap mobile
+12532158782,,82018075711#,,,,*419675# US (Tacoma)
+16699006833,,82018075711#,,,,*419675# US (San Jose)

Dial by your location
+1 253 215 8782 US (Tacoma)
+1 669 900 6833 US (San Jose)
+1 346 248 7799 US (Houston)
+1 929 205 6099 US (New York)
+1 301 715 8592 US (Washington DC)
+1 312 626 6799 US (Chicago)
Meeting ID: 820 1807 5711
Passcode: 419675
Find your local number: https://us02web.zoom.us/u/keI1pjVvdF

Join by Skype for Business
https://us02web.zoom.us/skype/82018075711

...

Attendees:

Absent

Agenda

  1. Open Actions
  2. Administrivia
    1. Voting - eduPersonAnalyticsTag
  3. Subcommittee status
    1. voPerson
  4. Status of splitting the eduPerson spec into core and supplemental
    1. Splitting Protocols From Schema Documents
  5. Review of Work Item Portfolio
  6. Releasing a new version of the eduPerson schema
    1. normative location?


Notes

  1. Open Actions (where we have updates)
    1. Benn has sent an email to schema-discuss; no feedback received. This was just an FYI, though, so no further action required.
    2. ssh ldap public key schema - Benn has been in contact with the maintainer; this is now ready to transfer and in the hands of the REFEDS/GEANT team to go through the steps
    3. progress of 6338bis - Miro has not heard back from Barry Leiba; Heather will follow up
  2.  Administrivia
    1. Voting - eduPersonAnalyticsTag
      1. We may want to introduce a new workflow for future attributes that would require some real-world experience to see if this attribute is actually used. We could put it in an experimental category and assign an OID there. Suggest formalizing the process that would say something like "if you want to introduce a new attribute to any schema managed by the schema board, you must come up with the proposal, draft the spec, demonstrate multiple implementations (organizations willing to use it), and then go through final consultation."
      2. Alternatively, we could also add this to an Experimental category (similar to what SCHAC has). Would need to define what it means to be experimental; probably something about no guarantees this attribute will persist if no production use is found.
        •  Heather Flanagan will draft a definition for experimental and send it to the schema board for discussion; when this is approved by the schema board, we'll take it to the community and suggest we'll be experimenting with the experimental tag on the eduPersonAnalyticsTag proposed attribute
  3. Subcommittee status
    1. voPerson - closed half the remaining issues for 2.0. One big issue remains (shifting to AsciiDoc format instead of Markdown).
  4. Status of splitting the eduPerson spec into core and supplemental
    1. Splitting Protocols From Schema Documents
    2. The TAP Attribute Dictionary is just about ready for v1; this will come back to the Schema Board after v1 tag is assigned.
    3. Keith has made progress on porting the eduPerson attributes into the TAP format - see https://github.internet2.edu/api-schema/attribute-dictionary/blob/draft/eduperson-entries.adoc for the current progress
    4. Next steps: Benn and Keith to discuss what a profile document will look like based on the attribute dictionary
    5. What will be the process to keep this in sync with the main schema? For most people, the authoritative schema docs will be what the Schema Board publishes. These other documents are behind the scenes for that work. The attribute dictionary can be the translation layer between things like a schema and a SCIM extension.
  5. Review of Work Item Portfolio
    1. Work Item 5 - There are still concerns about whether the note proposed is appropriate regarding the use of SubjectID.
    2. Work Item 6 - This will be resolved by the other work to split the protocol-specific information from the core spec. 
    3. Heather and Benn to discuss whether to continue to use this method for tracking work items or shift to using GitHub issues
  6. Releasing a new version of the eduPerson schema
    1. call ran out of time; will discuss in June