Hey @rock. It would be nice if you could explain your thoughts in English, as this is a mainly English community.
Team has already planned for a change in set and collection. See Prospective renaming of Collections & Sets; topic continuation
There are a few existing feature requests/discussions that might bring what you desire. Upvote them to show your needs and supports.
It seems the needs from your point 1 and point 2 could be a little contradictory… Point 1 requires more relation to be applied to more things, then point 2 requires more specification in relations…
- The current thing you could do is to create your own relation with specific usage.
– Different multi-select relations (as tag) e.g. commercial/cargo tag relation for airplanes and also communication tag relation for conversation
– Or set a limit for type in object-supported relation.
- Even though it might be conflicting, I believe under Anytype’s structure, it is possible to do both through actualising relational data model. For example, request StatusRelation then specific a secondary criterion (key) for Airplane ConditionForStatus, then we could have a general relation then narrow down to specific properties/options (hopefully at all relevant access points and but also only when required)
– In this case, Advanced Filters / Queries will be helpful.
