<html><head></head><body><div class="ydpba3f2df6yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div><div>Dennis, </div><div><br></div><div>I'm not saying that the methodologies we have developed are flawed. I am saying that they are <i>limited</i>. </div><div><br></div><div>There is some set of code points which are variants. Each methodology we have can identify some subset of those variants -- but not all of them. That is, after all, why we have developed multiple methodologies. <span><span style="color: rgb(0, 0, 0); font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 16px;">Our task, I submit, is not to process our methodologies; our task is to identify variants. The methodologies are a means to that end; they are not the end itself. </span></span></div><div><br></div><div>I believe we need to bear in mind that the methodologies which we have at this point may still not be sufficient to identify all of the variants which exist. We need to accept that, if we find code points which we generally agree are variants, but which are not identified by our existing methodologies, that is not a bad thing. It would be good to then identify why they are variants, in the interests of then finding others of the same type; to develop an additional methodology. Good, but not critical. </div><div><br></div><div>The quality of our work product is determined by how successfully we identify the variants which exist. If we find variants which are not generated by our methodologies, that improves the quality of our work. It does not, as you appeared to suggest, diminish it. </div><div><br></div><div>What I suggest the panel do is remain open to the possibility (I would say the certainty) that we have not yet created methodologies which will identify all variants. At some point, of course, we do have to stop. But that doesn't justify just saying "These code points do not fit the existing methodologies, so we cannot even consider them." Again, the methodologies are a tool, not an end.</div><div><br></div><div><br></div><div class="ydpba3f2df6signature">Bill Jouris<br>Inside Products<br>bill.jouris@insidethestack.com<br>831-659-8360<br>925-855-9512 (direct)</div></div>
<div><br></div><div><br></div>
</div><div id="ydp17a82f68yahoo_quoted_1245104190" class="ydp17a82f68yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Friday, February 22, 2019, 10:23:19 AM PST, Tan Tanaka, Dennis <dtantanaka@verisign.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="ydp17a82f68yiv9230238646"><div>
<div class="ydp17a82f68yiv9230238646WordSection1">
<p class="ydp17a82f68yiv9230238646MsoNormal">Bill,</p>
<p class="ydp17a82f68yiv9230238646MsoNormal"> </p>
<p class="ydp17a82f68yiv9230238646MsoNormal">I don’t see how the methods this panel have developed and signed-off on (some of them over a year ago) misalign with our goal.</p>
<p class="ydp17a82f68yiv9230238646MsoNormal"> </p>
<p class="ydp17a82f68yiv9230238646MsoNormal">What exactly are you suggesting this panel to do?</p>
<p class="ydp17a82f68yiv9230238646MsoNormal"> </p>
<p class="ydp17a82f68yiv9230238646MsoNormal">-Dennis</p>
<p class="ydp17a82f68yiv9230238646MsoNormal"> </p>
<div class="ydp17a82f68yiv9230238646yqt7430687659" id="ydp17a82f68yiv9230238646yqt92251"><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in;">
<p class="ydp17a82f68yiv9230238646MsoNormal" style="margin-left:.5in;"><b><span style="font-size:12.0pt;color:black;">From:
</span></b><span style="font-size:12.0pt;color:black;">Latingp <latingp-bounces@icann.org> on behalf of Bill Jouris <bill.jouris@insidethestack.com><br clear="none">
<b>Reply-To: </b>Bill Jouris <bill.jouris@insidethestack.com><br clear="none">
<b>Date: </b>Thursday, February 21, 2019 at 5:36 PM<br clear="none">
<b>To: </b>Latin GP <latingp@icann.org><br clear="none">
<b>Subject: </b>[EXTERNAL] [Latingp] Work Product Quality</span></p>
</div>
<div>
<p class="ydp17a82f68yiv9230238646MsoNormal" style="margin-left:.5in;"> </p>
</div>
<div>
<div id="ydp17a82f68yiv9230238646ydpc1b8a037yiv0434286997">
<div id="ydp17a82f68yiv9230238646ydpc1b8a037yiv0434286997yMail_cursorElementTracker_1550769559181">
<p class="ydp17a82f68yiv9230238646MsoNormal" style="margin-left:.5in;"><span style="font-size:12.0pt;">Dear colleagues, </span></p>
</div>
<div id="ydp17a82f68yiv9230238646ydpc1b8a037yiv0434286997yMail_cursorElementTracker_1550769568898">
<p class="ydp17a82f68yiv9230238646MsoNormal" style="margin-left:.5in;"><span style="font-size:12.0pt;"> </span></p>
</div>
<div id="ydp17a82f68yiv9230238646ydpc1b8a037yiv0434286997yMail_cursorElementTracker_1550769569135">
<p class="ydp17a82f68yiv9230238646MsoNormal" style="margin-left:.5in;"><span style="font-size:12.0pt;">I want to strongly disagree with the thesis put forward at this morning's meeting that the quality of our work product depends on our following some very
small number of discrete methodologies for identifying variants. It does not. </span></p>
</div>
<div id="ydp17a82f68yiv9230238646ydpc1b8a037yiv0434286997yMail_cursorElementTracker_1550769656752">
<p class="ydp17a82f68yiv9230238646MsoNormal" style="margin-left:.5in;"><span style="font-size:12.0pt;"> </span></p>
</div>
<div id="ydp17a82f68yiv9230238646ydpc1b8a037yiv0434286997yMail_cursorElementTracker_1550769656931">
<p class="ydp17a82f68yiv9230238646MsoNormal" style="margin-left:.5in;"><span style="font-size:12.0pt;">A methodology, any methodology, is merely a tool. Its purpose is to help us get to our goal -- identifying variants. If we use multiple methodologies,
each of which allows us to identify some (quite possibly overlapping) subset of the universe of variants, that's OK. If we identify a few additional cases that we believe to be variants, while going outside those methodologies, that's OK too. It is desirable
to have methodologies which identify large subsets, but <i>only</i> because that expedites our work. The methodologies are a means to an end, not the end in themselves. </span></p>
</div>
<div id="ydp17a82f68yiv9230238646ydpc1b8a037yiv0434286997yMail_cursorElementTracker_1550769857286">
<p class="ydp17a82f68yiv9230238646MsoNormal" style="margin-left:.5in;"><span style="font-size:12.0pt;"> </span></p>
</div>
<div id="ydp17a82f68yiv9230238646ydpc1b8a037yiv0434286997yMail_cursorElementTracker_1550769857497">
<p class="ydp17a82f68yiv9230238646MsoNormal" style="margin-left:.5in;"><span style="font-size:12.0pt;">The quality of our work product is based on how successfully we identify the members of the underlying universe of variants. How we get there is really
irrelevant to the quality of what we produce.</span></p>
</div>
<div id="ydp17a82f68yiv9230238646ydpc1b8a037yiv0434286997">
<p class="ydp17a82f68yiv9230238646MsoNormal" style="margin-left:.5in;"><span style="font-size:12.0pt;"> </span></p>
</div>
<div id="ydp17a82f68yiv9230238646ydpc1b8a037yiv0434286997">
<p class="ydp17a82f68yiv9230238646MsoNormal" style="margin-left:.5in;"><span style="font-size:12.0pt;"> </span></p>
</div>
<p class="ydp17a82f68yiv9230238646MsoNormal" style="margin-left:.5in;"><span style="font-size:12.0pt;">Bill Jouris </span></p>
</div>
<div id="ydp17a82f68yiv9230238646ydpc1b8a037yiv0434286997">
<p class="ydp17a82f68yiv9230238646MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.5in;">
<span style="font-size:12.0pt;"> </span></p>
<div id="ydp17a82f68yiv9230238646ydpc1b8a037yiv0434286997ymail_android_signature">
<p class="ydp17a82f68yiv9230238646MsoNormal" style="margin-left:.5in;"><span style="font-size:12.0pt;"><a shape="rect" href="https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature" rel="nofollow" target="_blank">Sent
from Yahoo Mail on Android</a></span></p>
</div>
</div>
</div></div>
</div>
</div></div></div>
</div>
</div></body></html>