<div dir="ltr"><div>I sincerely don't think it's length is a problem. There are longer accepted tags(like <span style="background-color:rgb(238,238,238)"><span style="font-family:courier new,monospace">parking:condition:right:time_interval</span></span>), and to shorten it would make it harder to remember and recognize (i.e. humans would be the ones paying the price). Tags like <span style="background-color:rgb(238,238,238)"><span style="font-family:courier new,monospace">addr:*</span></span> and <span style="background-color:rgb(238,238,238)"><span style="font-family:courier new,monospace">ele</span></span> are okay to abbreviate because they are used more frequently, but the others not so much.<br>
<br></div><div>I do think this particular pricing scheme(<span style="background-color:rgb(238,238,238)"><span style="font-family:courier new,monospace">all_you_can_eat</span></span>) is useful.<br></div><div>However I do agree that perhaps it would be better to include other pricing schemes.<br>
</div><div>The problem is, I have no idea how they are called, or what they are. For example, what is this daily menu you speak of?<br>
</div><div>Also, one place may have more than one pricing scheme, so I'm not sure the additional complexity is worth it.<br></div><div>I still think<span style="background-color:rgb(238,238,238)"><span style="font-family:courier new,monospace"> all_you_can_eat=yes/no/only</span></span> is a good idea.<br>
</div><div><br></div>
<div>I
understand there is some resistance to <span style="background-color:rgb(238,238,238)"><span style="font-family:courier new,monospace">all_you_can_eat:opening_hours</span></span>,
but I do think it's genuinely useful, as long as it is only used when it
is meant to be used(it is not a replacement of opening_hours). I gave one example of use of <span style="background-color:rgb(238,238,238)"><span style="font-family:courier new,monospace">all_you_can_eat:opening_hours=*</span></span>
in my previous message. Another example is a restaurant that only
offers all-you-can-eat options during lunch, and not during breakfast or
dinner. </div><div>But due to it's complexity(and the small number of cases), perhaps I should add a new value called "<span style="background-color:rgb(238,238,238)"><span style="font-family:courier new,monospace">interval</span></span>" to <span style="background-color:rgb(238,238,238)"><span style="font-family:courier new,monospace">all_you_can_eat</span></span>, which would mean "this option is not available at all times". I believe this would be enough to "kill" <span style="background-color:rgb(238,238,238)"><span style="font-family:courier new,monospace">all_you_can_eat:opening_hours</span></span>.<br>
<br>I actually was having the same idea of ftrebien: splitting <span style="background-color:rgb(238,238,238)"><span style="font-family:courier new,monospace">all_you_can_eat:type</span></span> into a new tag. Because to describe the <i>way</i> the food is served is one of my main purposes for creating this proposal. I was thinking of <span style="background-color:rgb(238,238,238)"><span style="font-family:courier new,monospace">serving_style</span></span>, but <span style="background-color:rgb(238,238,238)"><span style="font-family:courier new,monospace">serving_system</span></span> is also good.<br>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><span style="font-family:courier new,monospace">serving_system:food=<a href="http://en.wikipedia.org/wiki/Buffet" title="wikipedia:Buffet" target="_blank">buffet</a>/<a href="http://en.wikipedia.org/wiki/Rod%C3%ADzio" title="wikipedia:Rodízio" target="_blank">rodízio</a>/<a href="http://en.wikipedia.org/wiki/Sm%C3%B6rg%C3%A5sbord" title="wikipedia:Smörgåsbord" target="_blank">smörgåsbord</a>/<a href="http://en.wikipedia.org/wiki/Conveyor_belt_sushi" title="wikipedia:Conveyor belt sushi" target="_blank">conveyor_belt</a>/<a href="https://en.wikipedia.org/wiki/%C3%80_la_carte" target="_blank">à_la_carte</a>/<a href="http://en.wikipedia.org/wiki/Korean_BBQ">korean_barbecue</a>/<a href="https://en.wikipedia.org/wiki/Table_d%27h%C3%B4te">table_d'hôte</a>/...</span></blockquote>
<div>(each of the above values links to it's wikipedia article; you can see each style's peculiarities) <br></div>
</div><div>
<div>It seems there are others, that's why it's important to leave this as an open set.<br></div><div><br></div><div>The main reason I thought of splitting it into a new tag is because serving styles like buffet and conveyor belt does not necessarily means all-you-can-eat.<br>
</div><div><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-02-15 22:13 GMT-02:00 Fernando Trebien <span dir="ltr"><<a href="mailto:fernando.trebien@gmail.com" target="_blank">fernando.trebien@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+1 for pricing_scheme, +1 against the :opening_hours subtag<br>
<br>
What nounours77 proposes is simpler, easier to map, easier to<br>
understand and easier to consume in applications.<br>
<br>
I also suggest another tag:<br>
serving_system=buffet/smorgasbord/a_la_carte/table_d_hote (read up<br>
that Wikipedia link I've sent previously)<br>
<br>
In extreme cases (e.g. two services with completely different<br>
characteristics - different serving systems, pricing schemes and<br>
cuisines - offered at the same time of the day), if you're really<br>
picky, the best you can do is replicate the mapping of the same<br>
restaurant for each kind of service it offers, each instance with its<br>
own tags. (However, the usual recommendation is to choose the<br>
"primary" values for each tag.)<br>
<br>
I think it's absolutely ok to abbreviate all-you-can-eat by ayce, even<br>
though this is more common in tag names (such as hgv, psv, addr, hov<br>
and ele) than in tag values in OSM. Casual editors (using iD or<br>
Potlatch) would rarely use the tag directly (they can easily get a<br>
friendly named preset or option box, as they do for many tags today)<br>
and advanced users should read the wiki at least once anyway, even for<br>
tags that look deceptively obvious when ignoring the OSM context (e.g.<br>
highway=track, understood differently in many places mainly due to<br>
inexact translation).<br>
<div class="HOEnZb"><div class="h5"><br>
On Sat, Feb 15, 2014 at 6:40 PM, nounours77<br>
<<a href="mailto:kuessemondtaeglich@gmail.com">kuessemondtaeglich@gmail.com</a>> wrote:<br>
> Hi John,<br>
><br>
> I do not understand why this is useful.<br>
><br>
> The suggest tag is too long, to specific.<br>
><br>
> I do not understand the need for a special all_you_can_eat:opening_hours<br>
><br>
>> The problem with "cuisine=all_you_can_eat" is that "All you can eat" is<br>
>> a pricing scheme,<br>
><br>
> If you really think the information about the pricing scheme is relevant (which I don't), why not make a general tag:<br>
><br>
> Pricing_scheme=all_you_can_eat<br>
> Pricing_scheme=daily_menu<br>
><br>
> greetings,<br>
><br>
> nounours77<br>
> _______________________________________________<br>
> Tagging mailing list<br>
> <a href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a><br>
> <a href="https://lists.openstreetmap.org/listinfo/tagging" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
<br>
<br>
<br>
</div></div><div class="im HOEnZb">--<br>
Fernando Trebien<br>
<a href="tel:%2B55%20%2851%29%209962-5409" value="+555199625409">+55 (51) 9962-5409</a><br>
<br>
"The speed of computer chips doubles every 18 months." (Moore's law)<br>
"The speed of software halves every 18 months." (Gates' law)<br>
<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</div></div></blockquote></div><br></div>