<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 24/05/2015 5:10 PM, Bryce Nesbitt
wrote:<br>
</div>
<blockquote
cite="mid:CAC9LFPczrK54HRMord2GjG-JzPKug93vrXCkeVhpRJ_xOa=77g@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Fri, May 22, 2015 at 5:02 AM,
Blake Girardot <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:bgirardot@gmail.com"
target="_blank">bgirardot@gmail.com</a>></span>
wrote:
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
The intention of the damage:event=* or maybe
disaster:event=* tag doesn't have much to do with
assigning causation, and has more to do with tag
maintenance. We want to be able to run projects that get
objects that were tagged with an event related tag to
review, revise or remove them.</blockquote>
<div><br>
</div>
<div>But why put that node/way status in the OSM dataset
itself, rather than in a HOT tasking manager.<br>
</div>
</div>
</div>
</div>
</blockquote>
Because it become available to others .. like the government/local
authorities who may be in charge of repairs? <br>
</body>
</html>