Open jimkont opened 9 years ago
PersonFunction already has everything needed to record start and end. start/endOccupation are strings (?). I really don't see why they would be needed here.
otherOccupation is clearly named after the the template property name. Maybe just use occupation?
Maybe @jplu will stop by ?
everything needed to record start and end
In fact too much. Eg take activeYearsStartYear, activeYearsStartDate: there is no need for 2 fields differing only by precision. A field should reflect some meaning, a data type (xsd:date vs xsd:gYear) should be used to reflect precision. We need a best practice on mapping persons and positions.
I agree with that.
I was actually about to create a new issue about that (which is now done as #56 ). I think we have an example of "code is law" here. See this other issue for details. Any feedback is welcome!
At the moment these properties are used on one template each without proper documentation in in http://mappings.dbpedia.org/index.php/Mapping_fr:Infobox_Personnalit%C3%A9_du_hockey_sur_glace & http://mappings.dbpedia.org/index.php/Mapping_fr:Infobox_Musique_classique_(personnalit%C3%A9)
should we change these mappings?