2023-05-25 Aries Framework JS Meeting notes

Meeting recording

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

Resources

Status updates

Agenda

  • Record the meeting
  • Future of Aries
    • Make sure to read the meeting notes: 2023-05-24 Aries Working Group Call
    • Where did the initiative come from?
      • OWF doesn't make standards, Aries has RFCs
      • RFCs could be moved to DIF
    • We get a lot of things from HL (runners, infrastructure, marketing, workshops)
    • Problem from Hyperledger?
      • assumption = Hyperledger == blockchain
      • misconceptions about Aries
    • OWF = wallet, that doesn't make sense maybe?
    • Purpose / goal of Aries = rooted in blockchain (should goal be revamped?) 
      • Aries is not tied to indy, but not tied to blockchain at all
    • indy-pendence is not well-known, move to OWF could help in making that more clear
    • not as much activity / support?
    • other communities view Aries as AnonCreds, CL, Indy, DIDComm
      • perception is very difficult to change
      • Note from Tim Bloomfield:
    • wallet is the anchor where people start (so open wallet foundation can help)
    • components split up, so not one indy-sdk but separate components. Not connected to just indy.
    • Discussion in Aries repo: https://github.com/hyperledger/aries/discussions/20
  • Future architecture of Aries Framework JavaScript
  • Getting started with AFJ
    • difficult to keep up with versions, alpha vs stable, what to use, and install instructions are sometimes incorrect if in alpha stages
      • documentation not clear on what the release cycle looks like
    • getting the demo working (alice-faber walkthrough)
      • extracting it into a separate repo
      • or as acapy: add it in a docker container
    • lack of documentation/demo (for plugins)
      • bbs+, jsonld, cheqd not documented, also not in the demo
      • openid4vci
    • example repos setup with the latest version and having simple flows implemented
  • Release 0.4.0
    • shared components
    • not wait for revocation
  • DIDComm v2
    • What to do to get it merged?
    • do not call did resolver from wallet, but keep didcomm implemetnation in wallet for now.

Meeting Notes

Recording

https://youtu.be/Xw4Wc6dU8jk

Future topics

Future Topics:


  • It would be good to discuss OCA implementation in AFJ and in Aries Bifold and where should be a boundary between the two in this feature.
  • Wallet API redesign (Ariel Gentile )
  • Cheqd integration (Daev Mithran )
  • AFJ Interop tests not running