Hi Jessee,
The idea of implementing VCards for address storage was to have one database field containing all contact information formatted as VCard or another format. I don't like to add 200 cols to the contacts table just for each requested address field. I like the interface of Apple's Address book (or Gmail contacts) where the user is free to add fields and groups of fields for one specific contact record. To store this kind of data, a common database requires a very complex structure.
I planned to use some existing classes such as PEAR::Contact_Vcard_Parse and Contact_Vcard_Build. If there are any better classes, please give me a hint.
Currently, there's nobody working on this because we have to solve some basic issues before we can start extending the address book. Building the interface the way I have in mind, will also take some time...
Please contact me if you're interested in taking care of this task.
Regards, Thomas
Jesse Gillespie wrote:
A few questions with respects to the planned vCard implementation:
What are the plans to implement this?
Will the address book data be stored as vCards, or simply imported into the database?
Will we be using the vCard class, or building a parser from scratch?
Is anyone working on this now? Is there any room to help out?
//jesse gillespie
FreeMarket: an open source prediction market http://www.freemarket-project.org