# WG Meeting: 2022-10-04
## Agenda
- Naming (again) [Tim]
- PRs and Issues

## Attendees
- Shayne Miel (Cisco)
- Tim Cappalli (Microsoft)
- Nacy Cam-Winget (Cisco)
- Jason Garbis (AppGate)
- Andrii Deinega
- Asad Ali (Thales)
- Gail Hodges (OIDF)
- Steve Venema (ForgeRock)
- Atul (SGNL)
- Edmund Jay (OIDF)

## Notes
### Naming
- Tim: SSE is now a Gartner super term. People still call it CAEP anyway. Should we rename the SSE core spec to CAEP, keep RISC name as is and the CAEP list of events gets renamed.
- Nancy: In general, like the idea
- Steve: Power is beyond just CAEP and RISC
- Gail: Agree
- Nancy: Shouldn't concede to CAEP
- Asad: Agree, fight CAEP internally too. What about SES?
- Tim: Competing with Amazon service name
- Atul: How about something like webhooks?
- Shane: How about putting OI (for OpenID) in front of it
- Jason: CAEP does seem to work for the old umbrella term
- Steve: Gartner's CARTA term
- Nancy: OIDSS (OpenID Shared Signals)
- Shayne: Secure Shared Signals (SSS)
- Atul: Shared Signals Framework? (SSF)
- Tim: would we have to redo any paperwork?
- Jason: Potential confusion with OpenSSF
- {Tim}: Send out email to list

### PR Comments (PR # 31)
- Atul: example of a custom namespace is there deliberately
- Tim: as long as there is another pre-defined example
- Atul: Case sensitive or not?
- Tim: OpenID Connect has explicit statements for each claim/attribute
- Shayne: pull case sensitivity into its own topic

### PR Comment (PR # 9)
- Shayne: polling URL in delivery_methods_supported metadata? Think it is a good idea but split into a separate issue.
- Atul: would it work without that?
- Shayne: you would get it in the stream config metadata but not the transmitter metadata

## Action Items