Remember the Hyperledger Code of Conduct
...
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.
...
- Timo Glastra - Animo Solutions (timo@animo.id)
- Ariel Gentile - 2060.io (a@2060.io)
- Warren Gallagher (AffinitiQuest) <warren@affinitiquest.io>
- Zdravko Iliev - Vereign AG (zdravko.iliev@vereign.com)
Resources
- Hyperledger Discord: https://discord.gg/hyperledger (#aries-javascript and #aries-bifold)
- Aries JavaScript Docs: https://aries.js.org/
- Repositories:
- Aries Framework JavaScript: https://github.com/hyperledger/aries-framework-javascript
- Aries Framework JavaScript Extension: https://github.com/hyperledger/aries-framework-javascript-ext
- Aries Mobile Agent React Native: https://github.com/hyperledger/aries-mobile-agent-react-native
...
- Aries Bifold (Aries Bifold User Group Meetings)
- Meetings suspended until September
- Aries Call 2023-0708-19 02 Aries Working Group Call
- Discussion on peer did migration
- Use Discover Features to know if the other party supports did:peer:3
- Discussion on peer did migration
...
- Record the meeting
- Unqualified DID migration and DID:peer:3 support
- Aries RFC proposal: https://github.com/hyperledger/aries-rfcs/pull/793
- Some updates to be reviewed for transformation script https://github.com/TimoGlastra/legacy-did-transformation/pull/4
- A few notes for AFJ implementation: https://hackmd.io/sz0xbL9MTxeB3qDht3ClrQ
- See hackmd for notes from the WG Call
- JFF Plugfest 3: support for DIDComm V2/WACI-Pex? OIDC4VP?
- Probably no DIDComm tests for Plugfest 3
- Most parties using DIDComm v2 (makes sense to use that) → so we need DIDComm v2
- Issue Credential v3, Present Proof v3
- PEX attachment format for present proof
- Implementation of OpenID4VP for AFJ: https://github.com/animo/paradym-wallet/tree/main/packages/openid4vc-client/src/presentations
- DIDComm v2
- Discussion: https://github.com/hyperledger/aries-framework-javascript/discussions/1539
- Should be able to create oob v1.1 message and receive didcomm v2 message (using
accepthttps://github.com/hyperledger/aries-rfcs/blob/main/features/0044-didcomm-file-and-mime-types/README.md#defined-profiles) - OOB v2: https://identity.foundation/didcomm-messaging/spec/v2.0/#out-of-band-messages
- Look at open issues / PRs
- 0.5.0 release
- Deprecating the Indy SDK
- deprecate indy-sdk in 0.6.0?
- 0.5 will be last version with indy-sdk support, or should we already deprecate/remove it in 0.5?
- add deprecation warning to the framework already?
- need to coordinate with stephen
Meeting Notes
Recording / Slides
...
Future topics
Future Topics:
...