After reading your explanation and doing some research into this myself, I can see where you’re coming from.
Adding this 10 days later:
@Code-Jack I was watching this YouTube video diving into object oriented programing, which I’m guessing is where the main idea of object oriented approach to note taking came about. It is what @lester1027 used to help someone else understand relations in Anytype, and I think it’s quite a good video.
There are some terms touched on in the video that are familiar because it’s the same terms that are being used in Anytype, e.g. Class.
And then there are “Attributes”, which are what we are referring to here. Sometimes referred to as “Fields” (aligns with your point), but most programmers know them as “Properties” (and using the term Properties aligns with my point).
So it’s the same, can be called both “Field” and “Property”. “Fields” is what it’s sometimes referred to, and “Properties” is what most programmers would call it (his words, not mine). I’ll go one step further to say say: though most programmers call it Property, non programmers (not computer/software/data junkies, just normal layperson) would also know this more commonly as “Property”.
I’m not going to hide that I personally, as a layperson myself, like the term “Property” more than “Field” (and I think it shows from my comment lol); but if Anyteam have already decided on “Field”, sure, they’re the ones building this software and it’s not too big of a deal. However, I still think “Property” is going to appeal to the masses more, and considering majority of the everyday notetakers that Anytype would cater to are going to be non-programmers; calling it “Properties” is going to benefit Anytype. Also keeping in mind that this is something that stays for the remaining of Anytype’s life moving forward, I think going with the safer, more recognized term, is better.