Skip to content
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

Support for Concerto Vocabularies #711

Open
mttrbrts opened this issue Jan 5, 2022 · 2 comments
Open

Support for Concerto Vocabularies #711

mttrbrts opened this issue Jan 5, 2022 · 2 comments

Comments

@mttrbrts
Copy link
Member

mttrbrts commented Jan 5, 2022

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:

  1. Where should .voc files live in a Cicero template?
  2. Is a locale-specific parser useful?

Context

Detailed Description

@amanag25
Copy link

@mttrbrts can you elaborate on this a bit more, like what are we trying to achieve here by using vocabularies.

@mttrbrts
Copy link
Member Author

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants