<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:130245465;
mso-list-template-ids:875352084;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>This will sound like I’m ranting, and if it does, that’s not my intent. I’m really wanting to help creating additional problems. So . . .<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It won’t help improving and reconciling the non-CT data. But it will keep anyone else from adding (and then losing) data to features slated for deletion. Thinking in terms of a NEW user, who is already facing a steep learning curve to contribute to OSM, and who has by default accepted the new CT, and may not even know about the license change, such a person has every right to expect that his/her contributions will “stick” and not disappear next spring because s/he did not know to look first for whether it is OK to edit something already in the OSM database. “The big we” (the OSM community) do encourage people to edit/correct/update whatever is in the data, if it is incorrect or incomplete, as one of the strengths of our crowd-sourced approach to mapping. It is difficult enough getting people involved without asking them to pay attention to a problem that they did not create but that could come back to bite them. Again, I’m thinking of new users here. Ideally, if someone selects and tries to edit a feature that is subject to deletion or reversion, I would have something pop up with a brief, clear note that this contains “bad data” and should not be edited, but asking the person to create a new node/way based on their own observation, and to feel free to copy any tags that they can confirm from their own observation (for example, it is indeed a Shell station and does indeed sell diesel).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This will involve some programming and some attention to how to explain it. But without something like this, I think that this spring we’re going to lose contributors who don’t know anything about this and really shouldn’t have to, when their contributions disappear. I don’t want that to happen.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Ed Hillsman<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>>Richard Weait</b> <a href="mailto:talk%40openstreetmap.org?Subject=Re%3A%20%5BOSM-talk%5D%20Editing%20of%20content%20that%20will%20be%20deleted%20on%20April%201st&In-Reply-To=%3CCAGwUD5tSCMf%3DqjM5f7RXzQh_poAJAn8VeKwmrTss1Cni_z96UQ%40mail.gmail.com%3E" title="[OSM-talk] Editing of content that will be deleted on April 1st">richard at weait.com </a> wrote<br><i>>Tue Dec 13 18:47:28 GMT 2011</i> <o:p></o:p></p><p class=MsoNormal>><o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><pre>><o:p> </o:p></pre><pre>><o:p> </o:p></pre><pre>>On Tue, Dec 13, 2011 at 1:08 PM, 80n <<a href="http://lists.openstreetmap.org/listinfo/talk">80n80n at gmail.com</a>> wrote:<o:p></o:p></pre><pre>>[ ... ]<o:p></o:p></pre><pre>>><i> Isn't it time to block edits to non-CT content?<o:p></o:p></i></pre><pre>><o:p> </o:p></pre><pre>>And that would allow reconciling and improving that non-CT data how?<o:p></o:p></pre><pre><o:p> </o:p></pre><p class=MsoNormal><o:p> </o:p></p></div></body></html>