<div dir="ltr"><div dir="ltr">Here is the output of my review for consideration</div><div dir="ltr"><u><br></u></div><div dir="ltr"><u>Community Applications</u><br><br>[1] At page 160, Implementation Guideline 34.3 re: Criterion 1-A Delineation. <br>Although the text draws attention to the need for a non-exhaustive list to include elements applicable to communities that are not economic in nature, it does not explicit touch on 5 other points that I believe the WG discussed, which are:</div><div dir="ltr"><ul><li>Communities that are not economic in nature may not have clear and straight-forward membership definition and this should to not disadvantage such communities in terms of scoring as compared to economic communities with clear and straight-forward membership, that both types of communities should be able to score equally well</li><li>The extremity between "clear and straight-forward membership" scoring high and "vague, dispersed or unbound definition" scoring zero be mediated through an acknowledgment that a grouping without a clear and straight-forward membership but could still be found to be reasonably delineated may still receive a low score instead of zero.</li><li>I also recall that the term "membership" in reference to non-economic communities was problematic</li><li>Where could we explicitly introduce community-related expertise to the CPE process, especially to assist in evaluating non-economic communities for the delineation criterion where "community-related expertise" could be represented by an International Organization specializing in a certain field or a relevant subject matter / community expert of regional or international standing?</li><li>Redress for the requirement of "awareness and recognition of the community by its members" where such awareness and/or recognition could be alternatively provided by community-related expertise, especially in cases where awareness or recognition by the so-called members cannot be properly measured (eg, prevented by national law to recognise something) <br></li></ul>[2] At page 160, Implementation Guidance 34.4 re: the "Organized" element in Criterion 1-A Delineation<br>While the redress for term "mainly" as being permissibly applied to more than one entity appears, redress for the term "administer" does not. I recall having discussed adding the "advocate" verb because an applicant may not fit the role of administrator for a community. I suggest that the reference to "administer" be augmented to "administer or advocate for". Perhaps an alternative might be "represent" instead of "administer" as used in Implementation Guidance 34.8.<br><br>[3] The proposal to increase community participation or input in ICANN's engagement of CPE service provider/panellists is pending further discussion. <br><br>[4] Reference to lowering of the threshold to prevail in CPE, which if I recall correctly was offered by more than one commenter, is omitted. </div><div><br>Thanks,<br>Justine</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 30 Nov 2020 at 23:14, Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank">julie.hedlund@icann.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:11pt">And here are the original attachments for reference.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">Gnso-newgtld-wg <<a href="mailto:gnso-newgtld-wg-bounces@icann.org" target="_blank">gnso-newgtld-wg-bounces@icann.org</a>> on behalf of Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank">julie.hedlund@icann.org</a>><br>
<b>Date: </b>Monday, November 30, 2020 at 10:12 AM<br>
<b>To: </b>"<a href="mailto:gnso-newgtld-wg@icann.org" target="_blank">gnso-newgtld-wg@icann.org</a>" <<a href="mailto:gnso-newgtld-wg@icann.org" target="_blank">gnso-newgtld-wg@icann.org</a>><br>
<b>Subject: </b>[Gnso-newgtld-wg] REMINDER: Review Revised Draft Final Report - DUE Tuesday, 01 December<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11pt">Dear WG Members,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">This is a reminder that the deadline for the review of the revised draft Final Report
<i>for errors and omissions only</i>, if any, is <b><i><u>23:59 UTC on Tuesday, 01 December</u></i></b>. Please see the details below.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Kind regards,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Julie</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">Gnso-newgtld-wg <<a href="mailto:gnso-newgtld-wg-bounces@icann.org" target="_blank">gnso-newgtld-wg-bounces@icann.org</a>> on behalf of Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank">julie.hedlund@icann.org</a>><br>
<b>Date: </b>Monday, November 23, 2020 at 3:04 PM<br>
<b>To: </b>"<a href="mailto:gnso-newgtld-wg@icann.org" target="_blank">gnso-newgtld-wg@icann.org</a>" <<a href="mailto:gnso-newgtld-wg@icann.org" target="_blank">gnso-newgtld-wg@icann.org</a>><br>
<b>Subject: </b>[Gnso-newgtld-wg] Review Revised Draft Final Report - DUE Tuesday, 01 December</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
</div>
<p class="MsoNormal"><span style="font-size:11pt">Dear WG Members</span>,<u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">As noted during the WG meeting on Thursday, 19 November, please see for review the attached revised draft Final Report in Word and PDF, along with the Log of Final Report Action Items and Edits. </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">The redlines in the attached revised draft Final Report reflect the edits made by leadership and support staff in accordance with the
<b>actions agreed to by the WG during the WG meetings</b> held between 17 September and 09 November 2020, as noted in the Log with page references. These actions also were captured during each meeting and circulated to the WG.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">The following topics were covered by the WG in its meetings and addressed in the revised draft Final Report: Community Applications, General Comments, Predictability, Applicant Support, Limited Challenge/Appeal
Mechanism, Applicant Guidebook, Communications, Systems, Application Change Requests, Application Fees, Base Registry Agreement, GAC Early Warning / GAC Consensus Advice, Role of Application Comment, and Objections.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><i><span style="font-size:11pt">Note: In reviewing the revised draft Final Report WG members are requested to limit their review to the referenced pages in the Log and the redlines in the revised draft Final Report, and to focus only
on <u>errors and/or omissions</u>, if any. If any errors/omissions are noted please send them to the
<u>WG email distribution list, referencing the page number and text, respectively</u>.</span></i></b><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Please submit comments to the list, if any, not later than
<b><i><u>23:59 UTC on Tuesday, 01 December</u></i></b>.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Kind regards,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Julie</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt">Julie Hedlund, Policy Director</span><u></u><u></u></p>
</div>
</div>
_______________________________________________<br>
Gnso-newgtld-wg mailing list<br>
<a href="mailto:Gnso-newgtld-wg@icann.org" target="_blank">Gnso-newgtld-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a><br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote></div></div>