<div dir="auto">Breaking change come with a cost.<div dir="auto">Whether it is worth is a question should be asked.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">在 2020年10月19日週一 21:04，Dave F via Tagging <<a href="mailto:tagging@openstreetmap.org">tagging@openstreetmap.org</a>> 寫道：<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Irrelevant of any implied meaning, 'man_made' always appeared to be
a clunky, catch-all tag. OSM was being a bit lazy.<br>
I mean, *everything* is either man made or natural. We really
should come up with more specific, accurate key tags.<br>
<br>
DaveF <br>
<br>
<div>On 19/10/2020 12:45, Jo wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">It would be best to first consider the consequences
of such a change. Weigh the benefits against what we lose in
time (humanhours?) and resources/energy. And then there is still
the point that many objects will get new timestamps for a change
that's not really a change.
<div><br>
</div>
<div>Anyway, artificial sounds like made up to me.
artificial=dyke, not really a dyke, but it looks like it.</div>
<div><br>
</div>
<div>man_made has the advantage of being succinct. Most people
will immediately understand what is meant by it. Almost nobody
will think women were not involved in the creation of the
feature.</div>
<div><br>
</div>
<div>Polyglot</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Oct 19, 2020 at 12:42
PM Robert Delmenico <<a href="mailto:robert@rtbk.com.au" target="_blank" rel="noreferrer">robert@rtbk.com.au</a>>
wrote:<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 dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div>Nice investigating Nathan,</div>
<div><br>
</div>
<div>I would be open to using artificial instead of
human_made.</div>
<div><br>
</div>
<div><br>
</div>
<div>Would it be best to change the proposal or start
a second proposal?</div>
<div>Change man_made= to artificial=</div>
<div><br>
</div>
<div>Rob</div>
</div>
</div>
</div>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, 19 Oct 2020 at
21:14, nathan case <<a href="mailto:nathancase@outlook.com" target="_blank" rel="noreferrer">nathancase@outlook.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Pros and cons aside,
“human-made” is not a term that is in current widespread
usage. As a native English GB speaker, I find it clunky
and somewhat distracting.<br>
<br>
A better gender neutral term might be “artificial”, which
is already a synonym for “man-made” and is already widely
used. <br>
<br>
Indeed, the Handbook of Nonsexist Writing suggests:
"artificial, handmade, hand-built, synthetic,
manufactured, fabricated, machine-made, and constructed"
as options instead of man-made. Presumably the majority
(if not all) of OSM "man-made" tags relate to objects
which are not naturally occurring. Therefore "artificial"
seems to hold.<br>
<br>
Other sources: <br>
<a href="https://writingcenter.unc.edu/tips-and-tools/gender-inclusive-language/" rel="noreferrer noreferrer" target="_blank">https://writingcenter.unc.edu/tips-and-tools/gender-inclusive-language/</a>
<br>
<a href="https://www.chicagomanualofstyle.org/qanda/data/faq/topics/Usage/faq0053.html" rel="noreferrer noreferrer" target="_blank">https://www.chicagomanualofstyle.org/qanda/data/faq/topics/Usage/faq0053.html</a><br>
<a href="https://dictionary.cambridge.org/dictionary/english/man-made" rel="noreferrer noreferrer" target="_blank">https://dictionary.cambridge.org/dictionary/english/man-made</a><br>
<br>
An issue may arise if artificial is already being used as
a tag however.<br>
<br>
Best,<br>
<br>
Nathan<br>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank" rel="noreferrer">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote>
</div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank" rel="noreferrer">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Tagging mailing list
<a href="mailto:Tagging@openstreetmap.org" target="_blank" rel="noreferrer">Tagging@openstreetmap.org</a>
<a href="https://lists.openstreetmap.org/listinfo/tagging" target="_blank" rel="noreferrer">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
<br>
</div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank" rel="noreferrer">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div>