<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>What she said.</p>
<div class="moz-cite-prefix">On 3/17/2024 9:56 AM, Pamela Chestek
via E-trademarks wrote:<br>
</div>
<blockquote type="cite"
cite="mid:b12f1686-eed4-47e3-b3bf-c26ac93c89bd@chesteklegal.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
For one thing, it means that whenever you do a search you have to
make a decision about whether to use the Advanced syntax or the
regex syntax. And it appears there are situations where you <i>must</i>
use one or the other, such as my t-shirt example, which means you
have to be highly skilled with both. Case in point - use of
capitals:<br>
<br>
Id Query ResultCount<br>
1 GS2:DVD 98307<br>
2 GS2:/DVD/ 0<br>
3 GS2:/dvd/ 98307<br>
<br>
If you don't remember that the search string in regex must be
lowercase, and enter the term as it actually appears in the ID,
you may have just screwed the pooch. It's just an invitation to
disaster because unless you are a master of both you won't realize
that your query was malformed.<br>
<br>
I also mentioned that I haven't found a way to do a proximity
search in regex. But you can only do pattern matching in regex.
So to pattern match on a two-word unitary phrase, I guess you have
to include two different searches, e.g., <i>CM:("tick tock") AND
CM:(/ti[ckqx]/) AND CM:(/to[ckqx]/)</i> to find the homonyms for
"tick tock"?<br>
<br>
There are so many examples of unreliable queries - forgetting a
colon after the field tag, or failing to use all caps for
connectors, also give you some results and you may not realize
they are unreliable. I have submitted a request that a malformed
query be flagged. It might not be possible with the t-shirt
example, but it should be possible to at least identify
syntactical errors.<br>
<br>
Pam<br>
<br>
<div class="moz-signature">Pamela S. Chestek<br>
Chestek Legal<br>
300 Fayetteville Street<br>
Unit 2492<br>
Raleigh, NC 27602<br>
+1 919-800-8033<br>
<a class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:pamela@chesteklegal.com" moz-do-not-send="true">pamela@chesteklegal.com</a><br>
<a class="moz-txt-link-abbreviated"
href="http://www.chesteklegal.com" moz-do-not-send="true">www.chesteklegal.com</a><br>
<br>
</div>
<div class="moz-cite-prefix">On 3/16/2024 11:44 AM, Sam Castree
via E-trademarks wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAKU8sWZsi8AHDRn0BsWJkgGMzcHrtzTye_8Q_a9cPeBOKcbEQg@mail.gmail.com">
<meta http-equiv="content-type"
content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_default"
style="font-family:times new roman,serif"><span
style="font-size:16px">Just curious, but is there a reason
why that particular search would need to use regex at
all? Maybe I'm way off (I definitely don't claim to have
mastered this system yet), but it seems like a..."normal"
expert search would work just fine. GS:"baby bonnet" or
whatever.</span></div>
<div class="gmail_default"
style="font-family:times new roman,serif"><span
style="font-size:16px"><br clear="all">
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div
style="color:rgb(34,34,34);font-family:tahoma;font-size:medium"><span
style="font-family:"times new roman",serif"><span
style="font-size:16px">Cheers,</span></span></div>
<div
style="color:rgb(34,34,34);font-family:tahoma;font-size:medium"><span
style="font-family:"times new roman",serif"><span
style="font-size:16px"> </span></span></div>
<div
style="color:rgb(34,34,34);font-family:tahoma;font-size:medium"><span
style="font-family:"times new roman",serif"><span
style="color:rgb(255,102,0);font-size:12pt">Sam<span> Castree,
III</span></span></span></div>
<div
style="color:rgb(34,34,34);font-family:tahoma;font-size:medium"><span
style="font-family:"times new roman",serif"><span
style="color:rgb(255,102,0);font-size:12pt"><br>
</span></span></div>
<div style="color:rgb(34,34,34);font-size:medium"><font
face="times new roman, serif"><span
style="color:rgb(255,102,0);font-size:12pt"><span><i>Sam
Castree Law, LLC</i></span></span></font></div>
<div style="color:rgb(34,34,34)"><font
face="times new roman, serif"><span
style="color:rgb(255,102,0)"><span><span
style="font-size:12pt"><i>3421 W. Elm St.</i></span></span></span></font></div>
<div style="color:rgb(34,34,34)"><font
face="times new roman, serif"><span
style="color:rgb(255,102,0)"><span><span
style="font-size:12pt"><i>McHenry, IL
60050</i></span></span></span></font></div>
<div style="color:rgb(34,34,34)"><font
face="times new roman, serif"><span
style="color:rgb(255,102,0)"><span><span
style="font-size:12pt"><i>(815) 344-6300</i></span></span></span></font></div>
</div>
</div>
</div>
</span><br>
</div>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Mar 15, 2024 at
7:56 PM Pamela Chestek via E-trademarks <<a
href="mailto:e-trademarks@oppedahl-lists.com"
moz-do-not-send="true" class="moz-txt-link-freetext">e-trademarks@oppedahl-lists.com</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">Indeed,
and the help materials couldn't be more terse and the <br>
information more difficult to find, other than not to exist
at all. I <br>
have yet to figure out how (if possible) to search for a
two-word <br>
expression, like "baby bonnet," using regex.<br>
<br>
Id Query ResultCount<br>
3 GS2:(/baby/ AND /bonnet/) 2484<br>
2 GS2:/baby bonnet/ 0<br>
1 GS2:"baby bonnet" 43<br>
<br>
So you're left with trying to remember two similar, but not
identical, <br>
search systems, including how they treat quotation marks,
reserved <br>
characters, capitalization, etc.<br>
<br>
Pam<br>
<br>
Pamela S. Chestek<br>
Chestek Legal<br>
300 Fayetteville Street<br>
Unit 2492<br>
Raleigh, NC 27602<br>
+1 919-800-8033<br>
<a href="mailto:pamela@chesteklegal.com" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">pamela@chesteklegal.com</a><br>
<a href="http://www.chesteklegal.com" rel="noreferrer"
target="_blank" moz-do-not-send="true">www.chesteklegal.com</a><br>
<br>
On 3/15/2024 8:40 PM, Richard Schafer via E-trademarks
wrote:<br>
> The fact that we have to make guesses about how the
indexes work shows how poorly the PTO has implemented and
documented this system. I wonder if examining attorneys have
the same poor explanation about how the indexes work. If
they do, that's really bad. If they have a fuller
explanation, what possible reason would the PTO have for not
making that explanation public?<br>
><br>
> Best regards,<br>
> Richard A. Schafer | Schafer IP Law<br>
> P.O. Box 230081 | Houston, TX 77223<br>
> M: 832.283.6564 | <a
href="mailto:richard@schafer-ip.com" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">richard@schafer-ip.com</a><br>
><br>
> -----Original Message-----<br>
> From: E-trademarks <<a
href="mailto:e-trademarks-bounces@oppedahl-lists.com"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">e-trademarks-bounces@oppedahl-lists.com</a>>
On Behalf Of Neil R. Ormos via E-trademarks<br>
> Sent: Friday, March 15, 2024 6:19 PM<br>
> To: E-trademarks Mailing List <<a
href="mailto:e-trademarks@oppedahl-lists.com"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">e-trademarks@oppedahl-lists.com</a>><br>
> Cc: Neil R. Ormos <<a
href="mailto:ormos-lists@ormos.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">ormos-lists@ormos.org</a>><br>
> Subject: Re: [E-trademarks] Regex search<br>
><br>
> Pamela Chestek via E-trademarks wrote:<br>
><br>
>> Can anyone explain to me why the first two search
queries didn't give<br>
>> me the same results as the third query? I was in
expert mode.<br>
> <br>
>> GS:/t\-shirt/ 0<br>
>> GS:/t[-]shirt/ 0<br>
>> GS:t-shirt 511200<br>
> When the GS index is used with a regular expression
search, the index appears to contain each of the words of
the goods and services field in isolation. Spaces and
hyphens separate words, but some other punctuation does
not. Your regexps do not match because t-shirt does not
appear as a single word in the index.<br>
><br>
> The GS index behaves differently when used with other
types of search.<br>
><br>
> <<a
href="https://oppedahl-lists.com/pipermail/e-trademarks_oppedahl-lists.com/2024-January/000554.html"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://oppedahl-lists.com/pipermail/e-trademarks_oppedahl-lists.com/2024-January/000554.html</a>><br>
><br>
> And the GS2 index also behaves differently.<br>
><br>
> GS2:/t[-]shirt/<br>
><br>
> returns 61,341 records.<br>
><br>
> I know GS2 does some sort of stemming, but I haven't
been able to synthesize a complete explanation. If someone
has GS2 figured it out, or knows of a document that
describes its behavior, I hope they will explain.<br>
><br>
><br>
> --<br>
> E-trademarks mailing list<br>
> <a href="mailto:E-trademarks@oppedahl-lists.com"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">E-trademarks@oppedahl-lists.com</a><br>
> <a
href="http://oppedahl-lists.com/mailman/listinfo/e-trademarks_oppedahl-lists.com"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">http://oppedahl-lists.com/mailman/listinfo/e-trademarks_oppedahl-lists.com</a><br>
><br>
<br>
<br>
-- <br>
E-trademarks mailing list<br>
<a href="mailto:E-trademarks@oppedahl-lists.com"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">E-trademarks@oppedahl-lists.com</a><br>
<a
href="http://oppedahl-lists.com/mailman/listinfo/e-trademarks_oppedahl-lists.com"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">http://oppedahl-lists.com/mailman/listinfo/e-trademarks_oppedahl-lists.com</a><br>
</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
<br>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
</body>
</html>