Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Should the JSON path for constraints in input descriptor be specified as $.vc.credentialSubject or $.credentialSubject ? #478

Open
georgepadayatti opened this issue May 17, 2024 · 0 comments
Open

Should the JSON path for constraints in input descriptor be specified as $.vc.credentialSubject or $.credentialSubject ? #478

georgepadayatti opened this issue May 17, 2024 · 0 comments

Comments

@georgepadayatti
Copy link

All the examples specified in the specification have both the paths specified. For JWT based credential, should the JSON path evaluation be done inside the vc claim of JWT or should it be applied at the root level ? Is there any recommendation ? Should the holder wallets support both the possibilities ?
@georgepadayatti georgepadayatti changed the title Should it be in $.vc.credentialSubject or $.credentialSubject ? Should the JSON path for constraints in input descriptor be specified as $.vc.credentialSubject or $.credentialSubject ? May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@georgepadayatti