[Data-modeling] modeling restaurant price ranges

[Dan Milbrath]

These are just display names and can be easily modified. 
I'd be inclined to go with either ($,$$,...) or (*,**,...) until the need to revisit this arises.
We've done plenty of data modeling in the past where the practical trumped the perfect.






----- Original Message -----
From: "Kirrily Robert" <kirrily at metaweb.com>
To: "Freebase data modeling mailing list" <data-modeling at freebase.com>
Sent: Friday, April 25, 2008 3:33:34 PM (GMT-0800) America/Los_Angeles
Subject: Re: [Data-modeling] modeling restaurant price ranges


On Apr 25, 2008, at 3:14 PM, Robert Cook wrote:

> I like the idea, but I wouldn't use $ as the indicator as it wouldn't
> localize into the UK (and, for example, the mexican peso wouldn't
> localize into Spain.)  Also the guidelines would have to be written
> for each country.
>
> Another approach might be to store the average price of an entree in
> the local currency.


"Average price of an entree" only works for places that offer sit-down  
meals, especially dinners.  Doesn't work so well for eg. a dim sum  
place, or even a lunch bar.

How about just asterisks instead of $ signs?  Or high-end/midrange/ 
budget as I did for travel?  Most people can estimate which of those  
three categories a restaurant or hotel fits into, using the local  
currency and culture as a baseline, but calculating an average meal  
price is a bit more work.

K.

-- 
Kirrily Robert
Freebase Community Director
kirrily at metaweb.com
http://freebase.com/




_______________________________________________
Data-modeling mailing list
Data-modeling at freebase.com
http://lists.freebase.com/mailman/listinfo/data-modeling