<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>On 5/12/2019 8:19 PM, Graeme Fitzpatrick wrote:<br>
</p>
<blockquote type="cite"
cite="mid:CAP4zaXpbaq2qnFUWG+jb8NSdHKr1TJihLC-wuwqMzf78Ucq-Aw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sun, 12 May 2019 at
19:28, Tony Shield <<a
href="mailto:tony.shield999@gmail.com"
moz-do-not-send="true">tony.shield999@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Like the idea.<br>
<br>
delivery_contact might be better.<br>
</blockquote>
<div><br>
</div>
<div>I prefer delivery over contact</div>
<div><br>
</div>
<div>Maybe (using our local companies as an eg) </div>
<div>delivery:ubereats="url"</div>
<div>delivery:menulog="url"</div>
<div>delivery:deliveroo="url"</div>
<div>with "url" in each case being that delivery companies
online menu for that restaurant?</div>
</div>
</div>
</blockquote>
<p>I'm reluctant to recommend the OSM database as the best place to
collect links to the individual restaurant pages of various
delivery services. I prefer this "delivery:partner=*"
recommendation on
<a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Talk:Key:delivery">https://wiki.openstreetmap.org/wiki/Talk:Key:delivery</a> . The value
could be semicoloned, eg
delivery:partner=deliveroo;menulog;ubereats.</p>
<p>And if delivery:*=* is adopted, I'd recommend to start with
delivery:*=yes and make the url optional. (=yes might ultimately
be a better idea... any app who wanted to link to the delivery
services could forward the restaurant name and address to the
service's search url, and we wouldn't have the duty of maintaining
the individual restaurant links for each service. It means the
links wouldn't be available directly from
<a class="moz-txt-link-freetext" href="https://openstreetmap.org">https://openstreetmap.org</a>, but I'm fine with that.)</p>
<p>One weakness of both of these schemes is that there's no obvious
way to indicate that the restaurant also does deliveries itself --
which many of them do, and prefer to do, since they don't have to
give a cut to a dot-com middle man.<br>
</p>
<p>On principal I'm not a fan of giving airtime to these delivery
services because of their predatory behavior -- listing
restaurants without their consent, and squatting on
restaurantname.com websites to steer traffic to their service.
I've complained about these guys in the talk-us list; I'm not sure
if their behavior worldwide is as sleazy as it is here in NYC but
I wouldn't doubt it.</p>
<p>If these proposed tags are used I would strongly recommend that
they be based only on physically (or photographically) verifiable
signage, not just on the fact that a restaurant can be found in
the online database of a given service -- which might be entirely
involuntary, and therefore not, in fact, a verifiable property of
the restaurant itself.</p>
<p>Jason<br>
</p>
</body>
</html>