throbber
Case 1:19-cv-00859-RTH Document 69-1 Filed 01/21/22 Page 1 of 2
`
`Harel, Shahar (CIV)
`
`From:
`Sent:
`To:
`Cc:
`Subject:
`
`Shahar,
`
`
`Gerard O'Rourke <gorourke@okorlaw.com>
`Thursday, October 28, 2021 12:52 PM
`Harel, Shahar (CIV)
`Bolden, Scott (CIV); Kuan, Nelson (CIV); Sean O'Kelly; Laura Carrig; Thomas Kramer
`Re: [EXTERNAL] e-Numerate v United States - 19-859: Judge Albright's Claim
`Construction Order
`
`
`
`
`
`
`
`
`
`In light of the above, we would like to extend the next deadline by two weeks until November 22. I am using
`the exchange date we actually used for the definitions and adding two weeks from that. That also happens to be
`the Monday before Thanksgiving. Would you please advise whether you oppose that? If not, we'll map out a
`scheduling order and draft unopposed motion and send it to you for review.
`
`With regard to the order of claim construction briefing, it appears we are at an impasse on that. Is there any
`need to have a further meet and confer before we file a motion? Please advise. As we mentioned, the Judge has
`followed the most current version of Judge Albright's order in this proceeding. Our use of standard reservation
`of rights language in the cover document does not (in our view) provide a basis for departing from the Judge's
`practice.
`
`Finally, with regard to the claim constructions, we do not understand the Judge's Order to require that we
`propose definitions for your terms in the past exchange. We are reviewing your proposed definitions
`carefully. You should not assume that we will simply say "plain and ordinary meaning" for the terms and
`phrases you identified (but we have not). We are happy to discuss our thoughts with you on your terms during
`the meet and confer provided in the scheduling order.
`
`Very truly yours,
`
`Jerry
`
`
`
`On Wed, Oct 27, 2021 at 12:10 PM Harel, Shahar (CIV) <Shahar.Harel@usdoj.gov> wrote:
`
`Jerry,
`
`
`
`
`
`We do not agree to your suggestion that we modify the scheduling order to switch the order of the claim construction
`briefing. As you know, the parties have been operating under a schedule in which e-Numerate would file the opening
`brief for close to a year and now that the parties have exchanged terms for constructions and proposed constructions it
`does not make sense to dramatically change that procedure. This is especially the case since e-Numerate reserved
`
`1
`
`

`

`Case 1:19-cv-00859-RTH Document 69-1 Filed 01/21/22 Page 2 of 2
`
`“the right to modify, supplement, alter, delete and/or contradict any and all of [its] proposed constructions as
`this matter proceeds.” Plaintiffs’ Proposed Preliminary Constructions (emphasis added). Indeed, in its recent exchange
`e-Numerate did not even list the claim terms that Defendant identified for construction. Therefore, we understand
`that e-Numerate is proposing a “plain and ordinary” construction for these terms.
`
`
`
`
`
`Regards,
`
`Shahar
`
`
`
`
`
`From: Gerard O'Rourke <gorourke@okorlaw.com>
`Sent: Tuesday, October 26, 2021 8:17 AM
`To: Harel, Shahar (CIV) <Shahar.Harel@usdoj.gov>; Bolden, Scott (CIV) <Scott.Bolden@usdoj.gov>; Kuan, Nelson (CIV)
`<Nelson.Kuan@usdoj.gov>; Sean O'Kelly <sokelly@okorlaw.com>; Laura Carrig <lcarrig@okorlaw.com>
`Subject: [EXTERNAL] e-Numerate v United States - 19-859: Judge Albright's Claim Construction Order
`
`
`
`
`
`Shahar,
`
`
`
`
`
`Judge Albright in the Western District of Texas has recently modified his claim construction procedure in
`patent cases to specify that the Defendant files the first brief. Please see the attached at pages 4 - 5.
`
`
`
`
`
`Judge Holte has indicated that he wants to follow Judge Albright's procedures in previous scheduling orders in
`this matter. Will the Government consent to an amendment of the claim construction briefing to reflect Judge
`Albright's new procedure? Please advise.
`
`
`
`
`
`Thanks.
`
`
`
`
`
`Very truly yours,
`
`
`
`
`
`Jerry
`
`
`
`
`
`
`
`2
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket