<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Yeah. The "<i>other</i>" solution could be to "<i>namespace
everything</i>", so you could tag
building:whatever_property_key_you_want and
amenity:whatever_property_key_you_want, applied to the very same
object. But we're probably too late for that and apparently many
seems to hate this latter solution.<br>
</p>
<div class="moz-cite-prefix">On 2019-02-16 23:59, Martin
Koppenhoefer wrote:<br>
</div>
<blockquote type="cite"
cite="mid:8CC77989-A7EB-41E3-AD34-B4F8473BA121@gmail.com">
<pre class="moz-quote-pre" wrap="">
sent from a phone
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On 16. Feb 2019, at 23:49, Anton Klim <a class="moz-txt-link-rfc2396E" href="mailto:tohaklim@gmail.com"><tohaklim@gmail.com></a> wrote:
Like in the thread opening email, where there is an amenity that occupies the whole building, we put amenity tags on the outline.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
I agree with Serge here, when there is a problem where it is not clear to what the tags refer, it is usually a modeling problem of mixing different things up in one object, and a better solution than creating more specific tags by prefixing them, would be to fix the model. It will not end at start_date ;-)
Cheers, Martin
_______________________________________________
Tagging mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
</body>
</html>