<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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Arial",sans-serif;
color:black;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:47266501;
mso-list-template-ids:-1353790424;}
@list l0:level2
{mso-level-start-at:2;
mso-level-number-format:alpha-lower;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1
{mso-list-id:412314485;
mso-list-template-ids:-2095535472;}
@list l1:level2
{mso-level-start-at:3;
mso-level-number-format:alpha-lower;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level3
{mso-level-start-at:3;
mso-level-number-format:roman-lower;
mso-level-tab-stop:108.0pt;
mso-level-number-position:right;
text-indent:-18.0pt;}
@list l2
{mso-list-id:916672541;
mso-list-template-ids:-2084424764;}
@list l2:level2
{mso-level-start-at:3;
mso-level-number-format:alpha-lower;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l2:level3
{mso-level-start-at:2;
mso-level-number-format:roman-lower;
mso-level-tab-stop:108.0pt;
mso-level-number-position:right;
text-indent:-18.0pt;}
@list l3
{mso-list-id:1314288645;
mso-list-template-ids:2079243966;}
@list l3:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l4
{mso-list-id:1355497512;
mso-list-template-ids:305056790;}
@list l4:level2
{mso-level-start-at:2;
mso-level-number-format:alpha-lower;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l4:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:108.0pt;
mso-level-number-position:right;
text-indent:-18.0pt;}
@list l5
{mso-list-id:1477868903;
mso-list-template-ids:1382598288;}
@list l6
{mso-list-id:1928345693;
mso-list-template-ids:514899080;}
@list l6:level2
{mso-level-start-at:3;
mso-level-number-format:alpha-lower;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l6:level3
{mso-level-start-at:4;
mso-level-number-format:roman-lower;
mso-level-tab-stop:108.0pt;
mso-level-number-position:right;
text-indent:-18.0pt;}
@list l7
{mso-list-id:1949580947;
mso-list-type:hybrid;
mso-list-template-ids:532073110 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l7:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l7:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l7:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l7:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l7:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l7:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l7:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l7:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l7:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l8
{mso-list-id:2081829294;
mso-list-template-ids:894856384;}
@list l8:level2
{mso-level-start-at:3;
mso-level-number-format:alpha-lower;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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-GB" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-US">Thanks Jeff<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-US">If there is strong support in the WG to move away from the recommendation (option 1) then this should be to adopt option 2 instead, and
I support Donna’s reasoning. Brand effectively are not a singular/plural of the corresponding word since they do not operate in the dictionary sense. Further, the closely controlled registration and use provisions under Spec 13 ensure that the dotBrand registry
operator is readily able to maintain responsibility for the use of second level names in the TLD.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Susan Payne<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Head of Legal Policy<b><br>
Com Laude | Valideus</b><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">E:
<a href="mailto:susan.payne@comlaude.com">susan.payne@comlaude.com</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org>
<b>On Behalf Of </b>Donna@registry.godaddy<br>
<b>Sent:</b> 04 December 2020 19:11<br>
<b>To:</b> Jeff Neuman <jeff@jjnsolutions.com>; gnso-newgtld-wg@icann.org<br>
<b>Subject:</b> Re: [Gnso-newgtld-wg] Fourth Topical Questions: String Similarity Outstanding Questions<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">Hi Jeff, all<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Leaning toward <i>2. Ban the co-existence of Singulars and Plurals except for where either one or both of the strings are a Specification 13 (Brand TLD).</i><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">There is a reasonable case to be made that ‘brands’ are readily discernible by users as highlighted by the examples in your email below and as such do not represent the same challenges for user confusion and trying to
hold a TLD operator to registrations that are consistent with the intended use of the TLD.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Donna<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Donna Austin<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Head of Registry Policy<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">GoDaddy Registry<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Gnso-newgtld-wg <<a href="mailto:gnso-newgtld-wg-bounces@icann.org">gnso-newgtld-wg-bounces@icann.org</a>>
<b>On Behalf Of </b>Jeff Neuman<br>
<b>Sent:</b> Thursday, December 3, 2020 9:45 AM<br>
<b>To:</b> <a href="mailto:gnso-newgtld-wg@icann.org">gnso-newgtld-wg@icann.org</a><br>
<b>Subject:</b> [Gnso-newgtld-wg] Fourth Topical Questions: String Similarity Outstanding Questions<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid #A6A6A6 4.5pt;padding:0cm 0cm 0cm 14.0pt">
<p class="MsoNormal" style="background:#EBEBEB"><span lang="EN-US" style="font-size:9.0pt;font-family:"Tahoma",sans-serif;color:black">Notice:</span><span lang="EN-US" style="color:black">
</span><span lang="EN-US" style="font-size:9.0pt;font-family:"Tahoma",sans-serif;color:black">This email is from an external sender.
</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<p><span lang="EN-US"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">All,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">This is the <u>Fourth topical E-mail</u> on outstanding questions being “put to the list.” The first was on Predictability, second on Applicant Support, third was the Guidebook, and this covers string similarity (Topic
24).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Remember: We are down to the wire on this, so unless you have a VERY strong objection to these, we will put these into the document. If you do have a big issue with the responses to these (all of which were previously
discussed and in emails over the past 1.5 months), please let us know ASAP. Only comments that provide the rationale for the objection with proposed replacement text to address the specific outstanding questions will now be considered.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Lets not let the perfect be the enemy of the good.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l7 level1 lfo3"><u><span lang="EN-US">Intended Use Comments</span></u><span lang="EN-US">
<o:p></o:p></span></li></ol>
<ol style="margin-top:0cm" start="1" type="1">
<ol style="margin-top:0cm" start="1" type="a">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l7 level2 lfo3"><u><span lang="EN-US">Comments</span></u><span lang="EN-US">: Some commenters have expressed concerns about Recommendation 24.3 in that it calls for an evaluation of the “intended
use” of an applied-for string to determine whether terms that appear to be the singular/plural of each other will be allowed to co-exist (our paraphrasing).<o:p></o:p></span></li></ol>
</ol>
<p class="MsoListParagraph" style="margin-left:72.0pt"><span lang="EN-US"> <o:p></o:p></span></p>
<ol style="margin-top:0cm" start="1" type="1">
<ol style="margin-top:0cm" start="2" type="a">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l7 level2 lfo3"><u><span lang="EN-US">WG Recommendations</span></u><span lang="EN-US"><o:p></o:p></span></li></ol>
</ol>
<p class="MsoListParagraph"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-108.0pt;mso-text-indent-alt:-9.0pt;mso-list:l7 level3 lfo3">
<![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman"">
</span>i.<span style="font:7.0pt "Times New Roman""> </span></span></span><![endif]><u><span lang="EN-US">Recommendation 24.3.</span></u><span lang="EN-US"> …Specifically, the Working Group recommends prohibiting plurals and singulars of the same word
within the same language/script in order to reduce the risk of consumer confusion. For example, the TLDs .EXAMPLE74 and .EXAMPLES may not both be delegated because they are considered confusingly similar. This expands the scope of the String Similarity Review
to encompass singulars/plurals of TLDs on a per-language/script basis.<o:p></o:p></span></p>
<ol style="margin-top:0cm" start="1" type="1">
<ol style="margin-top:0cm" start="2" type="a">
<ol style="margin-top:0cm" start="1" type="i">
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l7 level4 lfo3"><span lang="EN-US">An application for a single/plural variation of an existing TLD or Reserved Name will not be permitted if the intended use of the applied-for string is the single/plural
version of the existing TLD or Reserved Name. For example, if there is an existing TLD .SPRINGS that is used in connection with elastic objects and a new application for .SPRING that is also intended to be used in connection with elastic objects, .SPRING will
not be permitted…<o:p></o:p></span></li></ol>
</ol>
</ol>
</ol>
<p class="MsoListParagraph" style="margin-left:144.0pt"><span lang="EN-US"> <o:p></o:p></span></p>
<ol style="margin-top:0cm" start="1" type="1">
<ol style="margin-top:0cm" start="3" type="a">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l7 level2 lfo3"><u><span lang="EN-US">Path Forward</span></u><span lang="EN-US"><o:p></o:p></span></li></ol>
</ol>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-108.0pt;mso-text-indent-alt:-9.0pt;mso-list:l7 level3 lfo3">
<![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman"">
</span>i.<span style="font:7.0pt "Times New Roman""> </span></span></span><![endif]><span lang="EN-US">First, put aside for the moment the issues expressed by the Board on “content” and assume for now that we can make these recommendations. An e-mail later
will address the content / bylaws issue.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-108.0pt;mso-text-indent-alt:-9.0pt;mso-list:l7 level3 lfo3">
<![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman"">
</span>ii.<span style="font:7.0pt "Times New Roman""> </span></span></span><![endif]><span lang="EN-US">Second, most of the Working Group had little/no issue when the Plural / Singular evaluation was between two brands or a brand and a generic application.<o:p></o:p></span></p>
<ol style="margin-top:0cm" start="1" type="1">
<ol style="margin-top:0cm" start="3" type="a">
<ol style="margin-top:0cm" start="2" type="i">
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l7 level4 lfo3"><span lang="EN-US">Examples: Apple (brand) / apples (generic); Caterpillar (Brand) / caterpillars (generic); Gap (brand) / gaps (generic); Whirlpool (Brand) / whirlpools (generic).
<o:p></o:p></span></li></ol>
</ol>
</ol>
</ol>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-108.0pt;mso-text-indent-alt:-9.0pt;mso-list:l7 level3 lfo3">
<![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman"">
</span>iii.<span style="font:7.0pt "Times New Roman""> </span></span></span><![endif]><span lang="EN-US">Remember also that we have added sections to the Report to now require that applicants describe their proposed use of a TLD in their application and
that the evaluators can ask Clarifying questions if they are unable to ascertain the intended use from the Applicant Responses (IG 24.4). Finally, If both versions (singular/plural) are allowed, then both applicants (in the case where they are both applied
for strings) or the 1 successful applicant (in the case where the application is for a singular/plural of an existing TLD) will have to agree to be bound by its commitment to use the TLD only in the manner in which it proposed in its application.
<o:p></o:p></span></p>
<ol style="margin-top:0cm" start="1" type="1">
<ol style="margin-top:0cm" start="3" type="a">
<ol style="margin-top:0cm" start="3" type="i">
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l7 level4 lfo3"><i><span lang="EN-US">Again, please ignore the potential Bylaws issue FOR NOW</span></i><span lang="EN-US">.
<i>We promise that we will address this later.</i><o:p></o:p></span></li></ol>
</ol>
</ol>
</ol>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-108.0pt;mso-text-indent-alt:-9.0pt;mso-list:l7 level3 lfo3">
<![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman"">
</span>iv.<span style="font:7.0pt "Times New Roman""> </span></span></span><![endif]><u><span lang="EN-US">Here are the options we have</span></u><span lang="EN-US"><o:p></o:p></span></p>
<ol style="margin-top:0cm" start="1" type="1">
<ol style="margin-top:0cm" start="3" type="a">
<ol style="margin-top:0cm" start="4" type="i">
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l7 level4 lfo3"><span lang="EN-US">Leave the language As-Is;<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l7 level4 lfo3"><span lang="EN-US">Ban the co-existence of Singulars and Plurals except for where either one or both of the strings are a Specification 13 (Brand TLD); or<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l7 level4 lfo3"><span lang="EN-US">Ban the co-existence of Singulars and Plurals regardless of intended use completely.<o:p></o:p></span></li></ol>
</ol>
</ol>
</ol>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-108.0pt;mso-text-indent-alt:-9.0pt;mso-list:l7 level3 lfo3">
<![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman"">
</span>v.<span style="font:7.0pt "Times New Roman""> </span></span></span><![endif]><span lang="EN-US">Absent agreement on either 2 or 3, we will stick with the language that we have (Option 1). A lot of work has gone into this already so we need a good
amount of support from within the Working Group to change.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US">Please have your comments (If any) by no later than 23:59:59 UTC on Monday, December 7, 2020.<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span lang="EN-US"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span lang="EN-US">Sincerely,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Jeff & Cheryl<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">SubPro Co-Chairs<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</div>
<hr>
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the
sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that the Com Laude Group does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this
email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company
registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 06181291 and registered office at 28-30
Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176, having its registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA
and Valideus USA, headquartered at 1751 Pinnacle Drive, Suite 600, McLean, VA 22102, USA; Com Laude (Japan) Corporation, a company registered in Japan having its registered office at Suite 319,1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan. For further information
see <a href="https://comlaude.com" target="_blank">www.comlaude.com</a>
</body>
</html>