You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
upon closer investigation, it turns out we don't actually need transformers for VCs and VPs, because we also have to be able to work with JWTs.
In addition, when using JSON-LD, all verification and creation (of VPs) is done by the CryptoSuite, and that is done completely self-contained and transparently.
What we will eventually need is something like an "extractor", that expands the VP/VC and extracts information out of it, to populate the model class (VerifiableCredential|Presentation).
Feature Request
This issue is intended as preparatory work for the IATP implementations, it calls for the implementation of the following model classes:
VerifiableCredential
VerifiablePresentation
these go into an SPI module together with the interfaces.
Other objects we need beforehand include JSON-LD transformers, which should go in a separate module.
Which Areas Would Be Affected?
iam
Why Is the Feature Desired?
IATP adoption
Solution Proposal
If possible, provide a (brief!) solution proposal.
The text was updated successfully, but these errors were encountered: