Date | Session | Presenter / Facilitator | Materials / Notes |
---|---|---|---|
| Group Discussion
| Roundtable | Meeting notes |
(The meeting has been moved due to holiday) | Shared services for API development teams: What are the limits and tradeoffs? | Rupert Berk (UWash) | |
| IAM Architecture and Services and API security and capabilities | Matthew Hailstone (BYU) | Recording |
| UW-Madison API program and API Platform rollout | Jon Terrones (University of Wisconsin, Madison) | |
| API Programme at The University of Washington | Rupert Berk | |
| "Quixotic shepherding of API-led connectivity" = The University of Auckland embarked upon an API Programme more than a decade ago, and success has proven elusive --- this discussion outlines the organisational waxing and waning of enthusiasm, capability, and appetite, and paints a picture of necessity-driven hope for an API-centric future. | jeff kennedy (The University of Auckland, New Zealand) | |
| |||
|
https://docs.google.com/document/d/1GdqO381B_mzDYCE1sJq8Gr_HhObhD7qCm36vu9cFzfo/edit?usp=sharing