You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue of a standard document format for Accord Project was raised by @jeromesimeon.
Details can be found here: Cicero Issue #562
TL;DR
The current CTA compressed archive format assumes the Accord contract is a template that is editable and represents a contract type but is not a contract in and of itself.
The assertion is that there needs to be a file format which contains a contract instance and encapsulates all data, logic and legal artefacts (e.g. signatures) that represents the final, executed agreement.
Sanket and Martin have been doing work on SLC file format.
Have added /signatures folder in file structure and have added state.json to track instantiation, signing and other interactions performed on contract.
Demo to be given at next Tech WG call on 06-Oct-2021
Discussion 🗣
The issue of a standard document format for Accord Project was raised by @jeromesimeon.
Details can be found here: Cicero Issue #562
TL;DR
The current CTA compressed archive format assumes the Accord contract is a template that is editable and represents a contract type but is not a contract in and of itself.
The assertion is that there needs to be a file format which contains a contract instance and encapsulates all data, logic and legal artefacts (e.g. signatures) that represents the final, executed agreement.
Context
This could be related to the issue Identity management and digital certs #13.
This could be a "Lab" candidate - under the Apache definition as there is no existing codebase.
The text was updated successfully, but these errors were encountered: