Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Summary:

<planned topics>

Aries / Indy SDK Split Plan

Aries Meeting Schedule / Format

Note: This call is Recorded. Recordings posted at the bottom of the page.

Date

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.

Hyperledger Code of Conduct

Attendees

NameOrganizationEmail
Sovrin Foundationdaniel.bluhm@sovrin.org
Cloud Compass Computing/BC Govswcurran@cloudcompass.ca
Paul Knowles Dativapa



































































Announcements

Agenda

ItemWhoNotes
Welcome / IntroductionsDaniel Bluhm will make sure the call is recorded in Sam's absence
Related Meetings Review

Ursa

Indy Semantics

Brief announcement about Agents and Hubs paperSee https://docs.google.com/document/d/1shacUcB9KcdKPmt2yAZkdOKsnsgDBXBewkOomlp7V2c/edit
Architecture of Indy/Aries SDK Split
Aries Meeting Schedule / FormatStarting an Asia-Pacific friendly meeting and / or an America-Europe friendly meeting (off-week from Indy Working Group, or taking the place of the Indy SDK Working Group)?






Open Discussion


Next Week

  • Daniel Hardman  - Converting the DIDcomm protocols to use the did:peer method.

Future Topics

Action items

Call Recording

  File Modified



  • No labels