Date
Remember the Hyperledger Code of Conduct
Anti-Trust Policy:
Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.
Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy . If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.
Attendees
- 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`
Agenda
- 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