<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">I would also prefer the transclusion
(template) instead of just links.<br>
<br>
It may be possible to split it up in and a part with more general
tags (e.g. name, ref, operator, distance, ...) that are also used
with other kinds of routes (e.g. for
route=running;bicycle;mtb;horse;piste;inline_skates), so that this
can be used there too, and in a part with hiking/walking specific
tags (e.g. network, educational).<br>
<br>
On 13.08.2019 12:31, Paul Allen:<br>
</div>
<blockquote
cite="mid:CAPy1dO+XUkYu+X4NDjgmgONG5Emy8ygqc9KfQKf38tw1WOHDmA@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">On Tue, 13 Aug 2019 at 09:52, s8evq <<a
moz-do-not-send="true" href="mailto:s8evq@runbox.com">s8evq@runbox.com</a>>
wrote:</div>
<div dir="ltr"><br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote">Would it not be easier and
more clear if we just keep one, and add a link to it in the
others?<br>
</blockquote>
<div><br>
</div>
<div>A principle used in programming is "DRY." Don't repeat
yourself. Maintaining the same</div>
<div>code in two or more places will cause problems down the
line when one version gets</div>
<div>changed and the other does not.</div>
<div><br>
</div>
<div>Documentation is a little different, because you often
wish the same information to appear</div>
<div>in several places. This is the case where the
documentation is extensive but people</div>
<div>assume that everything they need to know about a topic
will appear in one place. OTOH,</div>
<div>the desirability of not repeating yourself increases a
lot when you have many translations</div>
<div>of the material.<br>
</div>
<div><br>
</div>
<div>One way of handling this is a link. Another way of doing
it offered by the wiki is transclusion.</div>
<div>See <a moz-do-not-send="true"
href="https://en.wikipedia.org/wiki/Wikipedia:Transclusion">https://en.wikipedia.org/wiki/Wikipedia:Transclusion</a>
and</div>
<div> <a moz-do-not-send="true"
href="https://en.wikipedia.org/wiki/Wikipedia:Transclusion/How_Transclusion_Works">https://en.wikipedia.org/wiki/Wikipedia:Transclusion/How_Transclusion_Works</a></div>
<div>(the first of those two links transcludes the second of
those links, just so you can see how</div>
<div>it looks).</div>
<div><br>
</div>
<div>There are arguments against each way. If you link to a
full page then the poor user</div>
<div>encountering the link has to wade through that full page
to find the table. If you transclude</div>
<div>then those wishing to edit the page, or even the
transcluded material, may find it</div>
<div>difficult to figure out how to do it. You could, of
course, put the table in its own page and</div>
<div>link to that, which avoids the editing problem and the
information overload problem, but</div>
<div>still means more clicks and page loads are required than
reading a page with a</div>
<div>transclusion.</div>
<div><br>
</div>
<div>Up to you which one you go with. Note that at some point
in the future, somebody may</div>
<div>decide that whichever way you chose to do it was wrong
and edit it to do it differently. :)<br>
</div>
<div><br>
</div>
<div>-- <br>
</div>
<div>Paul</div>
<div><br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
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>
<br>
</body>
</html>