This is a good point that I have not thought of but sincerely relate. My pkm (and Graph, by extension) is so much richer and interactive because the term Relations encouraged me to build connections and fill in relevant (related) data wherever possible. Sure, a Graph with an ability to connect docs can be present in any app, but if not for the word relation, I would not bother planning and studying how each doc/file/object is connected or defining of one another. I imagine if it was in another app, I’d see a “Property” or an “Attribute” written and I’d just ignore the field thinking I’m not familiar with what it does or maybe I am, but don’t feel like I’m technical enough to bother with all those linking that I can possibly make. But here in Anytype, with a “technically incorrect but intuitive” word (as @ferdzso puts it), I was inspired to build a second brain that reflects my thought process more than just linking documents because the app can technically do it.
Even for those ‘relationships’ that don’t show in Graph (ex: location, number, tags…), the term encourages you to fill out important data (and consider where or how you can reuse it) that you can otherwise just write in text. There’s just something empowering with the choice of word and the simplification of the feature.
So in that context, I’d say that Relations is as much of a backbone of Anytype as its p2p and encryption capabilities.
I think, for newcomers, developers, and seasoned pkm users, it’s perfectly normal to feel like it’s introducing a made up term/feature (it kinda is), and think, “this isn’t right. We could use another/a more accurate word for its specific uses”. But for people who have settled in, it’s not just a word choice, it’s a building tool that founded our entire knowledge space. It signifies every notable data that I can put out there. It’s not that hard to grasp.
Okay, this might be coming partly out of emotional attachment, but I still feel like changing it — or worse, dividing it into very specific functions — totally kills the charm and innovation of that app feature. I may be convinced if the team is finally adding more complexity to Relations that would somehow require a new term, but I can’t see how adding scope or hierarchy would make that necessary.
Whatever happened to this proposal?! I thought this was supposed to monitor, encourage, and reward contributions, leading to the hastening of progress and development. There’s only been silence regarding this topic. 
I know there are some technicalities in there, but to be honest, I understand it just fine when the app says the word Relation encompasses all those uses.
Changing for the sake of changing wouldn’t make the outcome better, and I don’t want to waste our valuable team’s efforts.
)
