<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hi, this issue does pop up on the mailing lists sometimes.</div><div class="">Here are my thoughts from the last time: <a href="https://lists.openstreetmap.org/pipermail/tagging/2015-June/025438.html" class="">https://lists.openstreetmap.org/pipermail/tagging/2015-June/025438.html</a></div><div class=""><br class=""></div><div class="">To recap, here is what I would and would not support in iD:</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">- I would not support arbitrary free-text warning messages popping up as users try to edit things. This is too susceptible for abuse.</div><div class=""><br class=""></div><div style="widows: 1;" class=""><br class=""></div><div style="widows: 1;" class="">- I would support a standardized tag scheme that lets us warn a mapper about conditions that anybody would understand. <span style="widows: 1;" class="">These warnings would have very narrow scope and attach to areas. We would translate them to a user’s native language.</span></div><div class="">e.g. </div><div class="">`editor:warning=outdated_imagery`</div><div class=""><i class=""> “Imagery in this area may be outdated. Please do not make edits without local knowledge."</i></div><div class=""><div style="widows: 1;" class="">`editor:warning=border_dispute`</div></div><div style="widows: 1;" class=""><i class=""> “There is an ongoing border dispute in this area. Please do not make edits without local knowledge."</i></div><div style="widows: 1;" class="">`editor:warning=current_event`</div><div style="widows: 1;" class=""><div style="widows: auto;" class=""><div style="widows: 1;" class=""><i class=""> “A current event may have affected ground conditions in this area. Please do not make edits without local knowledge."</i></div><div class=""><br class=""></div></div></div><div style="widows: 1;" class=""><br class=""></div><div style="widows: 1;" class="">- I would support a standardized tag scheme that lets us restrict certain edits. </div><div style="widows: 1;" class="">(with the caveat that a determined user could remove the tag and edit the thing anyway).</div><div style="widows: 1;" class="">e.g. </div><div style="widows: 1;" class="">`editor:restriction=authoritative_data`</div><div style="widows: 1;" class="">`editor:restriction:source=<a href="http://nyc.gov" class="">nyc.gov</a>`</div><div style="widows: 1;" class=""><i class=""> “You may not move this item because its position has been surveyed with high accuracy."</i></div><div style="widows: 1;" class=""><br class=""></div><div style="widows: 1;" class=""><br class=""></div><div style="widows: 1;" class="">- I would support API-based restrictions (if the OSM API supported such a thing, which it doesn't), e.g. to counter abuse, edit wars, vandalism. We already poll the `/api/capabilities` endpoint every few minutes, so maybe it makes sense to stick API-based editing restrictions in there.</div><div style="widows: 1;" class="">e.g.</div><div style="widows: 1;" class=""><div class=""><i class=""> “Editing in this location is currently unavailable due to high amounts of vandalism."</i></div><div class=""><br class=""></div></div><div style="widows: 1;" class=""><br class=""></div><div style="widows: 1;" class="">Anyway feel free to discuss here, or on the iD issue list: :-)</div><div style="widows: 1;" class=""><a href="https://github.com/openstreetmap/iD/issues" class="">https://github.com/openstreetmap/iD/issues</a></div><div style="widows: 1;" class=""><br class=""></div><div style="widows: 1;" class=""><br class=""></div><div class="">Thanks, Bryan</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 26, 2015, at 4:43 PM, moltonel <<a href="mailto:moltonel@gmail.com" class="">moltonel@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><br class=""><br class="">On 26 September 2015 19:05:09 GMT+01:00, "André Pirard" <<a href="mailto:a.pirard.papou@gmail.com" class="">a.pirard.papou@gmail.com</a>> wrote:<br class=""><blockquote type="cite" class="">It is<br class=""><keyname>:warning=<text><br class="">which acts only when that key is changed.<br class="">geometry:warning=<text> to protect the coordinates of the element<br class="">name:warning=<text> to protect its name.<br class="">Those tags do not warn against changing other tags.<br class=""></blockquote><br class="">May I suggest 'edit_warning', or something else that explicit (because a 'warning' key could be used for so many purposes) ? And use proper namespace ordering, ie edit_warning:name=blah rather than name:edit_warning=blah (because many keys, like name or phone, are also namespaces that can be followed by arbitrary sufixes).<br class=""><br class="">That said, you should open bugs on the various editors as soon as possible to discuss with them what they think of such a feature. Unless this tag gets editor support, it doesn't bring anything that the already popular 'note' tag doesn't give. Sadly, inexperienced mapers are the ones most likely to miss a plain 'note' tag, but they are also most likely using iD, whose developers are pretty warning-averse...<br class="">-- <br class="">Vincent Dp<br class=""><br class="">_______________________________________________<br class="">Tagging mailing list<br class=""><a href="mailto:Tagging@openstreetmap.org" class="">Tagging@openstreetmap.org</a><br class="">https://lists.openstreetmap.org/listinfo/tagging<br class=""></div></blockquote></div><br class=""></body></html>