In the content tree, it is currently possible to add Table, Text, and Section as child of an Expression.
This is insufficient because some projects have linguistic objects that don't contain text. So the Text class does not meet the needs.
Solution
Content tree edit
1.a.
In the menu of Source Content and Section (and Linguistic Object once created), we need to add a button Linguistic Object, below Section but before Table and Text.
That creates a statement with:
subject: Clicked Instance (of class, Expression | Section | Linguistic Object)
property: crm:P165 incorporates
object: Linguistic Object
The button should be Blue (Entity) FOR THE MOMENT.
1.b. The Linguistic Object cannot be the parent of something else than a Text, Table or another Linguistic Object. Expressions and Expressions sections are NOT linguistic objects.
Content tree view
In the content tree visualize also property crm:P165 incorporates and its objects, as well as instances of geov:C16 Text (see issue #353) with the property geov:P1i is reproduced of
Show the content tree tab on entity cards of Linguistic Objects
On the View of Lingusitic Object, show the content tree on the right.
Current Situation
In the content tree, it is currently possible to add Table, Text, and Section as child of an Expression.
This is insufficient because some projects have linguistic objects that don't contain text. So the Text class does not meet the needs.
Solution
1.b. The Linguistic Object cannot be the parent of something else than a Text, Table or another Linguistic Object. Expressions and Expressions sections are NOT linguistic objects.
Content tree view In the content tree visualize also property crm:P165 incorporates and its objects, as well as instances of geov:C16 Text (see issue #353) with the property geov:P1i is reproduced of
Show the content tree tab on entity cards of Linguistic Objects On the View of Lingusitic Object, show the content tree on the right.