<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments for Patently-O	</title>
	<atom:link href="https://patentlyo.com/comments/feed" rel="self" type="application/rss+xml" />
	<link>https://patentlyo.com</link>
	<description>America&#039;s leading patent law blog</description>
	<lastBuildDate>Tue, 16 Jun 2026 21:43:34 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		Comment on It&#8217;s Not You, It&#8217;s Your Claims: Disclosed but Unclaimed Embodiments at the Federal Circuit by davidlewisnmn		</title>
		<link>https://patentlyo.com/patent/2026/06/its-not-you-its-your-claims-disclosed-but-unclaimed-embodiments-at-the-federal-circuit.html#comment-990179</link>

		<dc:creator><![CDATA[davidlewisnmn]]></dc:creator>
		<pubDate>Tue, 16 Jun 2026 21:43:34 +0000</pubDate>
		<guid isPermaLink="false">https://patentlyo.com/?p=48886#comment-990179</guid>

					<description><![CDATA[Note that although the claim recites &quot;receiving the password from the user via the first secure computer network,&quot; it never expressly recites that the user sent the password. 

Thus, even if sending a password in pieces is not sending a password (which is not entirely clear), one can infer that the drafter intended the claim to cover a situation in which the password is received even though it was somehow not sent as a password. 

In the password encryption art, that can be precisely the point - to send the password in pieces or to send something from which the password is constructed (or encrypting and sending the password in some other instead of sending the password itself), so that a usable unecrypted form of the password, as such, is never &quot;sent by the user,&quot; but is nonetheless is &quot;received from the user&quot; (as a result of being assembled from the messages sent by the user).  See https://en.wikipedia.org/wiki/Diffie-Hellman_key_exchange, as an example of such a method of exchanging keys without actually sending the keys (the same can be done for passwords).

Consequently, perhaps it is a bit of a stretch to say,

“I wouldn’t put it so much as excluding. I think the claim language simply doesn’t cover it on its face.” 

Note that following this logic (depending on specification, wording of the claims, and prosecution history), if Bob sends an encrypted password to Alice, and then Alice simply decrypts the encrypted password to arrive at a usable version of the password, Bob did not &quot;send the password to Alice&quot; and Alice did not &quot;receive the password from Bob&quot; (no matter how simple or complex the encryption is) - that embodiment is dedicated to the public (if disclosed in the specification but not expressly allowed for in the claim).

In the context of the password encryption art, that would seem a bit strange, because often those working in the password encryption art say sending the password but actually mean sending the encrypted password - but, yet, that would seem to be precisely what this case was about. 

Oh well... I guess we are stuck with this decision for now.]]></description>
			<content:encoded><![CDATA[ <p>Note that although the claim recites &#8220;receiving the password from the user via the first secure computer network,&#8221; it never expressly recites that the user sent the password. </p>
<p>Thus, even if sending a password in pieces is not sending a password (which is not entirely clear), one can infer that the drafter intended the claim to cover a situation in which the password is received even though it was somehow not sent as a password. </p>
<p>In the password encryption art, that can be precisely the point &#8211; to send the password in pieces or to send something from which the password is constructed (or encrypting and sending the password in some other instead of sending the password itself), so that a usable unecrypted form of the password, as such, is never &#8220;sent by the user,&#8221; but is nonetheless is &#8220;received from the user&#8221; (as a result of being assembled from the messages sent by the user).  See <a href="https://en.wikipedia.org/wiki/Diffie-Hellman_key_exchange" rel="nofollow ugc">link to en.wikipedia.org</a>, as an example of such a method of exchanging keys without actually sending the keys (the same can be done for passwords).</p>
<p>Consequently, perhaps it is a bit of a stretch to say,</p>
<p>“I wouldn’t put it so much as excluding. I think the claim language simply doesn’t cover it on its face.” </p>
<p>Note that following this logic (depending on specification, wording of the claims, and prosecution history), if Bob sends an encrypted password to Alice, and then Alice simply decrypts the encrypted password to arrive at a usable version of the password, Bob did not &#8220;send the password to Alice&#8221; and Alice did not &#8220;receive the password from Bob&#8221; (no matter how simple or complex the encryption is) &#8211; that embodiment is dedicated to the public (if disclosed in the specification but not expressly allowed for in the claim).</p>
<p>In the context of the password encryption art, that would seem a bit strange, because often those working in the password encryption art say sending the password but actually mean sending the encrypted password &#8211; but, yet, that would seem to be precisely what this case was about. </p>
<p>Oh well&#8230; I guess we are stuck with this decision for now.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Has the Late-Continuation Surcharge Shifted Filing? by paulf		</title>
		<link>https://patentlyo.com/patent/2026/06/has-the-late-continuation-surcharge-shifted-filing.html#comment-990178</link>

		<dc:creator><![CDATA[paulf]]></dc:creator>
		<pubDate>Tue, 16 Jun 2026 19:55:16 +0000</pubDate>
		<guid isPermaLink="false">https://patentlyo.com/?p=48706#comment-990178</guid>

					<description><![CDATA[The USPTO Rule for late-filed-continuations fee surcharges effective January 19, 2025 is to me one of the few business-positive real innovations of the current management.  Dennis deserves credit for showing in this blog how effective it has been in reducing the business-uncertainty of &quot;submarine&quot; (late-changing-claims) continuations many years after their parental application specification publications.  
  [Now if only the PTO would finally properly docket and process applications in their actual filing date order instead of fictionally treating continuations as “new” applications in several respects.]]]></description>
			<content:encoded><![CDATA[ <p>The USPTO Rule for late-filed-continuations fee surcharges effective January 19, 2025 is to me one of the few business-positive real innovations of the current management.  Dennis deserves credit for showing in this blog how effective it has been in reducing the business-uncertainty of &#8220;submarine&#8221; (late-changing-claims) continuations many years after their parental application specification publications.<br />
  [Now if only the PTO would finally properly docket and process applications in their actual filing date order instead of fictionally treating continuations as “new” applications in several respects.]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Hooked on Differences: Design Patent Doctrine and Schedule A Litigation at the Federal Circuit by Perry Saidman		</title>
		<link>https://patentlyo.com/patent/2026/06/hooked-on-differences-design-patent-doctrine-and-schedule-a-litigation-at-the-federal-circuit.html#comment-990177</link>

		<dc:creator><![CDATA[Perry Saidman]]></dc:creator>
		<pubDate>Tue, 16 Jun 2026 10:54:46 +0000</pubDate>
		<guid isPermaLink="false">https://patentlyo.com/?p=48831#comment-990177</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://patentlyo.com/patent/2026/06/hooked-on-differences-design-patent-doctrine-and-schedule-a-litigation-at-the-federal-circuit.html#comment-990175&quot;&gt;paulf&lt;/a&gt;.

&quot;colorable imitation&quot; has rarely been cited  by the CAFC, and when it was, no standards were set forth for determining it. And there&#039;s no ordinary observer there, so who makes the determination?  Is is the same, different, broader, narrower than &quot;substantially the same&quot;?]]></description>
			<content:encoded><![CDATA[ <p>In reply to <a href="https://patentlyo.com/patent/2026/06/hooked-on-differences-design-patent-doctrine-and-schedule-a-litigation-at-the-federal-circuit.html#comment-990175">paulf</a>.</p>
<p>&#8220;colorable imitation&#8221; has rarely been cited  by the CAFC, and when it was, no standards were set forth for determining it. And there&#8217;s no ordinary observer there, so who makes the determination?  Is is the same, different, broader, narrower than &#8220;substantially the same&#8221;?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Hooked on Differences: Design Patent Doctrine and Schedule A Litigation at the Federal Circuit by Perry Saidman		</title>
		<link>https://patentlyo.com/patent/2026/06/hooked-on-differences-design-patent-doctrine-and-schedule-a-litigation-at-the-federal-circuit.html#comment-990176</link>

		<dc:creator><![CDATA[Perry Saidman]]></dc:creator>
		<pubDate>Tue, 16 Jun 2026 10:51:10 +0000</pubDate>
		<guid isPermaLink="false">https://patentlyo.com/?p=48831#comment-990176</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://patentlyo.com/patent/2026/06/hooked-on-differences-design-patent-doctrine-and-schedule-a-litigation-at-the-federal-circuit.html#comment-990174&quot;&gt;BillAtkins&lt;/a&gt;.

The tell that the Gorham test is creeping towards  the trademark infringement test is  this sentence:  &quot;The opinion added that “one could mix samples of the two products randomly and have no trouble attributing them to the correct source.”  Design patent infringement has nothing to do with source, it focusses on comparing the two designs.  Also see the Berry Sterling case which, at the end, in dicta, the court listed functionality factors lifted almost entirely from the functionality test for trademarks.]]></description>
			<content:encoded><![CDATA[ <p>In reply to <a href="https://patentlyo.com/patent/2026/06/hooked-on-differences-design-patent-doctrine-and-schedule-a-litigation-at-the-federal-circuit.html#comment-990174">BillAtkins</a>.</p>
<p>The tell that the Gorham test is creeping towards  the trademark infringement test is  this sentence:  &#8220;The opinion added that “one could mix samples of the two products randomly and have no trouble attributing them to the correct source.”  Design patent infringement has nothing to do with source, it focusses on comparing the two designs.  Also see the Berry Sterling case which, at the end, in dicta, the court listed functionality factors lifted almost entirely from the functionality test for trademarks.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Hooked on Differences: Design Patent Doctrine and Schedule A Litigation at the Federal Circuit by paulf		</title>
		<link>https://patentlyo.com/patent/2026/06/hooked-on-differences-design-patent-doctrine-and-schedule-a-litigation-at-the-federal-circuit.html#comment-990175</link>

		<dc:creator><![CDATA[paulf]]></dc:creator>
		<pubDate>Mon, 15 Jun 2026 13:07:01 +0000</pubDate>
		<guid isPermaLink="false">https://patentlyo.com/?p=48831#comment-990175</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://patentlyo.com/patent/2026/06/hooked-on-differences-design-patent-doctrine-and-schedule-a-litigation-at-the-federal-circuit.html#comment-990172&quot;&gt;paulf&lt;/a&gt;.

Re design patent claims, did 35 U.S.C. § 289 or any equivalent statute contain the same apparent design patent infringement-broadening language of &quot;or any colorable imitation thereof&quot; at the time of Gorham v. White? Do controlling CAFC design patent cases define or rely on Not finding &quot;any colorable imitation&quot; in decisions finding a “plainly dissimilar” test from Egyptian Goddess?]]></description>
			<content:encoded><![CDATA[ <p>In reply to <a href="https://patentlyo.com/patent/2026/06/hooked-on-differences-design-patent-doctrine-and-schedule-a-litigation-at-the-federal-circuit.html#comment-990172">paulf</a>.</p>
<p>Re design patent claims, did 35 U.S.C. § 289 or any equivalent statute contain the same apparent design patent infringement-broadening language of &#8220;or any colorable imitation thereof&#8221; at the time of Gorham v. White? Do controlling CAFC design patent cases define or rely on Not finding &#8220;any colorable imitation&#8221; in decisions finding a “plainly dissimilar” test from Egyptian Goddess?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Hooked on Differences: Design Patent Doctrine and Schedule A Litigation at the Federal Circuit by BillAtkins		</title>
		<link>https://patentlyo.com/patent/2026/06/hooked-on-differences-design-patent-doctrine-and-schedule-a-litigation-at-the-federal-circuit.html#comment-990174</link>

		<dc:creator><![CDATA[BillAtkins]]></dc:creator>
		<pubDate>Mon, 15 Jun 2026 11:39:22 +0000</pubDate>
		<guid isPermaLink="false">https://patentlyo.com/?p=48831#comment-990174</guid>

					<description><![CDATA[This petition may have legs. It reminds me of the trademark realm’s ordinary purchaser with imperfect recollection, as that is more similar to the Gorham test. Highway signs in the 9th Circuit. Car sales (?) or similar driving down a road in the 7th. Let’s hope the Federal Circuit takes and corrects this.]]></description>
			<content:encoded><![CDATA[ <p>This petition may have legs. It reminds me of the trademark realm’s ordinary purchaser with imperfect recollection, as that is more similar to the Gorham test. Highway signs in the 9th Circuit. Car sales (?) or similar driving down a road in the 7th. Let’s hope the Federal Circuit takes and corrects this.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Hooked on Differences: Design Patent Doctrine and Schedule A Litigation at the Federal Circuit by paulf		</title>
		<link>https://patentlyo.com/patent/2026/06/hooked-on-differences-design-patent-doctrine-and-schedule-a-litigation-at-the-federal-circuit.html#comment-990172</link>

		<dc:creator><![CDATA[paulf]]></dc:creator>
		<pubDate>Sun, 14 Jun 2026 22:32:01 +0000</pubDate>
		<guid isPermaLink="false">https://patentlyo.com/?p=48831#comment-990172</guid>

					<description><![CDATA[It has been noted that the 1871 Gorham v. White Supreme Court decision did not just give a test for design patent infringement of only &quot;if, in the eye of an ordinary observer, giving such attention as a purchaser usually gives, two designs are substantially the same, if the resemblance is such as to deceive such an observer, inducing him to purchase one supposing it to be the other, the first one patented is infringed by the other.&quot;[32].  It additionally required that &quot;the accused device must appropriate the novelty in the patented device which distinguishes it from the prior art.&quot;[33].  
   Also, did Gorham v. White really reject any judicial consideration of the scope of the claim of a design patent for infringement [unlike normal patents] to use a test seeming more appropriate for trademark infringement? And, if so, would the present Supreme Court? 
  Also, re district court “Schedule A” suits granting injunctions against defendants uninformed and unrepresented, was there not a recent 7th Cir. decision on that?]]></description>
			<content:encoded><![CDATA[ <p>It has been noted that the 1871 Gorham v. White Supreme Court decision did not just give a test for design patent infringement of only &#8220;if, in the eye of an ordinary observer, giving such attention as a purchaser usually gives, two designs are substantially the same, if the resemblance is such as to deceive such an observer, inducing him to purchase one supposing it to be the other, the first one patented is infringed by the other.&#8221;[32].  It additionally required that &#8220;the accused device must appropriate the novelty in the patented device which distinguishes it from the prior art.&#8221;[33].<br />
   Also, did Gorham v. White really reject any judicial consideration of the scope of the claim of a design patent for infringement [unlike normal patents] to use a test seeming more appropriate for trademark infringement? And, if so, would the present Supreme Court?<br />
  Also, re district court “Schedule A” suits granting injunctions against defendants uninformed and unrepresented, was there not a recent 7th Cir. decision on that?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on It&#8217;s Not You, It&#8217;s Your Claims: Disclosed but Unclaimed Embodiments at the Federal Circuit by Elizabeth Nugent		</title>
		<link>https://patentlyo.com/patent/2026/06/its-not-you-its-your-claims-disclosed-but-unclaimed-embodiments-at-the-federal-circuit.html#comment-990171</link>

		<dc:creator><![CDATA[Elizabeth Nugent]]></dc:creator>
		<pubDate>Fri, 12 Jun 2026 17:26:33 +0000</pubDate>
		<guid isPermaLink="false">https://patentlyo.com/?p=48886#comment-990171</guid>

					<description><![CDATA[Could this patent have been saved in the drafting phase by including a dependent claim specifying that the receiving step included receiving the password in two separate parts?]]></description>
			<content:encoded><![CDATA[ <p>Could this patent have been saved in the drafting phase by including a dependent claim specifying that the receiving step included receiving the password in two separate parts?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Enforceable, but Not Reviewable: A Breached Sotera Stipulation and § 314(d) by WTF		</title>
		<link>https://patentlyo.com/patent/2026/06/the-sotera-trap-section-314d-and-the-stipulation-that-binds-only-one-side.html#comment-990170</link>

		<dc:creator><![CDATA[WTF]]></dc:creator>
		<pubDate>Thu, 11 Jun 2026 15:39:47 +0000</pubDate>
		<guid isPermaLink="false">https://patentlyo.com/?p=48811#comment-990170</guid>

					<description><![CDATA[Isn&#039;t this the right result all around?  The Sotera stipulation has the effect of moving 315(e) estoppel forward and, here, the Court enforced the stipulation in the same way it would likely have enforced estoppel under 315(e)(2) had the summary judgment argument already been addressed in a final written decision.  The stipulation never contemplated the sanction that a later-violation would cause the institution decisions to be unwound.]]></description>
			<content:encoded><![CDATA[ <p>Isn&#8217;t this the right result all around?  The Sotera stipulation has the effect of moving 315(e) estoppel forward and, here, the Court enforced the stipulation in the same way it would likely have enforced estoppel under 315(e)(2) had the summary judgment argument already been addressed in a final written decision.  The stipulation never contemplated the sanction that a later-violation would cause the institution decisions to be unwound.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Trading Claims for Speed: USPTO Sweetens the Streamlined Claim Set Pilot by Thomas Dickey		</title>
		<link>https://patentlyo.com/patent/2026/06/trading-claims-for-speed-uspto-sweetens-the-streamlined-claim-set-pilot.html#comment-990169</link>

		<dc:creator><![CDATA[Thomas Dickey]]></dc:creator>
		<pubDate>Thu, 11 Jun 2026 11:56:28 +0000</pubDate>
		<guid isPermaLink="false">https://patentlyo.com/?p=48851#comment-990169</guid>

					<description><![CDATA[I thought the backlog was down so low now that un-expedited time to 1st action was about as quick as the expedited time to 1st action of a few years past. Or am I thinking of some other Patent Office?]]></description>
			<content:encoded><![CDATA[ <p>I thought the backlog was down so low now that un-expedited time to 1st action was about as quick as the expedited time to 1st action of a few years past. Or am I thinking of some other Patent Office?</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
