<div dir="ltr"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div dir="ltr">Le lun. 17 déc. 2018 à 14:26, Sergio Manzi <<a href="mailto:smz@smz.it">smz@smz.it</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">Sorry, I didn't meant to be rude in any way: I just assumed you
were the one who introduced the switch=* key for power lines (<i>and
apparently I was wrong, you just "expanded" the information
about those...)</i></div></blockquote><div><br></div><div>Me neither, switch=* was firstly de facto used and then documented on wiki with a proposal.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">Bingo. Now try substituting the "="
sign with the ":" sign</div></blockquote><div><br></div><div>This would be redundant with railway=switch and power=switch :)</div><div>Be sure I'll be blamed for that just like I'm blame to don't use namespaces.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">
<div class="gmail-m_5908030686772758089moz-cite-prefix">
</div>
<div class="gmail-m_5908030686772758089moz-cite-prefix">If you do the same inside an objects
description, an editor or data consumer could instantly "<i>route</i>"
you to the relevant documentation when you are inspecting that
particular object (<i>either a railway switch or a power switch</i>).</div></div></blockquote><div>Editors like JOSM have context=x" concept to make the distinction.</div><div><a href="https://josm.openstreetmap.de/wiki/TaggingPresets#Attributes">https://josm.openstreetmap.de/wiki/TaggingPresets#Attributes</a><br></div><div>JOSM maintainers told me they prefer actuator=* as it's more simpler to type and users don't have to be annoyed with that.<br></div><div>I understand that editors have more work to do to deal with such generic keys, but editors should help users and not the contrary shouldn't you ?<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">
<div class="gmail-m_5908030686772758089moz-cite-prefix">
</div><div class="gmail-m_5908030686772758089moz-cite-prefix">Yes, the context (<i>either we find the
"switch" keyword inside the definition of a power line, a
railway or a network</i>) can imply the lexical scope of the
keyword, and most of the times that's self-evident for us humans,
but it is a lot more difficult to <i>teach </i>to a program.<br></div></div></blockquote><div>That's not so clear depending on which editor maintainer you ask.</div><div>Processors have to deal with tags associations, namespaces won't prevent them to be smart anyway i'm affraid.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><div class="gmail-m_5908030686772758089moz-cite-prefix">
</div>
<blockquote type="cite">
<div>Then actuator is an attribute of several kind of objects
(pipeline=valve and eventually railway=switch), just like
location.</div>
<div>I don't get where I confuse something between actuator=* like
tags and location=*<br>
</div>
</blockquote>
<p>Here is where I think you make the mistake.</p>
<p>The actuator is <u><b>not an attribute</b></u> of the things
(pipeline=valve and eventually railway=switch), but a <b>part/element</b>
of them.</p>
<p>Someone someday may be wishing to further describe actuators in
their own details/attributes, like now you are doing for valves
which are parts/elements of a pipeline.<br></p></div></blockquote><div>Currently it is an actual attribute for sake of simplicity for contribution and inventory, because we consider the system {valve + actuator}.<br></div><div><br></div><div>Then in eventual future, we will need another node to separate the actuator from the valve and a way connecting the valve and the actuator to map the mechanical link.</div><div>That should be done for transformers on top of poles, antennas on top of a mast, windows on a given house and so on...<br></div></div><div class="gmail_quote"><a href="https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element">https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element</a><br></div><div class="gmail_quote"><br></div><div class="gmail_quote">By the way I apreciate the discussion and this certainly improve the knowledge about tagging possibilities and principles.</div><div class="gmail_quote"><br></div><div class="gmail_quote">François<br></div></div></div></div>