# Meeting Notes 2024-06-11

## Attendees
👉 Add your names here
@gerryatstrata
@omri
@davidbrossard
@rolandbaum
Alex Olivier
Jahan Moreh
Steve Venema
George Fletcher
Angelo Moura
Mickey Martin
Wade Ellery
Don Coltrain
(Atul)
Victor Lu

## Agenda
- New meeting schedule starting next week
- Every other week the call will be at 3pm PT / midnight CET / 8am AEST
- to check on video recordings with Mike L.

- Implementer's Draft: details and process

- Boxcar spec status

- AOB (all other business)

## Notes
- EIC interop
- Went through the same use cases as at Identiverse
- There were some additional people in the room
- David and Allan did a video recording with Martin
- Person from Schneider Electric had an interesting use case presentation
- There was some discussion on terminology: decision vs. allowed

- Implementer's Draft
- It is a "core decision" to move to an Implementer's Draft, so there is a process to follow
- AT: the spec has to be voted on by a quorum of the whole OIDF and there are review periods before that vote.
- Start within the working group with a vote
- GF: should have clear goals for the draft, should be constructed so that additional functions that can be added easily
- AT: make the working draft more visible
- OG: starting cleaning up original draft of spec, but paused
- OG: meta conversation on sequence of events: stick with getting the MVP implementer's draft completed and published. Summary: do we want to stay with an incremental approach, rather than waiting on the other profiles?
- GF: Implementer's draft locks in IP. You won't get customers implementing this in production, so there may not be a drive to publish it.
- AT: review process becomes simpler if it includes the items that are most familiar. Don't have an opinion whether to have ID now
- SV: External optics can show the world that we are moving forward
- OG: Now that we have 12 implementations (mostly with proxies), we would feel more comfortable implementing in actual product with an ID. It puts more friction on putting changes (maybe not meaningful semantically).
- DB: In favor of getting the simple draft out sooner than later
- AT: No PEP implementations so far, which is the kind of implementation demand he was referring to
- DB: Probably need an ID before going to PEPs for support
- OG: there is rough consensus to move forward with the basic ID that does not have the results of SG1 or SG2
- Next steps
- Complete the cleanup/surgery on original draft from Atul (Omri)
- Coordinate the OIDF process (Gerry)