occupation vs personFunction

dbpedia / mappings-tracker

This project is used for tracking mapping issues in mappings.dbpedia.org

9 stars 6 forks source link

occupation vs personFunction #49

Open VladimirAlexiev opened 9 years ago

VladimirAlexiev commented 9 years ago

The two props occupation and personFunction have nearly identical role & history:

Created at the same time (2010)
No comment to distinguish them, no usage guidance
Both have range PersonFunction
personFunction also has domain Person, but that's a recent addition (2012)
occupation has no domain, but has had Person in the past
occupation has 100-250 uses
personFunction has 20-50 uses

People are more likely to use "personFunction" correctly because the name dictates the range. I doubt people have used "occupation" as an ObjectProperty but I have no desire to check 100-250 uses.

VladimirAlexiev commented 9 years ago

My doubt is correct. These maps use "occupation" as a DataProperty:

So the best is to turn "occupation" to a DataProperty. But before that, we need to check randomly 20 of the maps that use it.

@jimkont The Object/DataProp Dichotomy strikes again

VladimirAlexiev commented 9 years ago

And of course, DOCUMENT them both the end, pointing to each other. God, I hate this lack of traceability.

VladimirAlexiev commented 9 years ago

A similar data prop is "office", see https://github.com/dbpedia/mappings-tracker/issues/45#issuecomment-77564513, eg "President of the US". "occupation" is different, eg carpenter, politician...