## Agenda
👉 _Add items that you would like to cover on the call_ 👈
- Don't forget to join the community in
- 📄https://hackmd.io/@oidf-wg-authzen
- 💬[OpenID Slack Channel for AuthZEN](https://oidf.slack.com/archives/C0630873JGK)
- 📧[Mailing list](https://lists.openid.net/mailman/listinfo/openid-specs-authzen)
- 👩‍💻[Github Repo](https://github.com/openid/authzen)
- Atul to provide overview of existing [AuthZ spec in github](https://github.com/openid/authzen/blob/main/api/authorization-api-1_0.md). [See in HackMD](https://hackmd.io/@oidf-wg-authzen/authzAPI)
- [Presentation Draft](https://docs.google.com/presentation/d/1bWnazk6D54efbO08FUpwOyeLyrxz04hoSx2XwauyID8/edit?usp=sharing)
- What is the strategy for an interop?
- Goal: May 2024 at RSA
- Is there still such a thing as a PEP SDK?
- Should we avoid mentioning the word SDK?
- Review comments from @alexbabeanu, @xmlgrrl , and others on [Authorization Design Patterns](/H2a8WW2vTjOc5xy4Tm85oQ)
- Discuss plans for EIC (David) and Identiverse
## Attendees
👉 _Write your name down if you plan to attend_. 👈
- @davidbrossard
- @gerryatstrata
- @xmlgrrl
- Omri Gazitt @omrig
- Rifaat Shekh-Yusef
- Elie Azerad
- Jason Garbis
- David Hyland
- Atul Tulshibagwale
- @alexbabeanu
- Jeff Broberg
- Martin Besozzi @embesozzi
- Roland Baum
- Bjorn Hjelm
- George Fletcher
- Dani Katzman

## Notes
- Intros from David Hyland and Jason Garbis
- Housekeeping items/links
- Atul provides an overview of the spec document and some of the reasoning behind the concepts and approaches
- Alex/Eve discuss design patterns document, with the idea that this content could help inform discussions of the APIs
- Process for edits: If you add content, highlight the new text with a comment
- Suggesting changes to existing text: highlight the text and put new text in a comment
- Review: We will review new comments on weekly calls
- Long term storage: Once the document reaches its final stages with few edits, it will be move to GitHub
- Jason: What is the objective of this document? Eve: This could be an interim output to accelerate our learnings and help to evangelize the market place. Treat them as living documents and invite comment.
- George: One option may be to turn it into an OIDF white paper (non-normative). Perhaps we push OIDF to support more types of documents.
- Rifaat - more familiar with IETF process, there are definite categories of documents
- Lots of conversation and agreement to expand content that addresses the OAuth/Scope model. OAuth RAR model will also be important to consider here.

## Action items
- Eve still working on terminology document
- George to approach OIDF about supporting additional document types