[Developers] State Quarters example and "need a unique result to attach here"

[David Flanagan]

Christopher R. Maden wrote:
> David Flanagan wrote:
>> When I first wrote the US State Quarters example 
>> (http://freebase.com/view/guid/9202a8c04000641f800000000544e10c#id2609142)
>> I specified that the type of the us_state_quarter/state property was 
>> /type/text
>>
>> The example has been modified since I wrote it. It now expects the state 
>> property to be /location/us_state, which is good.  In order to make this 
>>   change work, however, the query in the python code had to change, and 
>> I don't understand why. Since I don't get it, I'm obviously not 
>> explaining something right about the MQL write grammar.
> 
> Names of things are not generally a good idea for connecting properties, 
> as they are rarely unique (and will become less so as Freebase expands), 
> and MQL shies away from being (or attempting to be) a DWIM system.

I understand that, but in this case (and as you point out), a US state 
is uniquely identified by its name and its type.  I'm wondering why, 
therefore, the expected type of the state property plus the name of the 
state isn't sufficient to identify the state object I want.  (And why is 
it confused about a city named Delaware?)

In order to make my documentation clear, I need to understand not just 
why it is a bad idea, but why it doesn't work!

	David