[Developers] List Of Properties

[Jason Douglas]

So if you do your query for '/guid/9202a8c04000641f80000000002eb15e',  
which is the movie 'Hard Eight', there's no evidence of the Character  
property of Film Performance in the MQL response because while there  
are several CVT instances with the Actor property filled-in, none have  
the Character property set.

Interestingly enough, though, in the course of looking for an example  
I found that freebase.com seems to have the same issue (no Character  
column):
	http://www.freebase.com/view/guid/9202a8c04000641f80000000002eb15e

-jason


On Jul 8, 2008, at 5:20 PM, Warren Harris wrote:

> Hi Jason,
>
> I'm not sure I follow. Can you give me an example?
>
> Warren
>
>
> On Jul 8, 2008, at 5:14 PM, Jason Douglas wrote:
>
>> Warren,
>>
>> I've been playing with that awesome mega-type/reflect query for
>> building my own topic page, and it's working pretty well, but I've  
>> run
>> into one problem which is that because the CVTs are inside out
>> (meaning the property metadata is nested under the links), it seems
>> like there's no way to know for sure all the properties of the CVT if
>> it's sparsely populated (i.e., there's not at least one instance link
>> for each property).
>>
>> A) Is that correct?  & B) Is there a way to compensate for that?
>>
>> -jason
>>
>>
>> On Jul 8, 2008, at 1:01 PM, Warren Harris wrote:
>>
>>>
>>> On Jul 7, 2008, at 10:48 AM, Kendra Kuhl wrote:
>>>
>>>> Thanks Christian. That works great.
>>>>
>>>> Now I’m having a bit of a different problem. Now, because there are
>>>> so many properties, when I query for their values, Freebase either
>>>> gives me a timeout / bad request(while using the API) or doesn’t do
>>>> anything (while using the query editor). I’m thinking it’s because
>>>> there’s too much going on, but maybe somebody can point me in the
>>>> direction to a better way?
>>>
>>> Hi Kendra,
>>>
>>> I think you should be able to adapt the mega- /type/reflect query
>>> that was sent out earlier to return all the detail that you're
>>> trying to get from the query below. But in general, if you ask for
>>> too much in one shot, you run the risk of timing out. Maybe you
>>> should break this up into a series of smaller queries.
>>>
>>> You might also want to use cursors:
>>>
>>> http://www.freebase.com/view/guid/9202a8c04000641f800000000544e139#cursors
>>> http://www.freebase.com/view/guid/9202a8c04000641f8000000005b7ad20?domain=%2Fuser%2Fnix%2Ftypes
>>> http://mqlx.com/~willmoffat/learn_feature/cursor/cursor.js
>>>
>>> Warren
>> _______________________________________________
>> Developers mailing list
>> Developers at freebase.com
>> http://lists.freebase.com/mailman/listinfo/developers
>
> _______________________________________________
> Developers mailing list
> Developers at freebase.com
> http://lists.freebase.com/mailman/listinfo/developers