2021-10-07 Aries Framework JS Meeting notes

Planned Topics:

• AFJ Mediation
• Issues and PRs
• AMA

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) <timo@animo.id>
• James Ebert  (Indicio) <james.ebert@indicio.tech>

Status updates

• Aries Bifold (Aries Bifold User Group Meetings)
• Aries Call
• Animo has won eSSIF Lab Grant to build Aries Mobile SDK - 
  • AIP 2.0
  • BBS+, JSON-LD
  • Shared components (Aries Askar, Indy CredX, Indy VDR)

Agenda

• Record the meeting
• Welcome & Introductions
• AFJ Mediation Architecture
  • 
  • What do we need in AFJ 
    • Pickup protocol 
    • Persistence of messages
    • Database
  • What do we need outside of AFJ
• Issues & PRs
  • feat(core): support image url in invitations
  • feat(core): support multiple indy ledgers
    • Should we prefer a self-certifying DID on a non-production ledger over a non-self-certifying DID on a production ledger?
• Expose wallet API
• AMA

Open Issues

• Finish getting started guides in documentation !!! Stephen & Mostafa
• Add support for receiving and proving revocable indy credentials - James
• Loading ledger asynchronously - reduce the time it takes when receiving a credential 
• How to handle the case without an internet connection
• Add support for RFC 0035: Problem Report - both adopted into other protocols and initiating it as a standalone protocol
• wallet import and export
• Add demos on how to use AFJ as issuer/holder/verifier (like sample mediator)
•  
• Machine-readable governance frameworks
• Action menu
• Add support for verifying revocable indy credentials
• Allow invitations to use public DID 
• Add support for RFC 0434: Out-of-Band - Priority (Connection reuse)
• Add support for RFC 0023: DID Exchange
• Add support for 0453: Issue Credential v2

Meeting Notes

Future topics

• React Native testing
• Support for Deno
  • Although it's not our focus right now, it should be possible in the long term.
  • First, we need to analyze if the following dependencies will work in Deno or what we need to do to make it work:
    • indy-SDK
    • native dependencies (file system, transport protocols like HTTP or WebSockets, ...)
    • other dependencies in package.json
• Monorepo dependencies
  • TypeScript types

Meeting recording: