Skip to content

rfc: odi and poa in vp - #21

Open
robdefeo wants to merge 2 commits into
mainfrom
vp-presentation
Open

rfc: odi and poa in vp#21
robdefeo wants to merge 2 commits into
mainfrom
vp-presentation

Conversation

@robdefeo

@robdefeo robdefeo commented Dec 12, 2024

Copy link
Copy Markdown
Collaborator

I tried to think a little more widely about how to solve the problem of including an ODI with a POA. This is one a those approaches along with #20.

This PR proposes to include both the ODI and POA when presenting credentials. This matches well with the pattern of authorising and action based on multiple credentials.

If we choose to go down this root, we can evaluate if we give different names to the linked/included ODI which would make clearer where to look for the proof and allow relying parties to choose what method(s) they would accept for ODI.

"credentialSchema": {
"id": "https://api-pilot.ebsi.eu/trusted-schemas-registry/v3/schemas/z2sbTT23X2zfsdMCPFMC7GiUwyHE91Lg9BpeEA5uqtT9s",
"type": "FullJsonSchemaValidator2021"
"type": ["VerifiablePresentation"],

@robdefeo robdefeo Dec 12, 2024

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could include another type in this array ["VerifiablePresentation", "IncludedODI"] or ["VerifiablePresentation", "LinkedODI"] name is not good but indicates to the validator to look for the ODI in the VP or for a linked ODI. This will also remove the issue of where to look for the ODI as the the POA or the presentation indicates what ODI to use.

"path": [
"$.type"
],
"optional": true,

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This indicates that this credential is optional.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant