...
- Define interop format for backup
- Not everything can be backed up. Some credentials may only be usable in the device/wallet it was issued to
- Define a backup service protocol
Error Handling and Reporting
- We don't currently have enough published community knowledge to organize the conversation very well.
- Errors need to be communicated at both a technical level and a human level
- Context for errors is important - don't imply that background errors relate to a different foreground operation.
- ToDo: Need a focused convention of agent developers to share the errors they handle and how, with a goal of capturing community knowledge and best practices.
Original Topics List
- 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
- Other User Experience (UX) (4)
- UX of Invitations
- Exposing errors / details to users & power users (404 and 503 like errors)
- Unsupported DID Method
- Glossary - naming conventions - how to hide technicalities in front of user
- QR / Invitations (1)
- 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