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.

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

Decide on supported feature set for Presentation Exchange #16

Closed
mistermoe opened this issue Nov 9, 2023 · 7 comments · Fixed by #96
Closed

Decide on supported feature set for Presentation Exchange #16

mistermoe opened this issue Nov 9, 2023 · 7 comments · Fixed by #96
Assignees
Labels
blocker needs a decision

Comments

@mistermoe
Copy link
Contributor

No description provided.

@decentralgabe
Copy link
Member

I believe we should support PEv2, with the following features:

  • Predicates (e.g. be able to filter that a field is of a certain regex, length, etc.)
  • Relational Constraints (e.g. require a credential to be self-issued, or not)
  • Credential Status (e.g. be able to require that a credential is of a certain status)

The features I've excluded: submission requirements, JSON-LD framing, retention. Everything else should be according to the spec.

@mahoekst
Copy link

relational contraints is also give me a VC from this specific issuer correct?

@decentralgabe
Copy link
Member

@mahoekst that would be predicates

@mistermoe
Copy link
Contributor Author

cc: @nitro-neal

@mahoekst
Copy link

I would recommend the minimum to support give me a VC of type X from issuer Y where both are optional.

@frankhinek frankhinek moved this to Todo in SDK Development Dec 19, 2023
@mistermoe
Copy link
Contributor Author

before closing this issue, we probably want to document this feature set in the README. @decentralgabe can you tackle that if possible?

@decentralgabe
Copy link
Member

#96

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker needs a decision
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants