-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Base/Cicero Accord Project Models Revisions for version 1.0 #93
Comments
A draft for what the base models could be like for That draft assumes support for systems model will be removed from Concerto. Some changes:
There is a lot of room for discussion here, and will need review and iteration. |
Nothing to add from me here. The changes in your fork LGTM |
@mttrbrts Are you also happy with 6. and 7. which I thought were a bit more controversial? About 6. We do have a few templates which leave parties as blank. About 7. Could go with specific Ergo support for storing/retrieving obligation from the state. This could provide much nicer support for the kind of logic currently used in the Supply Agreement template https://github.com/accordproject/cicero-template-library/tree/master/src/supplyagreement |
Status update on this issue:
Some observations:
|
New Accord Project base models can now be found in https://github.com/accordproject/models/tree/master/src/accordproject |
The Accord Project base models in https://github.com/accordproject/models/tree/master/src/cicero
were designed very early on before we had a lot of experience with the programming model, with the Ergo type system, etc.
Before we go to Cicero
1.0
we should do a review of those models, decide whether any change would be useful/needed.This revision should be aligned with whatever decision we make on whether we keep or remove support for Concerto systems models. (See accordproject/concerto#62)
Also, this revision should ideally address the use of a slightly different base model for Ergo type checking. (See accordproject/ergo#698)
The text was updated successfully, but these errors were encountered: