Tickets :: [#4999] Support of name components in turba

Summary	Support of name components in turba_object schema
Queue	Turba
Queue Version	HEAD
Type	Enhancement
State	Rejected
Priority	1. Low
Owners
Requester	ntai (at) smartfruit (dot) com
Created	02/15/2007 (6820 days ago)
Due
Updated	02/15/2007 (6820 days ago)
Assigned
Resolved	02/15/2007 (6820 days ago)
Milestone
Patch	No

02/15/2007 09:28:34 AM	Jan Schneider	Comment #2 State ⇒ Rejected	Reply to this comment
Then change it.

02/15/2007 07:37:22 AM	ntai (at) smartfruit (dot) com	Comment #1 State ⇒ New Priority ⇒ 1. Low Type ⇒ Enhancement Summary ⇒ Support of name components in turba_object schema Queue ⇒ Turba	Reply to this comment
Since a lot of non-Horde contact information contains the notion of name components, it requires to do some sort of magic to map the turba_object schema's name to non-Turba contact information. For example, vCard spec: Family Name (first field), Given Name (second field), Additional Names (third field), Name Prefix (fourth field), and Name Suffix (fifth field). ldap's commonly used schema uses sername (sn) a.k.a. lastname and distingused name (dn). The interoperability of turba schema against non-turba world would be a lot better if it supports name components.