<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px; ">
<div>
<div>Just a note to let you know that we filed BC comments on the matching rules for TM Clearinghouse. (see below and
<a href="http://forum.icann.org/lists/tmch-docs-sep12/msg00013.html">here</a>)</div>
</div>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px; ">
<br>
</div>
<div><font class="Apple-style-span" face="Calibri,sans-serif">The draft comment was circulated to BC membership on 17-Oct and no edits or objections were recorded in the 14-day review period. </font></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px; ">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px; ">
<div>Steve DelBianco</div>
<div>Vice chair for policy coordination</div>
<div>Business Constituency</div>
</div>
<span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px; ">
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-family: Calibri, sans-serif; ">
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Optima; font-size:10pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<b><br>
</b></div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-family: Calibri, sans-serif; ">
<div>The Business Constituency offers this suggestion on ICANN's proposed matching rules for names entered in the Trademark Clearinghouse.</div>
<div><br>
</div>
<div>Upon review of the possible methods for translating “@” and “&” as described in the “Explanatory Memorandum: Implementing the Matching Rules”, the Business Constituency requests that the languages for translations of “@” and “&” be chosen on a per-record basis
by the trademark owner.</div>
<div><br>
</div>
<div>The memorandum suggests that the language of translations should be based upon the official language(s) of the trademark registry.</div>
<div><br>
</div>
<div>Restricting translations to the official language of the trademark registry is problematic, particularly for global brands or for trademarks registered in countries where there is no official language.</div>
<div><br>
</div>
<div>Furthermore, requiring that translations of “@” and “&” match the official language of the trademark registry would likely result in additional costs to brand owners for additional submissions of the same mark to the Trademark Clearinghouse.</div>
<div><br>
</div>
<div>Elisa Cooper served as Rapportuer for these comments, which were approved in accordance with the BC Charter. </div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</span></div>
</div>
</span>
</body>
</html>