Evaluate new Sovrin TAA feature and how to handle that in ACA-Py

[swcurran]

The new Transaction Author Agreement (TAA) will soon be added to the Sovrin ledger (MainNet, BuilderNet and StagingNet) and support will need to be added to ACA-Py to support it for Aries instances accessing and writing to those networks.

Please review this new feature and evaluate how we can add support for the TAA in ACA-Py. This is a good starting article, and there links at the bottom of the article to further technical details.

https://sovrin.org/preparing-for-the-sovrin-transaction-author-agreement/

[vinomaster]

@swcurran You may want to review this draft diagram that has been submitted as part of an update to Sovrin Glossary Appendix E. It has been used for discussions with respect to contractual instruments for GDPR/CCPA/other-regulation compliance.

The right side of the diagram is pertinent to this issue. Based on the URL above there may not be a change to the process but this may help understand the contractual instruments at play.

[andrewwhitehead]

I would suggest adding this to the aca-py provision command, probably as an automatic part of aca-py provision ledger (which doesn't exist yet). It would download the AML and TAA if they exist, and assuming session_agreement is an option then it could present the terms and ask for user acceptance.

Each acceptance record would be stored in non-secrets and the latest one would be submitted with each request. Some formatting could probably also be applied by a markdown-to-terminal formatter (pygments seems to support that).

We would also want to add the ability to define an AML and TAA to von-network for testing.

[andrewwhitehead]

Resolved via #127