<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div><br></div><div>Oct 11, 2022, 12:27 by dieterdreist@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div><br></div><div><br></div><div dir="ltr">sent from a phone<br></div><div dir="ltr"><div><br></div><blockquote type="cite"><div>On 11 Oct 2022, at 11:30, Davidoskky via Tagging <tagging@openstreetmap.org> wrote:<br></div></blockquote></div><blockquote type="cite"><div dir="ltr"><p>Nobody is tagging the specific model type, such as distinguishing
nasone from the 1960s and nasone from the 1990s.<br></p><p>Should we introduce another key for the style and then tag the
specific model of the fountain style as new_key=nasone,
new_key:model=model_1960?<br></p></div></blockquote><div><br></div><div><br></div><div>I still haven’t discovered the problem with fountain=nasone. If you are not in Rome you will hardly ever come in contact with it, if you are in Rome, you will easily find out what it is about. If you don’t evaluate fountain=nasone in your app, it will gracefully degrade to amenity=drinking_water.<br></div><div><br></div><div>When we tag a “model” it will sooner or later become a geek tag which would indeed distinguish a 60ies from a 90ies nasone :D<br></div></blockquote><div dir="auto">main problems are that either<br></div><div dir="auto"><br></div><div dir="auto">- editor will need to handle specific models as values<br></div><div dir="auto">- this values will be not supported by editors and mappers will use less specific values<br></div><div dir="auto">(this is not a problem if mappers using model values will never, ever complain<br></div><div dir="auto">to mappers using only generic values and will never, ever complain to <br></div><div dir="auto">authors of editing software and noone will suggest adding support for model <br></div><div dir="auto">values in editing software<br></div><div dir="auto"><br></div><div dir="auto">what is impossible to achieve)<br></div><div dir="auto"><br></div><div dir="auto">And also<br></div><div dir="auto">- there is no graceful degradation to "it is drinking fountain"<br></div><div dir="auto">- wiki documentation pages are more confusing as result<br></div> </body>
</html>