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.

Sign up for GitHub

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

Jump to bottom

Include requirements? #3

Open
nrooney opened this issue Mar 17, 2016 · 0 comments
Open

Include requirements? #3

nrooney opened this issue Mar 17, 2016 · 0 comments

Comments

@nrooney
Copy link
Contributor

nrooney commented Mar 17, 2016

We could include requirements in the doc. These could be some of them:

Requirements

The use cases identified above allow the identification of a set of requirements. These are given below and should not be considered exhaustive.

  • A coding for absolute level of preference for a modality-language combination in levels. Suggestions include three levels: preferred, can-do, last-resort, or two levels: preferred and possible.
  • A grouping rule saying that if a language and modality is indicated for one direction and a certain level of preference, then it shall be regarded to be preferred to be used together with a language and modality in the other direction with the same level of preference.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nrooney