[Openid-specs-ab] Issue #1555: Use of scope values to request credential issuance and presentation (openid/connect)

[tlodderstedt]

New issue 1555: Use of scope values to request credential issuance and presentation
https://bitbucket.org/openid/connect/issues/1555/use-of-scope-values-to-request-credential

Torsten Lodderstedt:

The current texts/proposals derive a credential to be issued or to be presented from a scope value, e.g. \`openid\_credential:healthCard\`. That has turned out to result in complex logic \(PR #186\) and might cause issues with the way scope are implemented in existing products and potentially name clashes. 

I suggest to change the approach as follows: deployments, ecosystems, or standards can define scope values that map to requests for credential issuance or credential presentation, respectively. The spec does not take a stance on the structure of those scope values and how the definition of the mapping is done. For example, that can be done in normative text \(like OpenID Connect does for default claims sets\) or use some kind of machine readable definition \(e.g. a scope value is defined by an equivalent presentation\_definition object\).

Responsible: Torsten Lodderstedt