Aries agent export data format?

[swcurran]

An issue was raised in the ACA-Py repo about the need to track with a credential the ID of the connection that was used in issuing the credential. While an ACA-Py specific solution could be created, it raises the more general question about what data should be stored about credentials and connections so that the data is portable -- can be exported from one Aries instance and imported into another. As we start to implement Aries-level storage, we should discuss and document what expectations should be on all implementations and what is left to a specific implementation.

Another way of looking at this: what is the export data format for Aries agent storage?

[kdenhartog]

Not sure we'll be able to comply (I haven't even investigated), but I think we should take some inspiration at the least from this project. https://datatransferproject.dev/

If we can conform to what they're doing that would be pretty amazing I would think.

[dhh1128]

The Indy wallet already documents a streamable, encrypted export format for all wallets (and a corresponding import operation). Do we have any reason not to use it? I think it would adapt easily to wallets or KMSes that use other internal data formats...

[jakubkoci]

I see a similar problem with the basic message and from, to attributes. It's not part of a message in the basic message protocol (for a good reason not bloating up message with too much information), but I would like to keep and export/import such information anyway to be portable across different chat application implementations. It was discussed a little bit in #416.

[TelegramSam]

Discussed in Aries WG Call 2020-05-27. Notes: https://hackmd.io/NbQthk4xTACvBSEclxTShA