This document adds additional properties to the Person class.
The Person class should have properties for:
each component of the name
To display an abbreviated name on a mobile device.
To sort a list of names.
Many specifications use the same terms for name components, including FOAF, Schema.org, RFC 6350 (vCard 4.0) and OpenSocial. FOAF and Schema.org terms are reused, given their breadth of adoption.
The survey of existing specifications found few terms for sort keys;
sortName was chosen, which is under consideration for FOAF. The Person Core Vocabulary adds a
Patronymic names are important in some countries. Iceland does not have a concept of family name in the way that many other European countries do. In Bulgaria and Russia, patronymic names are in every day usage.
In RFC 6350 (vCard 4.0), each component of a name – family name, given name, additional name, honorific prefix and honorific suffix – can include multiple text values. Other vocabularies, including FOAF, do not restrict the cardinality of these properties either. Some, like OpenSocial, do. This data specification requires that each component of a name can include one text value only, which itself may contain multiple names.
||One or more family names|
||One or more primary given names|
||One or more secondary given names|
||One or more honorifics preceding a person's name|
||One or more honorifics following a person's name|
||One or more patronymic names|
||A name to use in a lexicographically ordered list|
schema:honorificPrefix is used instead of
foaf:title is a candidate for deprecation.
2. FOAF proposes
foaf:sortName. vCard uses
con:sortName seems to be the only existing RDF property.