...
- Timo Glastra (Animo Solutions) <timo@animo.id>
- Jakub Koci (Absa) <jakub.koci@gmail.com>
Status updates
- Issue credential protocol
- Issue credential merged
- Still needed:
- Start with credential proposal
- advanced threading
- validate credential preview against actual credential
- Present proof protocol
- AFJ ↔ React Native
- Started work on `@types/indy-sdk`
...
- Record the meeting
- Present Proof Progress
- How to handle auto accept?
- Framework API consistency
- https://github.com/hyperledger/aries-framework-javascript/issues/115
- Method arguments
- Method return types
- Only storing message content (CredentialPreview, PresentationPreview, CredOffer) instead of complete didcomm message?
- unnessacary base64 encoding / decoding
- IDs vs Objects
- find vs get
- Error vs non-error
- https://github.com/hyperledger/aries-framework-javascript/issues/78
- Multiple mediator support
- Forward handling incorrect?
- Use record state values that match RFC
- Easy for comparison, why not?
Meeting Notes
- Forward handling seems incorrect
- Verify with developer from other framework
- Multiple mediator support is a long-term feature and should be implemented in phases:
- Use only one mediator for an agent, but allow to change it after the agent initialization.
- Define and implement behavior for export/import agent data.
- Allow having more than one mediator for an agent. It will probably introduce some relation between a mediator connection and other connections stored by an agent.
Future topics
- Use record state values that match RFC
- Easy for comparison, why not?
- Only storing message content (CredentialPreview, PresentationPreview, CredOffer) instead of complete didcomm message?
- unnessacary base64 encoding / decoding
- IDs vs Objects
- find vs get
- Error vs non-error
- https://github.com/hyperledger/aries-framework-javascript/issues/78
- Present Proof Progress
- How to handle auto accept?
- State machines