Usage of a query language with OpenID Connect/SIOP

[Kristina Yasuda]

To account for cases when mechanisms to specify in more detail requested claims such as query language or OpenID Connect for Identity Assurance are being used, suggest merging following text to a draft as a non-normative note:"RP could use mechanisms to specify in more detail requested claims such as query language or OpenID Connect for Identity Assurance. In such cases, only one id_token should be returned and requested parameters should be included inside the id_token, and additional metadata should be included in registration parameter passed in the request."

May be this should be covered in query language and OIDC for ida specs, but thought worth suggesting.

Reference links:

https://openid.net/specs/openid-connect-4-identity-assurance-1_0-ID2.html#name-self-issued-openid-connect-

https://identity.foundation/presentation-exchange/

[Tom Jones]

Interesting idea. I tried to get a query language into the federation spec, but the R&E guys didn’t want to hear it.

[Kristina Yasuda]

I am ok to close this as the issue is now being addressed in OpenID Connect for Verifiable Presentations draft and a more in-depth discussion took place in issue #1230.