<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 10pt; color: #000000'>HI Corinna,<div><br></div><div>I think that it's good that we are going through a review of the policy. My comments are more of suggestions for clarity and understanding.</div><div><br></div><div>The EDI default text based on CC0 at first does not seem that different from CC BY - Attribution. It's not until you try to figure out the differences that under CC By- Attribution a data user must give appropriate credit and indicate if changes are made. While for CC0 ".. <span style="color: rgb(34, 34, 34); font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 14px; line-height: 20px; background-color: rgb(255, 255, 255);">there is no legal requirement that you attribute the affirmer, only an expectation that you will voluntarily do so if requested."</span><span style="font-size: 10pt;"> </span></div><div><span style="font-size: 10pt;"><br></span></div><div>So I would suggest for the wording of the policy for the default text following "No Rights Reserved" that the attribution is requested but voluntary. Otherwise data providers may have false expectations.</div><div><br></div><div>Thanks,</div><div><br></div><div>Jim</div><div><br></div><div><br></div><div><br><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Corinna Gries" <cgries@wisc.edu><br><b>To: </b>im@lternet.edu<br><b>Sent: </b>Tuesday, March 7, 2017 3:43:56 PM<br><b>Subject: </b>[LTER-im] LTER Data Access Policy Request for Comments<br><br>
<style><!--
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
<div class="WordSection1">
<p class="MsoNormal">Dear all,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">To work through issues that may require some changes to LTER data management practices we would like to employ a process of requesting comments from all of you.
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">We are starting with the LTER Data Access Policy. Background, reasons for changing it, and recommendations are outlined in the attached document. Please either discuss on this list, send your comments, concerns, questions to IMexec or directly
to Corinna <a href="mailto:cgries@wisc.edu" target="_blank">cgries@wisc.edu</a> before April 15<sup>th</sup>. If there is enough time this discussion will also be part of the agenda for the next Water Cooler.
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">We will collate all of the comments and formulate recommendations based on those comments to send to the EB before the Science Council meeting in May.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">The same request for comments will go out the LTERexec mailing list. Please discuss with your PIs.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">EDI and NCO</p>
<p class="MsoNormal"> </p>
</div>
<br>_______________________________________________<br>Long Term Ecological Research Network<br>im mailing list<br>im@lternet.edu<br><br></div><br></div></div></body></html>