One reason to have a subclass structure under Person (but also under any natural kind) is to support generalizations for subcategories. Many of the subclasses of Person in DBpedia are for occupations, e.g., Architect, Athlete, NascarDriver, Politician, and Senator. If these subclasses of Person are eliminated then there should be some way to retain that any senator is a politician.
peter On 07/11/2017 03:10 PM, Sebastian Hellmann wrote: > Hi all, [...] > By the way, is there actually any sensible class that can be subclass of > Person? As far as I see, the only essential distinction that lasts lifelong is > fictious/non-fictious . We are thinking about disallowing subclasses of > Person, unless there is a valid concern brought up. > > Also it seems like we will not be able to handle all exceptions like spouse > being non-functional for a dozen persons. From a practical perspective, if > functionality is consistent for 95% of the data, this might be something we > can live with. Proper documentation of these pitfalls can be given. > > All the best, > Sebastian > > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ DBpedia-discussion mailing list DBpedia-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
