-
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
Define key terms and definitions in a contract/clause #124
Comments
This is an interesting issue. I'm not sure how I missed it. I'm a little unclear if this should be:
|
@jeromesimeon I think we will first have to create a data type for this which I guess makes it a concerto issue. Then we can handle the parsing in cicero. |
What functionality would you expect this to have? E.g. within the Contract Editor. |
Whatever this is, I feel this is mostly related to the models library. We do already have "base" types for requests/responses/obligations/contract state etc. Not sure we need more. Users can define their own kinds of obligations that might be more specific. Am I missing something? |
Is your feature request related to a problem? Please describe.
It would be great if we could add a data type whose function will be to define the key terms or definition used throughout the contract. An example of such terms:
Describe the solution you'd like
We can add a data type which shall define these terms.
Describe alternatives you've considered
I am although not sure if this should be a data type or we can just place it at the beginning of the contract (it exists in the beginning usually) and parse it using
cicero
.The text was updated successfully, but these errors were encountered: