Date: Fri, 29 Mar 2024 14:14:16 +0000 (UTC)
Message-ID: <376555834.57.1711721656060@wiki-prod.refeds.org>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_56_1026233769.1711721656059"
------=_Part_56_1026233769.1711721656059
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Call-in Coordinates
Heather Flanagan is inviting you to a scheduled Zoom meeting.
Topic: Schema Editorial Board - February 2020
Time: Feb 7, 2020 11:00 AM Pacific Time (US and Canada)
Join Zoom Meeting
https:=
//zoom.us/j/979687605?pwd=3DakZaL1dCUVp2SXdnMFhBdHdHakVIZz09
Meeting ID: 979 687 605
Password: 818727
One tap mobile
+16699006833,,979687605# US (San Jose)
+19292056099,,979687605# US (New York)
Dial by your location
+1 669 900 6833 US (San Jose)
+1 929 205 6099 US (New York)
Meeting ID: 979 687 605
Find your local number: https://zoom.us/u/aRjU5ChSJ
Join by Skype for Business
https://zoom.us/skype/979687605<=
/a>
Expect=
ed Attendees
Apologies
Agenda
- Open Actions
- Administrivia
- Board nominations
- David Banz (U. Alaska) (2019-2020)=
span>
- Scott Koranda (LIGO/SCG) (2019-2020)=
- Miro Milinovic (SRCE) (2019-2020)
- Catarina Ribeiro (University of Porto) (2019-2020)
- Status of schema
- eduCourse
- voPerson
- Next steps for eduPerson
- AOB
Notes
- Open Actions
- For the LDIF files, see =
eduPerson LDIF Files - still need additional pointers to other LDIF fil=
es as appropriate. Board should send those to Keith or update that page.
- For 6338bis, see AOB
- SimpleSAMLphp - are all the tools ready to deal with the SAML identifie=
rs (Subject-ID and Pairwise-ID)? yes, this is fine, no issue
- Administrivia
- Board nominations - nominations will open in March; the seats below wil=
l move to 2-year terms. We need at least two nominations, no more than four=
.
- David Banz (U. Alaska) (2019-2020)=
span>
- Scott Koranda (LIGO/SCG) (2019-2020)=
- Miro Milinovic (SRCE) (2019-2020)
- Catarina Ribeiro (University of Porto) (2019-2020)
- Benjamin=
Oshrinwill post a suggestion to the board list on how to handle the si=
tuation of receiving more nominations than seats open for the board<=
/li>
- Status of schema
- eduCourse
- eduCourse was designed with an eye towards what IMS Global was specifyi=
ng for course rosters. The current new standard is OneRoster 1.1 (see Keith=
's comment). Someone needs to review that document to see if the informatio=
n it contains what is needed. We may need to profile what's in there.
- Keith Ha=
zeltonto review the OneRoster 1.1 spec and make a recommendation to the=
board re: whether we need to create a SAML profile for the material
- Since IMS Global is currently working on EduAPI, it is probab=
ly premature to spend a lot of time on IMS's OneRoster 1.1 specification: <=
a class=3D"external-link" href=3D"http://www.imsglobal.org/oneroster-v11-fi=
nal-specification" rel=3D"nofollow">http://www.imsglobal.org/oneroster-v11-=
final-specification ;
- voPerson
- The subcommittee is trying to work out the SAML representation of the v=
oPerson attributes.
- v2 of the schema is having some challenges - some new information will =
be added (see https://github.com/voperson/voperson/is=
sues). Blocked on getting O=
IDs assigned. (Does this need =
a registry update as well?) Explore the idea of having a Schema Board branc=
h so we can add more schema as needed; leave SCHAC as grandfathered in with=
its own top-level domain
- Next steps for eduPerson
- decoupling the protocols are a likely place to start, and may end up su=
ggesting other changes to the spec.
- Are we talking about stripping out the LDIF examples? Having the expect=
ed value styles is helpful, but it does influence specific protocols (e.g.,=
LDAP). Alternatively, we could dilute the protocol specificity by adding m=
ore protocol examples. What would be most useful to the community? Given we=
're still waiting for the OIDC Federation, we're not sure exactly what will=
be most useful. Consensus is leaning towards having eduPerson as a complet=
e with multiple examples and changing the markup to make it easier to extra=
ct the examples into a protocol appropriate set. Discuss on the next call; =
start going through the spec to determine where we could make changes to be=
more clear re: the protocols.
- What about focusing on expanding attribute values? Check for some possi=
ble notes from Internet2's Tech Ex 2019. Affiliations, in particular, could use pot=
ential expansion (though maybe groups are a better way to handle the many v=
ariances of affiliation possibilities). This is something we should explore=
with the community to figure out what they need us to do. Some federations=
have done this on a federation-specific level. Let's reach out and figure =
out what they are doing and why. Discuss on the next call how to phrase the=
questions and how to reach out.
- Let's also discuss adding AcademicID to a schema (the way we have ORCID=
). Maybe this belongs in SCHAC?
- AOB
- Updating RFC 6338 - should we broadly replace "TERENA" with "GEANT"? Pe=
rhaps change the intro to include "Management of the schema has been transi=
tioned to REFEDS, an entity supported via secretarial services by GEANT."=
li>
------=_Part_56_1026233769.1711721656059--