<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:Aptos;}
@font-face
{font-family:remialcxesans;}
@font-face
{font-family:zone-1;}
@font-face
{font-family:zones-AQ;}
@font-face
{font-family:template-5QSGLunPEem16QANOhMLNA;}
@font-face
{font-family:"Calibri \(Body\)";}
@font-face
{font-family:"Open Sans";}
@font-face
{font-family:Times-Roman;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Times-Italic;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.gmail-double-dentquote, li.gmail-double-dentquote, div.gmail-double-dentquote
{mso-style-name:gmail-double-dentquote;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
p.gmail-double-dentquotechar, li.gmail-double-dentquotechar, div.gmail-double-dentquotechar
{mso-style-name:gmail-double-dentquotechar;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
span.gmailsignatureprefix
{mso-style-name:gmail_signature_prefix;}
span.EmailStyle23
{mso-style-type:personal-compose;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Perhaps also cite ABS Global. ABS Global, Inc. v Cytonome/ST (Fed Cir 2023)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">From page 9 of the attached opinion:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="X-NONE" style="font-size:11.0pt">\u201cuse of \u2018a\u2019 or \u2018an\u2019 before a noun naming an object\u201d requires that the phrase be construed to mean \u201c\u2018one or more\u2019 unless the context sufficiently indicates otherwise.\u201d
<i>Lite-Netics, </i>60 F.4th at 1345; <i>see Salazar, </i>64 F.4th at 1315; <i>Convolve, Inc. v. Compaq Computer Corp.,
</i>812 F.3d 1313, 1321 (Fed. Cir. 2016); <i>Baldwin, </i>512 F.3d at 1342\u201343. The court has called this the \u201cgeneral rule,\u201d adding that an exception \u201conly arises where the language of the claims themselves, the specification, or the prosecution history necessitate
a departure from the rule.\u201d <i>Baldwin, </i>512 F.3d at 1343.</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<div>
<div>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr>
<td style="padding:0in 0in 0in 0in">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr>
<td style="padding:7.5pt 0in 0in 0in">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr>
<td valign="top" style="padding:0in 0in 0in 0in">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td valign="top" style="padding:0in 0in 0in 0in">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr>
<td valign="top" style="padding:0in 0in 0in 0in">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td valign="top" style="padding:7.5pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:"Arial",sans-serif;color:#0F172E">Scott C. Sample</span></b><b><span style="font-family:"Arial",sans-serif;color:#0F172E"><o:p></o:p></span></b></p>
</td>
</tr>
</tbody>
</table>
</td>
<td valign="bottom" style="padding:0in 0in 0in 0in">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td valign="bottom" style="padding:0in 2.25pt 0in 2.25pt">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri \(Body\)";color:gray">|</span><span style="font-size:11.0pt;font-family:"Calibri \(Body\)";color:gray"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
</td>
<td nowrap="" valign="bottom" style="padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri \(Body\)";color:gray">Partner</span><span style="font-size:11.0pt;font-family:"Calibri \(Body\)";color:gray"><o:p></o:p></span></p>
</td>
<td style="padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:1.0pt;font-family:remialcxesans;color:white">\u200b</span><span style="font-size:1.0pt;font-family:template-5QSGLunPEem16QANOhMLNA;color:white">\u200b</span><span style="font-size:1.0pt;font-family:zone-1;color:white">\u200b</span><span style="font-size:1.0pt;font-family:zones-AQ;color:white">\u200b</span><span style="font-size:1.0pt"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<td valign="top" style="padding:0in 0in 0in 0in">
<p class="MsoNormal"><a href="https://www.cm.law/" target="_blank"><span style="font-size:1.0pt;text-decoration:none"><img border="0" width="130" height="50" style="width:1.3541in;height:.5208in" id="Picture_x0020_2096035244" src="cid:image001.png@01DC2ECE.12763670"></span></a><span style="font-size:1.0pt"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<td valign="top" style="padding:0in 0in 0in 0in">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td valign="top" style="padding:.75pt 0in 0in 0in">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td style="padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:1.0pt;color:gray"><img border="0" width="16" height="16" style="width:.1666in;height:.1666in" id="Picture_x0020_2" src="cid:image002.png@01DC2ECE.12763670" alt="Direct:"><o:p></o:p></span></p>
</td>
<td style="padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri \(Body\)";color:gray"> </span><span style="font-size:11.0pt;font-family:"Calibri \(Body\)";color:gray"><a href="tel:469-444-1488" target="_blank"><span style="color:gray;text-decoration:none">469-444-1488</span></a><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td style="padding:0in 0in 0in 0in"></td>
<td style="padding:0in 0in 0in 0in"></td>
</tr>
<tr>
<td style="padding:0in 0in 0in 0in"></td>
<td style="padding:0in 0in 0in 0in"></td>
</tr>
<tr>
<td style="padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:1.0pt;color:gray"><img border="0" width="16" height="16" style="width:.1666in;height:.1666in" id="Picture_x0020_3" src="cid:image003.png@01DC2ECE.12763670" alt="Email:"><o:p></o:p></span></p>
</td>
<td style="padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri \(Body\)";color:gray"> </span><span style="font-size:11.0pt;font-family:"Calibri \(Body\)";color:gray"><a href="mailto:ssample@cm.law" target="_blank"><span style="color:gray;text-decoration:none">ssample@cm.law</span></a><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<td valign="top" style="padding:0in 0in 0in 0in">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td valign="top" style="padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><i><span style="font-size:10.0pt;font-family:"Calibri \(Body\)";color:gray"><a href="https://www.cm.law/cm-law-formerly-culhane-meadows-launches-second-decade-with-fresh-name-and-modern-brand/" target="_blank"><span style="color:#0F172E;text-decoration:none">Please note: Culhane Meadows is now CM Law</span></a><o:p></o:p></span></i></b></p>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<td valign="top" style="padding:0in 0in 0in 0in"></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Patentpractice <patentpractice-bounces@oppedahl-lists.com>
<b>On Behalf Of </b>David Boundy via Patentpractice<br>
<b>Sent:</b> Friday, September 26, 2025 10:04 AM<br>
<b>To:</b> For patent practitioners. This is not for laypersons to seek legal advice. <patentpractice@oppedahl-lists.com><br>
<b>Cc:</b> David Boundy <DavidBoundyEsq@gmail.com><br>
<b>Subject:</b> Re: [Patentpractice] Article ("a" "an" or "the") required before "apparatus" in a claim?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellpadding="0">
<tbody>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<div style="border:solid red 3.0pt;padding:0in 0in 0in 0in">
<p class="MsoNormal" align="center" style="text-align:center;line-height:12.0pt;background:red">
<span style="font-family:"Calibri",sans-serif;color:white">EXTERNAL EMAIL<o:p></o:p></span></p>
</div>
</td>
</tr>
</tbody>
</table>
<div>
<div>
<div>
<p class="MsoNormal">The examiner is wrong. I often use either no article or multiple "a" when i've got a computer network invention, and there are multiple tasks. I do not want my claim to say that all steps must necessarily be performed on one and the same
computer. I use these quotes from the MPEP regularly, and here's form language I use regularly. The question is whether there's some larger stakes to fight for, or whether the best response is to just roll for it. If it's the only amendment you;d make,
then I would resist making the amendment, to make it harder for the next action to be final.<o:p></o:p></p>
</div>
<div>
<p class="gmail-double-dentquote" style="mso-margin-top-alt:12.0pt;margin-right:.5in;margin-bottom:0in;margin-left:.5in;break-after:avoid">
<b><span style="font-size:11.0pt;font-family:"Times New Roman",serif">2173.04 Breadth Is Not Indefiniteness</span></b><span style="font-size:11.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="gmail-double-dentquote" style="mso-margin-top-alt:3.0pt;margin-right:.5in;margin-bottom:0in;margin-left:.5in">
<span style="font-size:11.0pt;font-family:"Times New Roman",serif">Breadth of a claim is not to be equated with indefiniteness.
<i>In re Miller</i>, 441 F.2d 689, 169 USPQ 597 (CCPA 1971). If the scope of the subject matter embraced by the claims is clear, and if applicants have not otherwise indicated that they intend the invention to be of a scope different from that defined in the
claims, then the claims comply with 35 U.S.C. § 112, second paragraph.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="gmail-double-dentquotechar" style="mso-margin-top-alt:12.0pt;margin-right:.5in;margin-bottom:0in;margin-left:.5in;break-after:avoid">
<b><span style="font-size:11.0pt;font-family:"Times New Roman",serif">2173.02 Clarity and Precision</span></b><span style="font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="gmail-double-dentquotechar" style="mso-margin-top-alt:3.0pt;margin-right:.5in;margin-bottom:3.0pt;margin-left:.5in">
<span style="font-size:11.0pt;font-family:"Times New Roman",serif">The examiner\u2019s focus during examination of claims for compliance with the requirement for definiteness of 35 U.S.C. 112, second paragraph, is whether the claim meets the threshold requirements
of clarity and precision, not whether more suitable language or modes of expression are available. \u2026 he or she should allow claims which define the patentable subject matter with a
<u>reasonable</u> degree of particularity and distinctness. <b>Some latitude in the manner of expression and the aptness of terms should be permitted even though the claim language is not as precise as the examiner might desire. Examiners \u2026 should not reject
claims or insist on their own preferences</b> if other modes of expression selected by applicants satisfy the statutory requirement.</span><span style="font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="line-height:22.0pt"><span style="font-family:"Times New Roman",serif"> In a case where pedantic conformance to \u201cantecedent basis\u201d was the only reason to question definiteness, the Federal Circuit squarely rejected \u201cantecedent
basis\u201d as a controlling principle. The Federal Circuit made clear that indefiniteness turns on consideration of surrounding claim language, the specification, and the knowledge of those in the art, to identify substantive indefiniteness, not rules of form:<o:p></o:p></span></p>
<p class="gmail-double-dentquote" style="mso-margin-top-alt:12.0pt;margin-right:.5in;margin-bottom:3.0pt;margin-left:.5in">
<span style="font-size:11.0pt;font-family:"Times New Roman",serif">When the meaning of the claim would reasonably be understood by persons of ordinary skill when read in light of the specification, the claim is not subject to invalidity upon departure from
the protocol of "antecedent basis." <i>Energizer Holdings, Inc. v Int\u2019l Trade Comm\u2019n</i>, 435 F.3d 1366, 1370, 77 USPQ2d 1625, 1628 (Fed. Cir. 2006).<o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:22.0pt"><span style="font-family:"Times New Roman",serif"> The MPEP teaches the same. MPEP § 2173.05, by its terms, applies only to statutory indefiniteness, but gives valuable advice here. MPEP § 2173.05(e)
instructs that mere lack of antecedent basis \u201cdoes not always render a claim indefinite.\u201d Rather, an Action
<b><i>must in addition</i></b> show \u201cit would be unclear as to what element the limitation was making reference.\u201d The examples given in MPEP § 2173.05(e) all require that there be two of something, and that the claim language be ambiguous as to which of the
two is being referred to, or some similar <i>ambiguity</i>. No such showing exists in the Action. MPEP § 2173.05(e) cautions that no rejection should be raised when \u201cthe scope of a claim would be reasonably ascertainable by those skilled in the art.\u201d
</span><span style="font-family:"Times-Roman",serif">MPEP § 2173.02(II) cautions that \u201cExaminers should note that Office policy is not to employ
</span><i><span style="font-family:"Times-Italic",serif">per se </span></i><span style="font-family:"Times-Roman",serif">rules to make technical rejections.\u201d <i>See also </i></span><span style="font-family:"Times New Roman",serif">
<i>Evolusion Concepts, Inc. v. HOC Events, Inc.</i>, 22 F.4th 1361 (Fed. Cir. 2022) (departure from strict "antecedent basis" is not indefinite).<o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:22.0pt"><span style="font-family:"Times New Roman",serif"> The Action makes no showing that the scope of any of the objected-to claims is anything other than \u201creasonably ascertainable.\u201d Without that explanation,
it\u2019s impossible to know whether there\u2019s a real problem, let alone what the appropriate cure would be.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Fri, Sep 26, 2025 at 10:38<span style="font-family:"Arial",sans-serif">\u202f</span>AM George Jakobsche via Patentpractice <<a href="mailto:patentpractice@oppedahl-lists.com">patentpractice@oppedahl-lists.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif">An examiner objected to a claim like the following (emphasis added):</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif">A doohickie comprising:
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif"> <u>XYZ apparatus</u> that defines a volume and comprises:
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif"> a port in fluid communication with the volume;
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif"> ... ; and</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif"> a ABC disposed directly below the XYZ apparatus ...</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif">The examiner asserts \u201cXYZ apparatus\u201d requires a leading indefinite article, i.e., \u201ca\u201d. This seems like a relatively minor point, but
it seems to me that \u201capparatus\u201d here refers collectively to its components (as recited after its \u201ccomprising\u201d). If so, \u201capparatus\u201d is
<i>uncountable</i> and, therefore, does not take an indefinite article before it, as discussed
<a href="https://www.butte.edu/departments/cas/tipsheets/grammar/articles.html" target="_blank">
here</a> and <a href="https://usingaborrowedlanguage.wordpress.com/2014/02/11/apparatus/" target="_blank">
here</a>. </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif">Are there any grammarians on this list who can opine on necessity of an indefinite article before \u201capparatus\u201d in the subject claim?</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif">Situations like this make me wish I still had access to my nineth grade English teacher (Mrs. Pollard), who I sorely underappreciated
at the time. </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif">Best regards,</span><o:p></o:p></p>
<div style="border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in;border-color:currentcolor currentcolor windowtext">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif">George</span><o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif">George Jakobsche Patent Counsel PLLC</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif">39 Old Farm Road, Concord, MA 01742-5234</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri",sans-serif"><a href="mailto:George@JakobscheLaw.com" target="_blank"><span style="color:#0563C1">George@JakobscheLaw.com</span></a> | +1-978-245-8100</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">This e-mail is from George Jakobsche Patent Counsel PLLC, a law firm, and it may contain confidential or privileged
information. If you are not the intended recipient, do not read, copy, or distribute this message or any attachment(s). Instead, please notify the sender and delete the message and the attachment(s). Thank you.</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">-- <br>
Patentpractice mailing list<br>
<a href="mailto:Patentpractice@oppedahl-lists.com" target="_blank">Patentpractice@oppedahl-lists.com</a><br>
<a href="http://oppedahl-lists.com/mailman/listinfo/patentpractice_oppedahl-lists.com" target="_blank">http://oppedahl-lists.com/mailman/listinfo/patentpractice_oppedahl-lists.com</a><o:p></o:p></p>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<span class="gmailsignatureprefix">-- </span><o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:7.5pt;margin-left:0in">
<span style="font-size:9.0pt;font-family:"Open Sans",sans-serif;color:#667FA0"><a href="https://www.iam-media.com/strategy300/individuals/david-boundy" target="_blank"><span style="color:#667FA0;text-decoration:none"><img border="0" width="73" height="92" style="width:.7604in;height:.9583in" id="_x0000_i1025" src="https://ci3.googleusercontent.com/mail-sig/AIorK4wRMgBgcdZCqTw68Gg6ihENvW6_y8dGBqYvnJwiaIyu6LO5a7IJ-cljKsueIE5uxXbT6s9MN5hE2lGU"></span><span style="color:#667FA0;text-decoration:none">
<br>
</span></a><o:p></o:p></span></p>
<p style="margin:0in;text-align:start"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#606E9A">David Boundy </span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#7C869A">| Partner <span style="background:white">| </span>Potomac Law
Group, PLLC</span><span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:#323130"><o:p></o:p></span></p>
<p style="margin:0in;text-align:start"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#7C869A">P.O. Box 590638, Newton, MA 02459</span><span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:#323130"><o:p></o:p></span></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif;color:#7C869A">Tel (646) 472-9737 </span><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif;color:gray">|</span><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif;color:#7C869A"> Fax:
(202) 318-7707</span><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif;color:#7C869A"><o:p></o:p></span></p>
<p style="margin:0in"><u><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#0C64C0"><a href="mailto:dboundy@potomaclaw.com" target="_blank" title="mailto:dboundy@potomaclaw.com"><span style="color:#FE46A5">dboundy@potomaclaw.com</span></a></span></u><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#0C64C0"> </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#7C869A">| <u><a href="http://www.potomaclaw.com/" target="_blank" title="http://www.potomaclaw.com/"><span style="color:#0C64C0">www.potomaclaw.com</span></a></u></span><span style="font-size:10.0pt;font-family:"Helvetica",sans-serif;color:#7C869A"><o:p></o:p></span></p>
<p style="margin:0in"><span style="font-size:10.0pt"><a href="http://ssrn.com/author=2936470" target="_blank">Articles at http://ssrn.com/author=2936470</a><a href="https://www.keynect.us/requestCardAccess/USA500DBOUN?" target="_blank"><span style="color:windowtext"><br>
</span></a><o:p></o:p></span></p>
<p style="margin:0in"><span style="font-size:10.0pt"><a href="https://www.keynect.us/requestCardAccess/USA500DBOUN?" target="_blank"><span style="color:windowtext">Click here to add me to your contacts.</span></a><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>