Closed awoie closed 1 year ago
Would the following make sense?
{
"@context": [
"https://www.w3.org/2018/credentials/v1"
],
"type": “Verifiable”Presentation,
"verifiableCredential": [
“b64-(sd-jwt-combined-format-4-persenation)-#1”,
“b64-(sd-jwt-combined-format-4-persenation)-#2”
]
}
After thinking about this a bit more, I'd say that this doesn't have to be solved in the VC-SD-JWT spec. It should be solved at the protocol level, e.g., OpenID4VP where the vp_token
would contain an array of VP-SD-JWTs.
+1
No need for another envelope. On 19. May 2023 at 11:26 +0200, Oliver Terbu @.***>, wrote:
After thinking about this a bit more, I'd say that this doesn't have to be solved in the VC-SD-JWT spec. It should be solved at the protocol level, e.g., OpenID4VP where the vp_token would contain an array of VP-SD-JWTs. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>
As discussed in our call, this should not be handled by our specification.
As discussed on the editor's call (5/23), closing this issue since no longer needed.
We should describe how multiple VCs and VPs can be combined in one VP.