[Tagging] Feature Proposal - RFC - All You Can Eat

John Packer john.packer7 at gmail.com
Sat Mar 1 00:15:34 UTC 2014


I no longer feel this proposal is appropriate, therefore I'm canceling it.
Thanks for all your comments.

I am creating another proposal to describe the serving system of a
It is based on all_you_can_eat:type from this proposal, which I found to be
quite interesting when used properly.
It is still in *Draft* status, and can be seen in the following link:


2014-02-24 16:38 GMT-03:00 Fernando Trebien <fernando.trebien at gmail.com>:

> I remember having been to restaurants here in Brazil where the food
> that is served as "all you can eat" is not exactly the same as the one
> you may order from a regular menu. Not far from my home there is a
> restaurant that serves 3 cuisines at different times of the day
> (italian and japanese for dinner, and an all-you-can-eat regional
> buffet for lunch; I'm sure but they may operate a cafe for breakfast).
> Place all the values in the cuisine tag and you won't be able to tell
> at which time each cuisine is offered. How do you express that the
> all-you-can-eat service is offered only for the regional cuisine?
> Answer: you need 2 objects (nodes or areas) for that.
> But anyway, I'm with Martin, it's best to use :service_times to avoid
> confusion with the regular opening_hours tag. The place is usually
> open (offering its regular service) for a longer period than that in
> which it offers an all you can eat service.
> On Sat, Feb 22, 2014 at 4:37 PM, Paul Johnson <baloo at ursamundi.org> wrote:
> > On Monday, February 17, 2014, Steve Doerr <doerr.stephen at gmail.com>
> wrote:
> >>
> >> On 17/02/2014 18:04, Fernando Trebien wrote:
> >>
> >>> I still think that "opening_hours" as a subtag would be an unnecessary
> >>> specialization that would only be needed rarely. Can you provide an
> >>> example in which you would not be able to represent that information
> >>> in a different way? (such as using two or more geometric objects)
> >>
> >>
> >> It's quite common in the UK for a restaurant to operate as a normal, a
> la
> >> carte restaurant most of the week, and offer an all-you-can-eat buffet
> on,
> >> say, Sundays. I'm at a loss to understand why that would be represented
> as
> >> two separate geometric objects.
> >
> >
> > Yeah, I've been trying to think of a use case scenario that makes sense
> for
> > this, and I can't.  It seems to be more in line with the expectation
> typical
> > by cuisine.  For instance, Genghis Grill seems to be about the only chain
> > around that doesn't consider Mongolian.
> >
> > _______________________________________________
> > Tagging mailing list
> > Tagging at openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/tagging
> >
> --
> Fernando Trebien
> +55 (51) 9962-5409
> "The speed of computer chips doubles every 18 months." (Moore's law)
> "The speed of software halves every 18 months." (Gates' law)
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20140228/4028df73/attachment.html>

More information about the Tagging mailing list