Attendees

• Miroslav Milinović
• David St Pierre Bantz
• Alan Buxey
• Heather Flanagan
• Benjamin Oshrin

Regrets

• Terry Smith
• Keith Hazelton
• Mario Reale

Agenda

1. Agenda bash
2. Review of Action Items
3. Updating the Community
4. Sub-committee Status
   1. eduPersonAffiliation
   2. voPerson
5. Steps to manage proposed entity categories
   1. Authentication Only
   2. Anonymous Authorization
   3. Pseudonymous Authorization
6. Request for new SCHAC attribute - schacLocalReportingCode
7. AOB

Notes

• Review of Action Items
• Updating the Community
  • Heather will be sending a 1H 2020 update to REFEDS about the work of the schema board; will send to the schema board for review
    • Make sure to include what we expect to do with semantic versioning. The next release will therefore be $foo.
• Sub-committee Status
  • eduPersonAffiliation
    • Working on defining the use cases that led to the group forming, determining what is more appropriately an entitlement, and what is an affiliation. See Affiliation and Entitlements Use Cases.
  • voPerson
    • Some progress since the last call in getting to the 2.0 final draft. No ETA.
• Steps to manage proposed entity categories
  • Authentication Only
  • Anonymous Authorization
  • Pseudonymous Authorization
  • Why should this be in the Schema Board? Logic is that since it's about attributes and attribute release, that leads to schema, which leads to the Schema Board.

  • Proposal for incorporating and kicking off a consultation period

    • Set up two webinars for the community to talk through the entity categories

      • What they are intended for

      • What they don’t do

      • Schedule for June 30 @ 8am PT and 8pm PT, start 8-week consultation period (July 1 - August 26)

• Request for new SCHAC attribute - schacLocalReportingCode
  • How can this apply in a university setting? Can this be maintained in a large university setting? Can it instead be calculated from other attributes? Will this become neglected in the same way that Entitlement is? With a multi-valued attribute, how will the SP know which one to use? How will the IdP know which one to send? We need a lot more information in how this could work, and how IdPs could actually support this internally given the changes within an institution. If we see this kind of attribute constantly become invalid, then the overall reputation and management of the IdP becomes an issue. Let's keep talking about this, but figure out how to make it something other than a grab bag of poorly maintained data.
    • Heather Flanaganto send a doodle poll to the list for a call to discuss a local reporting code attribute with interested parties
• AOB