[Developers] Change in JSON output

[Kirrily Robert]

On Mar 4, 2009, at 10:55 AM, Kendra Kuhl wrote:
> Any knowledge beforehand will work, but the more notice the better.  
> The way
> in which that gets delivered is completely up to you, as long as we  
> know the
> rules. :o) I keep an eye on the developer list, so an email to the  
> group
> would work. Doesn't have to be detailed, just something saying - "New
> release will be deployed on this day, go here for details". We use a  
> JSON
> parser, but we check for that ok status code before loading up a  
> class we
> didn't need (why parse the JSON if we don't need to). So, this  
> change broke
> some stuff. That leads me to my next question. Will this be coming  
> to the
> rest of your APIs? Right now the search API still returns the old  
> way. Will
> you be changing that too? And, is there a chance that it will get  
> changed
> back in one of the next release cycles?


Kendra,

Generally speaking, we give notification here on the developer mailing  
list and/or on the Freebase blog at http://blog.freebase.com/, and for  
an API change, we would hope to give at least a couple of weeks'  
notice.  I have no idea how this one slipped through the net, but it  
certainly wasn't intended to do this without notice!  We are changing  
some of our release processes at the moment, so I am going to talk to  
some folks about how we can make sure that I'm aware of things like  
this and can publicise them ahead of time.

K.

-- 
Kirrily Robert
Freebase Community Director
kirrily at metaweb.com
http://freebase.com/