Date: Thu, 28 Mar 2024 19:59:16 +0000 (UTC) Message-ID: <940787499.1920.1711655956660@wiki-prod.refeds.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1919_153674951.1711655956657" ------=_Part_1919_153674951.1711655956657 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Heather Flanagan is inviting you to a scheduled Zoom meeting.
Topic: REFEDS Schema Editorial Board - March 2020
Time: Mar 12, 2020 01:00 PM Pacific Time (US and Canada)
Join Zoom Meeting
https:=
//zoom.us/j/502263634?pwd=3DbTRMcXZYMFZqSXZxTzJTWTZVMW0xZz09
Meeting ID: 502 263 634
Password: 070460
One tap mobile
+16699006833,,502263634# US (San Jose)
+19292056099,,502263634# US (New York)
Dial by your location
+1 669 900 6833 US (San Jose)
+1 929 205 6099 US (New York)
Meeting ID: 502 263 634
Find your local number: https://zoom.us/u/aRjU5ChSJ
Join by Skype for Business
https://zoom.us/skype/502263634<=
/a>
Administrivia
Board nominations
One nomination received; we need a minimum of two
Of the people whose term is ending and want to self-nominate, please= do so
Miro is willing to continue but will step aside if we receive more n= ominations than we have slots for
Regarding process to handle too many nominations: Benn to follow up = by next call
Regarding OneRoster - Keith - no update
Regarding voPerson OIDs - Heather has reached out to Nicole (as has = Neils); we expect to hear back on this in a few weeks (need to follow up wi= th Licia about the transfer from Terena to GEANT)
Miro - has been focused on other things; will come back to this
<= /li>Benn - has submitted a proposal (https://wiki.refeds.org/pages/viewpage.action?pageId=3D5062= 6585&src=3Dcontextnavpagetreemode). Benn will review against the ne= eds for voPerson and will consider David=E2=80=99s comments in the text. No= te regarding David=E2=80=99s comment about ldif, we never intended ldif to = be the only example
Status of schema
eduCourse - there was a proposal that we would adopt the eduCourse s= chema; given this has been turned into OneRoster, it=E2=80=99s unclear stil= l if we need to do anything with this. This relates to Keith=E2=80=99s acti= on item re: OneRoster. Also unclear if this is being used in the wild yet. = Will wait until we have more info from Keith.
voPerson - some progress regarding the representation of voPerson at= tributes in SAML. Benn created a branch 2.0 voPerson in GitHub so that prog= ress can be made while other stuff is being sorted out. It will not be fina= l until it=E2=80=99s ready to be managed by REFEDS. See https://github.com/voperson/voperson/tree/draft-2.0.0=
Next steps for eduPerson
Prioritization of Schema Board Work Ite= m Portfolio - currently includes four open items
Work Item 5: Adding a Notes section to the eduPersonUniqueId definit= ion - need to put something in a SAML-specific support page (example: = https://github.com/vop= erson/voperson/blob/draft-2.0.0/aux/voPerson-SAML.md)
Work Item 6: Protocol-specific markup - consider having a master doc= ument that contains everything, with automated extraction for protocol-spec= ific files
Alan Buxey will do some research to = see if there are examples of documentation that will build itself out of a = master file already in existence on GitHub
Work Item 7: Expand Attribute Values - are there one or two affiliat= ions that would solve people=E2=80=99s problems? This needs to go to a work= ing group or out for community discussion to see what actual use cases requ= ire. Example: contractor.
Alan Buxey and Heather Flanagan to create subcommittee charter = on the potential expansion of affiliation values
Work Item 8: AcademicID - there is more than one initiative to creat= e an identifier for campus people; how many of these do we want to support?= They are already going to use the SCHAC PersonalUniqueID. What, if anythin= g, should eduPerson support? If someone approaches us to ask us to support = another thing like an ORCID, how do we support this? How likely is it that = we=E2=80=99re going to see a bunch of requests come in? Perhaps just consid= er this on a case by case basis. If we did support unique identifiers from = given efforts, need to indicate that populating these attributes should be = done according to that efforts=E2=80=99 policies. We can=E2=80=99t protect = this for them.
Consensus here is to deal with this on a case by case basis;= will reconsider if we see a number of requests coming in. = p>
https://github.com/REFEDS/eduper= son/tree/documentation-hf
Terry has reviewed; Alan to review what=E2=80=99s in the branch
<= /li>
AOB
SCIM - came up at the TIIME workshop. Action item was to do a mappin= g of eduPerson into a SCIM schema. Peter Gietz volunteered to run this subc= ommittee.
Heather Flanagan to reach out to Peter = to kick off a SCIM committee
Issues on GitHub (https://github.com/REFEDS/edu= person/issues)
Regarding case, this is already specified in the specification (valu= es can be mixed); some federations, though, assume/require all lower case. = This sounds more like a bug report for the implementation, not the specific= ation.
Regarding orcid, this is a fairly straightforward item - need to dis= cuss, though, on the next call to discuss if/how to update narrative text a= nd whether that requires a new release