Quoting Tom Morris <tfmor...@gmail.com>:
>> OL does not store >> these as authors, however, so we can be sure that all authors are >> persons, or some other entity presenting itself as a person. > > That may be the intent, but it isn't the reality today. There are > large numbers of corporate authors in the database. Look at the > results for this search http://openlibrary.org/search/authors?q=adobe > for just a small sample. GIGO - OL took in some sources of data with "bad" coding -- e.g. coded corporate authors as personal authors. There's actually been talk of removing some of them, since they also tend not to merge correctly in the database. > >> The FOAF >> Person does not imply a natural person, and can be used for any >> assertion of person-ness. > > The spec says "The Person class represents people," which I infer to > mean natural people since that's the common usage. I think Person's > superclass foaf:Agent may be what you want (it's also a superclass of > foaf:Organization and foaf:Group). It goes beyond that and says: "The Person class represents people. Something is a Person if it is a person. We don't nitpic about whether they're alive, dead, real, or imaginary." So unnatural people are included. And that is an interesting variation from library practice, in which imaginary persons do not get personhood. So Luke Skywalker is a concept in LCSH, not a Person. And I don't mean that Luke is a "subject/person" -- there's nothing about the coding that includes personness -- Luke is coded the the same as "Skywalks -- Accidents." kc -- Karen Coyle kco...@kcoyle.net http://kcoyle.net ph: 1-510-540-7596 m: 1-510-435-8234 skype: kcoylenet _______________________________________________ Ol-tech mailing list Ol-tech@archive.org http://mail.archive.org/cgi-bin/mailman/listinfo/ol-tech To unsubscribe from this mailing list, send email to ol-tech-unsubscr...@archive.org
