<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
Examples: either each road is tagged with <tt
style="background:#EEF" dir="ltr" class="mw-content-ltr"><a
href="https://wiki.openstreetmap.org/wiki/Key:maxspeed"><bdi
style="white-space:nowrap"><strong class="selflink">maxspeed</strong></bdi>=*</a>
</tt>speed limit and <a
href="https://wiki.openstreetmap.org/wiki/Key:driving_side"><tt
style="background:#EEF" dir="ltr" class="mw-content-ltr"><bdi
style="white-space:nowrap"><strong class="selflink">driving_side</strong></bdi>=*</tt></a>
or there are defaults.<br>
I'm reviving this remark because the examples are numerous:<br>
<ul>
<li>The Belgian Flemish community wants to tag <tt
style="background:#EEF" dir="ltr" class="mw-content-ltr"><a
href="https://wiki.openstreetmap.org/wiki/Key:maxspeed"><bdi
style="white-space:nowrap"><strong class="selflink">maxspeed</strong></bdi>=*</a></tt>
on every road instead of using a default. Is this a new
specification and where is it written? Must that now be done in
every country?</li>
<li>The current language= proposition wants to do it without
defining defaults. Really? language= on every name= ?</li>
<li>Other examples are maxheight in tunnels. Osmose just accused
me of someone else's omitting maxheight. It shouldn't be
necessary if it's the default, that is if there is no sign for
it, but Osmose likes to yell just in case.<br>
</li>
<li>countless etc.<span class="mw-content-ltr"
style="background:#EEF"><br>
</span></li>
</ul>
Please choose.<br>
<br>
Either the defaults are in the OSM database and it takes just a
routinely map fetch to get them all updated timely,<br>
or each other router (GPS) writer implements them each their own way
from various random other files. It's not well clear how
contributors ca update all those files instead of OSM and it
typically needs a full software update for each little default
change, depending on writer's availability.<br>
<br>
Please choose.<br>
<br>
There is a <a
href="https://wiki.openstreetmap.org/wiki/Proposed_features/Defaults">Proposed_features/Defaults</a>
that puts the defaults in OSM and it's an EXTREMELY HUGE mistake to
have marked such a paramount good work as abandoned because nobody
continued the work. For the sake of OSM, especially routing, please
reopen it.<br>
I don't claim that it is the good solution but I do claim we should
work on such a default database <b>in priority</b>.<br>
<br>
I didn't analyze it in full depth, but I have the following remarks:<br>
- Why not allow the def keyword in the border relation itself? But
it could be called zzdef to cluster at the key end.<br>
- If a separate relation is preferred, it should be pointed at by a
"defaults" role in the corresponding border or other relations so
that it can be found.<br>
- to ease scanning a border tree upwards, a "parent" relation should
exist in border relations.<br>
<br>
In hope of a well structured OSM,<br>
<br>
Cheers
<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<br>
<br>
</body>
</html>