[Data-modeling] "area" property of "/location/location" type

[Kurt Bollacker]

On Wed, Apr 02, 2008 at 11:40:00AM -0700, Robert Cook wrote:
> So far my (kind of lame) solution is to use two distinct properties.   
> This is an OK stopgap, but, like all denormalizations, it's confusing  
> and semantically sub-optimal.  

The most common example of this is "name" and "alias" for topics.  In
this case, the semantics of separation are clear.  Is analogously
naming like "alternate area measurements" still confusing?

> The "simple" property really should be  
> generated by a query on the complete property, although it's not clear  
> how that could support the "top 30 earthquakes" example above in a  
> performant way.  For now, though, we have to balance when to have the  
> simple representation and when we should add a CVT enriched property  
> that can hold all of the possible representations.

Although there are several ways graphd could support these use cases
in a performant way, none of them are exposed in MQL.  Perhaps the
longer term solution is to add support for this general "main"
vs. "alternates" split to MQL itself.

								Kurt :-)



 
> Thoughts?
> 
> R
> 
> On Apr 2, 2008, at 10:47 AM, Jeff Prucher wrote:
> 
> >> -----Original Message-----
> >> From: data-modeling-bounces at freebase.com
> >> [mailto:data-modeling-bounces at freebase.com] On Behalf Of
> >> Kirrily Robert
> >> Sent: Wednesday, April 02, 2008 10:04 AM
> >> To: Freebase data modeling mailing list
> >> Subject: Re: [Data-modeling] "area" property of
> >> "/location/location" type
> >>
> >>
> >> ----- "Jonathan W. Lowe" <jlowe at giswebsite.com> wrote:
> >>> The "/location/location" type has an "area" property that accepts
> >>> multiple values.  Should this property instead be restricted to one
> >>> value?
> >>>
> >>> Unless someone can identify a location having more than one valid
> >>> area, I recommend a schema change that restricts
> >>> /location/location/area to one value.
> >>
> >> Time series!  Uhhh... forget I said that.  Please.  PLEASE?
> >
> > Well, that and the fact that different sources can have different,  
> > equally
> > valid, area measurements for the same location at the same time,  
> > depending
> > on methodology. But neither of those reasons is why the current  
> > property is
> > non-unique; the real reason is that I forgot to check the box. Me, I'm
> > tempted to just make it unique until we actually have some time- 
> > series data
> > to input. Right now, it's practically all WP infobox loads, which  
> > implies
> > reasonably current area.  (There are 24 locations with multiple  
> > values, all
> > of which appear to be differences in rounding, conversion, or using  
> > the
> > different measurement units, which will have to be cleaned up before  
> > we can
> > make the property unique.)
> >
> > Jeff P
> >
> > _______________________________________________
> > Data-modeling mailing list
> > Data-modeling at freebase.com
> > http://lists.freebase.com/mailman/listinfo/data-modeling
> 
> _______________________________________________
> Data-modeling mailing list
> Data-modeling at freebase.com
> http://lists.freebase.com/mailman/listinfo/data-modeling