Skip to content

Include requirements? #3

@nrooney

Description

@nrooney

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions