<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>7 Jul 2021, 14:38 by bert.araali.afritastic@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><p><span class="font" style="font-family:Verdana"> If there is really a need to describe or use specific
terms one can use description=* or even in some cases one of the
name keys.</span><br></p></blockquote><div dir="auto">No, as it blocks any automatic processing.<br></div><div dir="auto"><br></div><div dir="auto">There is a good reason why we have</div><div dir="auto">highway=motorway not a freeform</div><div dir="auto">description tag.</div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><p><span class="font" style="font-family:Verdana"> - a caponier is a building and a trench </span><span class="font" style="font-family:Verdana">historic=building, highway=footway, cutting=yes,
trench=* again with </span><span class="font" style="font-family:Verdana"><span class="font" style="font-family:Verdana">description and use the Wikidata and Wikipedia
keys for more context;</span></span><br></p></blockquote><div dir="auto">If someone is interested in that then <br></div><div dir="auto">allowing to identify them in OSM is 100% fine</div><div dir="auto">(I assume that it is verifiable to map them)</div><div dir="auto"><br></div><div dir="auto">Expecting to parse external resources <br></div><div dir="auto">(often on incompatible licences) is not</div><div dir="auto">a comparable solution.</div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="auto"><span class="font" style="font-family:Verdana"><span class="font" style="font-family:Verdana"> - a cavalier is just a building with more levels, enough tags
(hsitoric, building, ruins, building:levels etc...) to tag
those </span></span><span class="font" style="font-family:Verdana">again with </span><span class="font" style="font-family:Verdana"><span class="font" style="font-family:Verdana">description and use the
Wikidata and Wikipedia keys for more context;</span></span><br></div></blockquote><div dir="auto">Freeform text and external resources is</div><div dir="auto">not comparable solution.</div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><p><span class="font" style="font-family:Verdana">Our wiki says explicitly about historical
key:</span><br></p><p><span class="font" style="font-family:Verdana">where the contributor prefers to define the
type of structure in additional tags, then it is possible to use
a generic value for the tag historic=*.</span><br></p></blockquote><div dir="auto">Proposal process is one of tools to create new<br></div><div dir="auto">tagging schemes, not yet described at Wiki.</div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="auto"><span style="font-family: Verdana;">we
also have heritage=*</span><br></div></blockquote><div dir="auto">That gives no info about type of an object</div><div dir="auto">(except indirect pointer to a sometimes useful</div><div dir="auto">database)</div> </body>
</html>