<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 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
@font-face
{font-family:"Lucida Grande";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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 bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Before moving beyond thin data we need to talk about display and access of thin data. Some members have already expressed their views like you have, but we
need to see if we can reach rough consensus as a WG. We also want to discuss privacy and data protection related to thin data elements before moving to thick elements.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Let me add though, as I shared on the call yesterday, that the leadership team recognizes that we need to move beyond thin data soon so you can expect that
we will.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"> gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org]
<b>On Behalf Of </b>Sam Lanfranco<br>
<b>Sent:</b> Wednesday, January 25, 2017 9:05 AM<br>
<b>To:</b> Stephanie Perrin <stephanie.perrin@mail.utoronto.ca>; Michele Neylon - Blacknight <michele@blacknight.com>; David Cake <dave@davecake.net><br>
<b>Cc:</b> gnso-rds-pdp-wg@icann.org<br>
<b>Subject:</b> [EXTERNAL] Re: [gnso-rds-pdp-wg] Now open: 18 January Poll on Purpose<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">My last comment here (from the balmy shores of Dakar) is:<br>
<br>
Can we close the door on the "thin" data discussion. Stephanie is right when she says deciding what to collect is difference from deciding what to disclose. The purpose of that thin data example is that it violates none of the principles being discussed here.
<br>
<br>
As for what to collect, data is never proposed for collection without some purpose, be that good, bad, legal or illegal. We have had analogies (garbage can lids), example (health data) etc.. Should we get back to simply listing the principles (legal, ethical,
etc.) that should be considered when deciding what to collect, then later on get into the principles that should govern what should be disclosed and under what conditions?<br>
<br>
Sam <o:p></o:p></p>
<div>
<p class="MsoNormal"><i><span style="font-size:10.0pt">On 2017-01-25 11:56 AM, Stephanie Perrin wrote:</span></i><o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p><i><span style="font-family:"Lucida Grande",serif">Sorry, this discussion is important. Your example proves my point. What you show below is a disclosure. It is a disclosure of a limited set of data. we are not supposed to be talking about disclosure
at this point in our proceedings. I leave it to the experts on whether this is "thin" in the sense of the thick transition discussion, I really don't know because we are focused on gTLD policy here. My point is this is a disclosure. We do not "collect"
thin data per se, we collect a whole mess of mandatory data elements, as per the RAA. Then we generate a whole mess as part of activating and making real the domain's existence. Then we share (release) a small subset.
</span></i><o:p></o:p></p>
<p><i><span style="font-family:"Lucida Grande",serif">So talking about collecting thin data is misleading in my view. Purpose of disclosing it is what we are in fact talking about. Calling it a purpose for collection opens the barn door.</span></i><o:p></o:p></p>
<p><i><span style="font-family:"Lucida Grande",serif">Stephanie</span></i><o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>