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

[Christopher R. Maden]

David Flanagan wrote:
> 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!

I will let one of the developers handle the rationale.

But we are not yet at a point where we can generally assume that things 
are well-enough typed to use as a filter programmatically, so when you 
specify something solely by name in MQL, it filters solely on the name. 
  If you want to filter on name and type, you must specify the name and 
type.

It is also worth noting that, as per Bryan Cheung’s post to the data 
modeling list, cities and towns are now given their simple names 
(“Delaware”) rather than their formerly disambiguated names (“Delaware, 
Ohio”).

~Chris
-- 
Christopher R. Maden
Data Architect
Metaweb Technologies, Inc.
<URL: http://www.metaweb.com/ >