<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">2013/9/16 Matthijs Melissen <span dir="ltr"><<a href="mailto:info@matthijsmelissen.nl" target="_blank">info@matthijsmelissen.nl</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Dear all,<br><div><br>There are some OpenStreetMap features for which there is no consensus on how to tag them. It does not seem like consensus will arise soon. The lack of consensus does cause problems for the Openstreetmap community, though. Therefore, it would be good to have ideas or procedures on how to create consensus.<br>
<br>There are currently quite a lot of OpenStreetMap features for which there is no consensus on how to tag them. Some examples (but I'm sure there are many more):<br>- What is the difference between highway=footway and highway=path?<br>
- What is the right scheme for tagging public transport?<br></div></div></blockquote><div><br><br></div><div>there is no problem, the solution are additional tags like foot=designated. The 2 public transport schemes can coexist AFAIK. <br>
</div><div><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>- Is an unsurfaced residential road a track?<br></div></div></blockquote><div>
<br><br></div><div>AFAIK there is consensus that a residential road is a residential road aside from the surface qualities and that a track is something different (and could well be paved).<br><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>- Should we use shop=betting or shop=bookmaker?<br></div></div></blockquote><div><br><br></div><div>you can use both<br><br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>- Should we use shop=fishmonger or shop=seafood?<br></div></div></blockquote><div><br><br></div><div>does seafood include fish from fresh water?<br><br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>- Should we use office=estate_agent or shop=estate_agent?<br></div></div></blockquote><div><br><br></div><div>an office is something that doesn't have general access by the public, while a shop would allow you to drop by any time they are open (usually). <br>
<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>
- Should we use shop=tailor or craft=tailor?<br></div></div></blockquote><div><br><br></div><div>you can use both, if its a craftsman. Again, a shop should be publicly accessible, while a craft would not necessarily be accessible without appointment.<br>
<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>The lack of consensus becomes clear by the fact that there are discrepancies between documentation on the wiki, the outcome of a voting, actual use (as documented on Taginfo, for example), and what editors and renderers support.<br>
</div></div></blockquote><div><br><br></div><div>yes, but all of them could deal with the situations. <br><br><br></div><div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
The lack of consensus creates several problems. These problems include the following.<br>- Multiple parallel tagging schemes and unclear documentation creates confusion for newcomers.<br></blockquote><div><br><br>+ <br></div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">- Users are often advised not to follow the documentation on the wiki, and to look at Taginfo instead. This makes the wiki useless. It also leads to the fact that hardly anybody bothers to edit the wiki anymore.<br>
- If mappers should follow current use of tags, then it becomes very hard to introduce new tagging schemes, such as the office= and craft= keys.<br>- Multiple tagging schemes creates problems for the implementation of data users (renderers, routers).<br>
<br>It does not look like consensus on these issues will form naturally, as there many of them exist for multiple years, and I hardly see any initiative to do something about them. Most users seem to accept that there are controversies, instead of trying to come to a solution. I think there is nothing wrong with a temporary period in which two tagging schemes are used in parallel, but permanent lack of consensus creates problems for the community.<br>
<br>Rather than trying to solve the individual cases where there is a lack of consensus, I think we should first try to agree on a procedure on how to solve these issues. For example, we might try to answer the following questions.<br>
- What should be the process to create consensus?<br>- Should we recommend (new) users to follow the wiki, actual usage (Taginfo), or the votings?<br>- Should we recommend data users and editors to follow the wiki, actual usage (Taginfo), or the votings?<br>
- Should the wiki be adapted to actual usage (Taginfo) and/or to votings?<br>- Should we allow automatic edits in simple cases (such as bookmaker versus betting), or leave the process of standardisation to local communities?<br>
</blockquote>
<br>I would like to thank anyone responding in advance for his/her feedback.<br><br>Best regards,<br>Matthijs Melissen<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"></div>
<br>_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Martin Koppenhoefer (Dipl-Ing. Arch.)<br>Via del Santuario Regina degli Apostoli, 18<br><br>00145 Roma<br><br>|llllIllll|llllIllll|llllIllll|llllIllll|llllIllll|llllIllll|llllIllll|llllIllll|<br>
<br>Italia<br>N41.851, E12.4824<br><br>tel1: +39 06.916508070<br>tel2: +49 30 868708638<br>mobil: +39 392 3114712<br>mobil: +49 1577 7793740<br><a href="mailto:mk@koppenhoefer.com" target="_blank">mk@koppenhoefer.com</a><br>
<a href="http://www.koppenhoefer.com" target="_blank">http://www.koppenhoefer.com</a><br><br><br>Hinweis:<br>Diese Nachricht wurde manuell erstellt. Wir bemühen uns um fehlerfreie Korrespondenz, dennoch kann es in Ausnahmefällen vorkommen, dass bei der manuellen Übertragung von Informationen in elektronische Medien die übertragenen Informationen Fehler aufweisen. Wir bitten Sie, dies zu entschuldigen.<br>
<br>Any views or opinions are solely those of the author and do not necessarily represent those of <a href="http://koppenhoefer.com" target="_blank">koppenhoefer.com</a> unless specifically stated.<br>This email and any files attached are confidential and intended solely for the use of the individual or entity to which they are addressed.<br>
If you have received this email in error, please notify <a href="mailto:postmaster@koppenhoefer.com" target="_blank">postmaster@koppenhoefer.com</a><br><br>Please note that to ensure regulatory compliance and for the protection of our clients and business, we may monitor and read messages sent to and from our systems.<br>
<br>Thank You.
</div></div>