FOAF and hCard compared

FOAF or other xml hCard Description
foaf:Agent n.a. A superclass for any whatsoever which can act in some way. For persons, organisations, groups and the like there are better, more precise classes.
foaf:Person n.a. A person. It is not specified wether this person is alive, dead, historical, fictive or whatever The usage of address and hCard markup implies a person beeing referenced.
foaf:name fn Full name of the person, including any titles, prefixes, suffixes, ...
foaf:nick nickname A nickname as f.ex. beeing used in forums, chats, blogs or the like.
foaf:title title A title
foaf:homepage url The url of a web site related to that person.
foaf:mbox email The e-mail address of that person With hCard it is possile to refine that by specifying the type of e-mail address.
foaf:sha1sum n.a. A Hash of the first e-mail address, used as an ID for that person.
foaf:img photo A picture directly related to that person, i.e. a photo of that person.
foaf:depiction photo Similar to img, but a superclass. May denote any visual representation of that person.
foaf:surname family-name (?) Family name? FOAF status is testing.
foaf:family_name family-name Family name? FOAF status is testing.
foaf:givenname given-name The given name.
foaf:firstName given-name The given name

The other FOAF properties do not have a hCard representation, and there are hCard properties where there are no FOAF representations Luckily there is a way to include vCard properties into the FOAF RDF document, as recommended by the Web Consortium. So a complete personal data file in RDF will include both namespaces. Dublin Core is not reallycomparable, the crossover parts are too few.