...
Does aries wallet really needs lock/unlock feature?
→ Open question : Still investigating- Should we provide password in each api call as given in specification?
→ to be decided during design discussion
VC plugin:
VC plugin adds verifiable credential features to the wallet. By default aries-framework-go verifiable command features will be used for creating and verifying credentials/presentations.
The new interface 'presentationSubmission' can be used to submit presentation definitions to the wallet and to get presentation submission as response.
...
- Why we need a new query interface for querying VCs using presentation exchange? Why can't we use existing 'query' interface from store plugin?
→ 'add' interface function from store plugin can be used to add any data model. Modifying 'query' interface to support presentation exchange may increase the complexity for non-VC data model users.
...
Key plugin provides 2 interfaces : verifyRaw & signRaw. Framework will use aries kms api provider for these wallet features.
This plugins can be injected to customize the wallet to use other kms implementations like webkms.
API Dependencies:
- KMS: use key plugin for cryptographic operations, if not provided then fallback to aries-framework-go kms api.
Store plugin:
Store plugins adds features for maintaining wallet content stores. Framework will use aries storage provider for these wallet features.
This plugin can be injected to customize the wallet to use custom storage providers like encrypted data vaults.
- add: adds data models to wallet contents
- remove: takes id of the content to be removed from wallet contents.
- query: query wallet content based on search criteria. (TODO: search criteria to be decided)
Questions:
- As per specifications for query interface, how can we use map and reduce functional arguments effectively for REST bindings?
→ we can use functional arguments in JS bindings & SDK bindings. But REST & mobile bindings it needs to be modified to support some sort of generic query feature.
DID plugin:
Unlike other plugins, DID plugin functions won't be part of exposed wallet APIs, since aries-framework-go already has vdri interfaces exposed.
This plugin can only be used to inject custom DID features like using custom did methods for wallet operations.
Questions:
- Why can't we get rid of this plugin and use ask client's to use their customized aries vdri.
→ to be decided during design discussion