Versions Compared

Old Version 5

changes.mady.by.user Steve McCown

Saved on

compared with

New Version 6

changes.mady.by.user Sam Curren

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary:

Excerpt
  • Aries Mobile Agent Summit


...

(7AM Los Angeles, 10AM New York, 3PM London, 4PM CET, 18H Moscow)

Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit 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.

...


Welcome / Introductions

...

  • Aries Mobile Agent Summit
  • Prioritize topics: 
    • RFC 496 - Transition to OOB and DID Exchange
    • HTTP Mobile exemptions
    • UX of Invitations
    • SVG Cred Display
    • Mobile Infrastructure (2)
      • Mobile Verifiers
      • Device Recovery (Backup/Restore/Sync/Rotation to new keys)
      • Secure Element usage
      • SDK / Embedding Agents into existing Mobile Apps
    • Credential UX (3)
      • SVG Cred Display
      • Auto-approval of presentation requests (e.g.: trusted verifier, trusted preset, etc ...)
      • Credential Theming (e.g. Icon, Colors, Description)
      • Revocation implications for Mobile
      • Consequences of Machine Readable Governance on UX
      Embedding Agents into existing Mobile Apps
    • Other User Experience (UX) (4)Mobile Verifiers
      • UX of Invitations
      • Exposing errors / details to users & power users (404 and 503 like errors)
        • Unsupported DID Method
    • Revocation implications for Mobile
      • Glossary - naming conventions - how to hide technicalities in front of user
    • QR / Invitations (1)Device Recovery (Backup/Restore/Sync/Rotation to new keys)
      • How are we really going to do deep-links?
    • Secure Element usage
      • RFC 496 - Transition to OOB and DID Exchange
      • RFC 700 - sending out-of-band as query parameters and enable redirect back.
      • HTTP Mobile exemptions
    • Security
      • DID method specific
      • Immutability of schema and JSON-LD security issues
      • Biometrics/PIN unlock (overlap with UX)
    • Protocols
      • DIF Credential Manifest attachment (followup from Issue Credential v2 json-ld attachment in AIPv2).
      • DIDComm v2 (and related)
        • DIDComm v2
        • WACI
  • Future sessions - schedule, format, and topics
      First topics
      • TBD2 hour meetings weekly
      • task forces - publish agendas, focused on different issues
      • group agenda topics
        • protocol format
        • mobile infrastructure
          • backup
          • secure elements
        • ux topics
          • display creds
          • standardized experiences
      • leverage wiki on topics, discussions on github?
    • Tasks
      • Select regular 2 hour meeting block (sam)
      • wiki / etc infrastructure (sam)

    Other Business

    Future Topics

    ...