The aim of this issue is to come up and discuss a base RDBMs schema that supports the following requirements:
- Support for multiple users
- Support for multiple projects
- User permissions on project level
- Store translations as key/value pair (key should be fully qualified name?)
- A project needs to consist of various translations across different languages.
- Different language standards need to be supported (e.g. different language code standards, also with localization)
- Support fallback language
The following image shows an example ER diagram depicting what such DB schema could look like.

Let's discuss if this is a good starting point or some adjustments to this proposal would make more sense. For example, not storing languages as individual table.
The aim of this issue is to come up and discuss a base RDBMs schema that supports the following requirements:
The following image shows an example ER diagram depicting what such DB schema could look like.

Let's discuss if this is a good starting point or some adjustments to this proposal would make more sense. For example, not storing languages as individual table.