<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 9/10/22 21:49, Martin Koppenhoefer
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CABPTjTA9QBYW_GrRkMmSKaxf50UWN24K4XS3UZLzcxcQcOfTFA@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">Am So., 9. Okt. 2022 um
12:22 Uhr schrieb Minh Nguyen <<a
href="mailto:minh@nguyen.cincinnati.oh.us"
moz-do-not-send="true" class="moz-txt-link-freetext">minh@nguyen.cincinnati.oh.us</a>>:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
drinking_water=no is already approved for non-potable water,
and there <br>
are non-Boolean values and drinking_water:legal=* if you'd
like to split <br>
hairs. </blockquote>
<div><br>
</div>
<div><br>
</div>
<div>+1</div>
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">I'd expect that a tag for
fountains and a tag for drinking <br>
fountains would both imply a default value for
drinking_water=* by <br>
default, but the default should be overridden when more is
known about <br>
the water source.<br>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>a tag for drinking fountains should definitely imply
drinking_water=yes,</div>
</div>
</div>
</blockquote>
<p>Agreed. However there is a t least one case where a drinking
fountain carries a sign that it is not suitable for drinking.
Local drink form it anyway and don't seem to suffer from it. I'd
tag it as drinking_water:legal=no and not tag drinking_water=* at
all<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CABPTjTA9QBYW_GrRkMmSKaxf50UWN24K4XS3UZLzcxcQcOfTFA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div> but amenity=fountain should not imply any default value
for "drinking_water", it should be checked and tagged
explicitly. Expectations change around the globe and while
it could be approached with national or regional defaults, I
think it is better to be explicit (because a missing value
is not clear, can be default or unknown, and potability of
water is super important in this context).<br>
</div>
</div>
</div>
</blockquote>
<p><br>
</p>
<p>I would take the safe view, drinking_water=no unless specifically
tagged. <br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CABPTjTA9QBYW_GrRkMmSKaxf50UWN24K4XS3UZLzcxcQcOfTFA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<br>
With a tag for water taps in general, it isn't as clear. But
as a data <br>
consumer or user, I wouldn't be eager to assume that an
outdoor tap is <br>
potable without more context. I've been to cemeteries in
swampy New <br>
Orleans that have taps signposted "Water for Flowers" and
never once <br>
considered that they might be hooked up to the municipal
water system <br>
and maintained to the standard of a public drinking
fountain.<br>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>yes, water taps on cemeteries, as far as I recall, have
been the initial reason for introducing man_made=water_tap
(some people had started mapping amenity=drinking_water
drinking_water=no ;-) )</div>
<div><br>
</div>
</div>
</div>
</blockquote>
<p><br>
</p>
<p>I'd still take the same safe view, drinking_water=no unless
specifically tagged. </p>
<p><br>
</p>
</body>
</html>