[Developers] A reminder: /location/mailing_address schema has changed...

[brendan]

I post this as a user, because I noticed archiportal had some breakage  
today after the new freebase release went out.  If folks on the dev/ 
data team want to pitch in more info, please do.

1. the property /location/mailing_address/street_address_2 is now  
hidden in the UI.  The UI now allows the user to create multiple  
values for the "street_address" property, instead.

so... WARNING: if you have queries that ask for "/location/ 
mailing_address/street_address" : null

prepare for breakage because users are now creating multiple values of  
street_address through the UI: you must use [] instead of null.

2. something less urgent: note that mailing_address now has properties  
for state and country.  As an example, archiportal just asks for the  
citytown property and passes that and the street address up to the  
google api to get coordinates.   That works because cities are named  
with the state they are in, for U.S. cities anyhow (e.g. "Oakland,  
California").   I'm not sure what the data team's plan is for this but  
eventually, the city names will change and you will have to query out  
the citytown and the state (and perhaps country) in order to have a  
fully qualified address.

Question for someone on the data team?  When you denude city names of  
the state info, would you please go through all mailing addresses to  
make sure that the state that the city belongs to is filled in (where  
it's known of course)?

When does the data team plan on doing that?

thanks,

Brendan


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freebase.com/pipermail/developers/attachments/20080326/aa79c757/attachment.htm