Amigos,
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
restaurant.
It is based on all_you_can_eat:type from this proposal, which I found to be
quite interesting when used
On Fri, Feb 28, 2014 at 4:15 PM, John Packer john.pack...@gmail.com wrote:
Amigos,
I no longer feel this proposal is appropriate, therefore I'm canceling it.
Thanks for all your comments.
Remember it's still OK to write a note (in the local language preferably)
associated with any node.
When you say no longer appropriate, do you mean to say the
all_you_can_eat idea is not appropriate, or that working through the
approval procedure got bogged down? ;-)
I feel the idea is not appropriate, at least not to my initial needs. I
started this proposal to be able to tag some buffets
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
On Monday, February 17, 2014, Steve Doerr doerr.step...@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
Am 17/feb/2014 um 21:57 schrieb John Packer john.pack...@gmail.com:
Summary of changes:
1. combined subtag :opening_hours with the main tag (inspired by the tags lit
and fee)
I suggest to use :service_times instead of opening hours here.
cheers,
I'm not sure I understood everything you said, John, specially about
interval. Would you update your proposal and send it to us the way
you think it should be?
I suggested serving system because that's how Wikipedia describes
it. I think I know English well, but since I'm not a native speaker,
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
On Sat, Feb 15, 2014 at 7:57 AM, John Packer john.pack...@gmail.com wrote:
Actually, all_you_can_eat:type=* describes the *way* the food is served.
If the value is buffet, then people go to the food to get it; if the
value is rodízio, then waiters go around the restaurant offering samples
of
On 2/17/14 1:49 PM, Steve Doerr 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
So now, what's the difference in /serving style/ between rodizio and dim
sum?
I never went to a restaurant with *dim sum*, but reading about it on
wikipedia, I would say the differences are:
In a rodízio, the waiters go around offering food, and don't leave food on
a table unless requested by
Updated the proposal.
Summary of changes:
1. combined subtag :opening_hours with the main tag (inspired by the tags
lit and fee)
2. removed value only from main tag
3. added value special to main tag
4. renamed subtag :type to serving_system (should I move this to a new
proposal?)
2014-02-17
So now, what's the difference in /serving style/ between rodizio and dim
sum?
The former is a serving style while the latter is a cuisine. The latter
might also appear in restaurants that employ a serving style of rodizio.
Btw, this is the first time I've been exposed to that term either in
John, at this point, would you please you put all this into a summary, or
a full proposal, so we can see the entire package?
Do you mean this?:
http://wiki.openstreetmap.org/wiki/Proposed_features/All_you_can_eat
I think I should better document the serving_system values. I will do that
this
The problem with cuisine=all_you_can_eat is that All you can eat is
a pricing scheme, not a cuisine. This would prevent tagging with the
actual cuisine, such as cuisine=Chinese or cuisine=Mediterranean.
+1
cuisine=* should be reserved for the actual type of food, not the
pricing/serving
It seems I was too brief in my initial email, so let me clarify.
What I am proposing *is not* cuisine=all_you_can_eat.
I am proposing three new tags: all_you_can_eat,
all_you_can_eat:opening_hours and all_you_can_eat:type.
I am in complete agreement cuisine=all_you can_eat and cuisine=buffet are
Reading up on Wikipedia
(http://en.wikipedia.org/wiki/All-you-can-eat#All-you-can-eat_.28AYCE.29),
this tag could also be shortened to ayce=yes/no.
I agree all_you_can_eat=* is a little long, however I would like to keep it
that way. Because if another mapper saw a place with ayce=*, he
Actually, all_you_can_eat:type=* describes the *way* the food is served. If
the value is buffet, then people go to the food to get it; if the value is
rodízio, then waiters go around the restaurant offering samples of food to
each table; if the value is conveyor_belt, then people sit around a
Hi John,
I do not understand why this is useful.
The suggest tag is too long, to specific.
I do not understand the need for a special all_you_can_eat:opening_hours
The problem with cuisine=all_you_can_eat is that All you can eat is
a pricing scheme,
If you really think the information
+1 for pricing_scheme, +1 against the :opening_hours subtag
What nounours77 proposes is simpler, easier to map, easier to
understand and easier to consume in applications.
I also suggest another tag:
serving_system=buffet/smorgasbord/a_la_carte/table_d_hote (read up
that Wikipedia link I've sent
John,
Thanks for the clarification. I reckon I can now agree with your intent and
the wording of this proposal.
As an aside though, I wonder how many mappers will take the trouble to tag
such restaurants with the full compliment of tags you want to provide.
There is a similar type of restaurant
I sincerely don't think it's length is a problem. There are longer accepted
tags(like parking:condition:right:time_interval), and to shorten it would
make it harder to remember and recognize (i.e. humans would be the ones
paying the price). Tags like addr:* and ele are okay to abbreviate because
http://wiki.openstreetmap.org/wiki/Proposed_features/All_you_can_eat
This tag describes whether there is an all-you-can-eat option in a
restaurant, fast food joint, cafe or other kind of place that sells food
for direct consumption.
___
Tagging mailing
John Packer wrote:
http://wiki.openstreetmap.org/wiki/Proposed_features/All_you_can_eat
What does taginfo suggest people are currently tagging places with an
all you can eat option as?
I'm not convinced that this necessarily needs a proposal...
Cheers,
Andy
What does taginfo suggest people are currently tagging places with an all
you can eat option as?
The closest I was able to find were 2 uses of cuisine=all_you_can_eat, 1
use of note=all_you_can_eat, 5 uses of buffet=yes and 68 uses of
cuisine=buffet.
The tag cuisine=buffet might have a
There are many all-you-can-eat restaurants in North America too, and
just like here, the actual food type (cuisine) may vary considerably.
Reading up on Wikipedia
(http://en.wikipedia.org/wiki/All-you-can-eat#All-you-can-eat_.28AYCE.29),
this tag could also be shortened to ayce=yes/no.
On Fri,
On 02/14/2014 06:33 PM, John Packer wrote:
What does taginfo suggest people are currently tagging places with
an all you can eat option as?
The closest I was able to find were 2 uses of cuisine=all_you_can_eat,
1 use of note=all_you_can_eat, 5 uses of buffet=yes and 68 uses of
On Fri, Feb 14, 2014, at 09:03 PM, John F. Eldredge wrote:
The problem with cuisine=all_you_can_eat is that All you can eat is
a pricing scheme, not a cuisine. This would prevent tagging with the
actual cuisine, such as cuisine=Chinese or cuisine=Mediterranean.
+1
cuisine=* should be
28 matches
Mail list logo
