<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2015-05-11 09:27, Bryce Nesbitt
wrote :<br>
</div>
<blockquote
cite="mid:CAC9LFPdi+oPtvr5weTdP8sdRAiij7oVn3R4biW_WZOJAmWj_Dg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Sat, May 9, 2015 at 11:31 PM,
Mateusz Konieczny <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:matkoniecz@gmail.com" target="_blank">matkoniecz@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex"><br>
Also, it would break all current data consumers.<br>
</blockquote>
<div><br>
</div>
<div><br>
<br>
I think the concern about data consumers in general is far
higher on this tagging list, then among actual data
consumers.<br>
<br>
</div>
<div>For example: Any decent data consumer needs to process
<b>both</b>:<br>
<br>
</div>
<div><b> phone=XXX<br>
+<br>
</b></div>
<div><b> contact:phone=XXX<br>
</b><br>
</div>
<div>Else they're missing 100,000 data points. So even if
<b>phone</b> was mechanically retagged to<b> contact:phone</b>
(or the other way around) data consumers would<i> not even
notice.</i></div>
</div>
</div>
</div>
</blockquote>
<br>
The problem is that if you don't find a phone number you may miss a
phone call but that if you use wrong access or routing tags you will
instantly have GPSes send cars, bikes or pedestrian on the wrong
road.<br>
It's really difficult to have it understood that GPS software
blindly obeys rules and that tags must also strictly obey the same
rules for the GPSes to work. The many many routing tags errors are
a real PITA. Even wrong instructions in the documentation causing
contributors to be misinformed. Is OSM suitable for GPS ????<br>
<br>
Cheers
<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<br>
</body>
</html>