[Developers] freebase-suggest modification

[brendan]

Please keep the old options around for a while: meaning, until we've  
corrected the documentation everywhere and we have no evidence of  
anyone using the old options. I think that's what you meant by  
"deprecated" but just wanted to make sure.

thanks,

Brendan

On May 19, 2008, at 1:03 PM, Andi Vajda wrote:

>
> On Mon, 19 May 2008, Faye Li wrote:
>
>> 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.
>
> The values of "true" and "false" for "strict" are still supported  
> but on
> their way out (deprecated). The proper values for "strict" are:
>   - 'should' -> type matches are favored but not required
>   - 'any' -> one type from the list supplied is required to match
>   - 'all' -> all types must match
>
> Andi..
> _______________________________________________
> Developers mailing list
> Developers at freebase.com
> http://lists.freebase.com/mailman/listinfo/developers