[Openid-specs-ab] Issue #1369: Make requesting verifiable presentations extensible (openid/connect)

[David Chadwick]

New issue 1369: Make requesting verifiable presentations extensible
https://bitbucket.org/openid/connect/issues/1369/make-requesting-verifiable-presentations

David Chadwick:

The current specification of verifiable presentation selection \(section 8   \) is fixed to one edition of the presentation exchange specification \(v1\) which makes the protocol inflexible, fixed in time, and incapable of adapting to new ways of requesting verifiable presentations. For example, v2 of PE is currently being specified, as is a simple profile of PE but neither of these are catered for.

The proposal is to replace the current fixed format with a type and value, where the type defines the contents of the value. The various types can be specified in the standard or in an IANA registry.

This means replacing the following data structure from the first non-normative example from section 8

\{  
"id\_token": \{  
"acr": null,  
"verifiable\_presentations": \{  
"presentation\_definition": \{  
"input\_descriptors": \[  
\{  
"schema": \[  
\{  
"uri":  
"[https://www.w3.org/2018/credentials/examples/v1/IDCardCredential"](https://www.w3.org/2018/credentials/examples/v1/IDCardCredential%22)  
\}  
\]  
\}  
\]  
\}  
\}  
\}  
\}

‌

with

\{  
"id\_token": \{  
"acr": null,  
"verifiable\_presentations": \{  
"type": "<choice between pev1, pev2, pescp, any other registered type. pev1 is chosen here>",  
"value": \{  
"presentation\_definition": \{  
"input\_descriptors": \[\{  
"schema": \[\{  
"uri": "[https://www.w3.org/2018/credentials/examples/v1/IDCardCredential"](https://www.w3.org/2018/credentials/examples/v1/IDCardCredential%22)  
\}\]  
\}\]  
\}  
\}  
\}  
\}  
\}

Responsible: David Chadwick