My req's for the people part of contact info were slim, so i just modeled the contact info data model after the PalmOS fields, as they seem to get the job done pretty well. For now, the contact_info object type duplicates first and last name so that it can be used outside of the context of an ACS Person, as acs persons are a bit unwieldy for use on the level of an address book or something like that (how do you deal with many non-unique copies of a person in different peoples' address books, etc). So when the contact info object was used in the context of being an offshoot of a person, the first_name and last_name fields were just left null, preferring to use the persons table for that info. How does your model differ from the classic persons concept? Or is your concept of a person similar to my contact_info?
