Yes, this is one of the differences to Notion, where you can create any number of databases (database = table) in a workspace, each with specific properties.
Well, a space is basically a graph DB, and because of that a collection is a sub-graph, which can still be considered as graph DB. At least theoretically, in graph DB, there are ways to “scope” the relations between nodes so that they can be handled for a specific sub-graph.
E.g. in common graph DB implementations like memgraph and neo4j, relations have their own attributes. A simple solution there, would be to add a relation property to store the “scope” of the relation, and then you could use it, for example, to differentiate tags based on the scope or just show all of them.
So, I really do not think there’s any technical or theoretical blocker for this feature, and IMO the fact that anytype doesn’t handle DBs like Notion is not relevant to the topic. I would guess that the issue is that implementing this feature requires a careful update of the core part of the app, for which currently there’s no time.
And the only solution for me currently is creating properties (relations) with a scoped name, e.g.
Trip | Tag
Project | Tag
…