<html><head></head><body><div class="gmail_quote">Martin Koppenhoefer <dieterdreist@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr"><div class="gmail_extra"><br /><div class="gmail_quote">2013/10/2 Fernando Trebien <span dir="ltr"><<a href="mailto:fernando.trebien@gmail.com" target="_blank">fernando.trebien@gmail.com</a>></span><br /><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Renderers often don't support life cycle tags, but that doesn't matter because we don't tag for the renderer/applications, right? </blockquote></div><br /><br /></div><div class="gmail_extra">This is nothing particular about renderers or routers, it is generally a flawed approach to add tags like the so-called "life cycle" tags to change the meaning of other tags (e.g. instead of a restaurant you'd express that there once was a restaurant or similar). Opposed to this, the prefixing makes it quite safe to asume that these objects won't be misinterpreted.<br />
<br />I think there is a misconception about what is expressed with the "don't tag for the X" paradigm. The idea behind this is: do not use a tag that is actually rendered (or used in a routing engine) for something different than what the tag was intended for (just to make it appear, or to achieve in certain conditions the same behaviour even if the tag meaning is different). This doesn't imply we have to structure our data in a way that makes the evaluation particularily difficult or easy to get it wrong.<br />
<br /></div><div class="gmail_extra">cheers,<br />Martin<br /></div></div>
<p style="margin-top: 2.5em; margin-bottom: 1em; border-bottom: 1px solid #000"></p><pre class="k9mail"><hr /><br />Tagging mailing list<br />Tagging@openstreetmap.org<br /><a href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a><br /></pre></blockquote></div><br clear="all">I think it makes sense to tag a no-longer-maintained hiking trail in a manner that will still be rendered, but will be rendered in a manner that distinguishes it from an actively-maintained trail. Some portions of a trail may remain visible for centuries, such as a well-built stone retaining wall. Other portions may become impassable within months, due to landslides or fast-growing vegetation. Having both maintained and non-maintained trails marked will reduce the odds of someone accidentally getting onto a non-maintained trail at a junction point, a mistake that can be life-threatening in severe weather.<br>
<br>
-- <br>
John F. Eldredge -- john@jfeldredge.com<br>
"Darkness cannot drive out darkness: <br>
only light can do that.<br>
Hate cannot drive out hate: only love can do that."<br>
Dr. Martin Luther King, Jr.<br>
</body></html>