As you guys know, I'm more excited about structured names and addresses in the Contacts API than anyone really should be. However, I've noticed that the automatic parsing that (sometimes?) happens when there is unstructured data but no structured data isn't super sophisticated.
For instance, if I have a contact named Dr. John J. Smith, Jr., the current parser returns firstname="Dr.", middlename="John J. Smith", lastname="Jr.". Clearly, the ultimate answer here is for Contact API clients -- including the Contacts web UI -- to input structured data. But in the mean time, more robust parsing would be most helpful. Any chance that functionality will be upgraded soon? If not, here's a simple stopgap measure I'd like to see. Include a flag in the name and address elements indicating whether the structured data was entered as such, or if it was created by parsing unstructured data. That way we could simply ignore the structured data marked as "parsed" and apply our own parsing rules to the unstructured data. Thanks, Charlie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Contacts API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-contacts-api?hl=en -~----------~----~----~----~------~----~------~--~---
