TODO: define the behaviour in the UI @Lydia_Pintscher, otherwise this would be only about the internal data strcture, and the data structure exposed to users (API or special pages).
Note that as of 2018-03-19, the data structure used for internal storage of the lexeme data is assuming there only a single form representation for a given language code.
The possible data structure used could look like below:
```
"L560": {
...
"forms": [
{
"id": "L560-F1",
"representations": [
{
"language": "en",
"value": "colour"
},
{
"language": "en",
"value": "color"
}
],
...
}
...
]
...
}
```
For the existing data stored in the database of the demo system, and possible other development instances, the conversion of the data could be provided by adding the needed functionality to LexemeSerializationUpdater (if found necessary).
Pointers:
- FormSerializer is the service generating the structure stored in the database, and also used e.g. by get entities API action