[Developers] freebase-suggest modification

[Faye Li]

In terms of "strict", "should" really means "false", and the results are 
not restricted to the type specified. This pattern is used in the 
Freebase app where if you autocomplete on a property that expects a Film 
Actor, for example, topics matching that type are boosted, but other 
types are not entirely eliminated, since it's possible that a topic 
hasn't been properly typed.

If you only want topics of the specified type to show up, and it sounds 
like you do, you need to set "strict" to True when using 
/api/service/autocomplete. "Strict" defaults to True for 
/api/service/search.

-- Faye


Christopher Dummy wrote:
>> queries even though they look the same. When absent, "strict" defaults
>> to "true" for search (it's a must), and "should" for autocomplete (it's
>> preferred).
>>     
>
> What does "should" specify? I'm unclear as to how that would change
> the results. Does that leave whether or not things show up in the
> choice of the API? would it be different on each request?
>
>