We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With support for locale-specific vocabularies in Concerto, we can now expose locale variants to users of Cicero templates
A localised Cicero template would allow reuse of the model and logic definition but with different text and terms depending on a user's locale.
For example, a contract written for Canadian law, could have text and model terms in both en-ca and fr-ca.
A vocabulary for a template's model should follow the implementation that was recently created for Concerto.
Templates should include text for each locale that they support, with a default locale identified for backwards compatibility.
Open questions:
.voc
The text was updated successfully, but these errors were encountered:
@mttrbrts can you elaborate on this a bit more, like what are we trying to achieve here by using vocabularies.
Sorry, something went wrong.
Thanks @amanag25 , I've added a little more detail.
This idea isn't well formed yet, and some discussion in this issue would be helpful before any code is written.
Do you have any suggestions?
No branches or pull requests
Feature Request ποΈ
With support for locale-specific vocabularies in Concerto, we can now expose locale variants to users of Cicero templates
Use Case
A localised Cicero template would allow reuse of the model and logic definition but with different text and terms depending on a user's locale.
For example, a contract written for Canadian law, could have text and model terms in both en-ca and fr-ca.
Possible Solution
A vocabulary for a template's model should follow the implementation that was recently created for Concerto.
Templates should include text for each locale that they support, with a default locale identified for backwards compatibility.
Open questions:
.voc
files live in a Cicero template?Context
Detailed Description
The text was updated successfully, but these errors were encountered: