1. Home
  2. |Insights
  3. |Inadequate Justification for Restrictive Requirements Leads to Injunction

Inadequate Justification for Restrictive Requirements Leads to Injunction

Client Alert | less than 1 min read | 01.10.11

After having been thrown out of GAO for purportedly not being an interested party to challenge Interior’s restriction of its procurement of a department-wide messaging and cloud computing system to Microsoft resellers on the GSA schedule, Google found a more sympathetic ear, and standing to complain, in the CFC. In Google, Inc. v. U.S. (Jan. 4, 2011), the court found that Interior had failed to take several of the procedural steps required by CICA and the FAR to justify the restrictive specification of Microsoft products, enjoined the procurement, and remanded the matter to the agency for it to follow the correct steps of the process.

Contacts

Insights

Client Alert | 2 min read | 11.14.25

Defining Claim Terms by Implication: Lexicography Lessons from Aortic Innovations LLC v. Edwards Lifesciences Corporation

Claim construction is a key stage of most patent litigations, where the court must decide the meaning of any disputed terms in the patent claims.  Generally, claim terms are given their plain and ordinary meaning except under two circumstances: (1) when the patentee acts as its own lexicographer and sets out a definition for the term; and (2) when the patentee disavows the full scope of the term either in the specification or during prosecution.  Thorner v. Sony Comput. Ent. Am. LLC, 669 F.3d 1362, 1365 (Fed. Cir. 2012).  The Federal Circuit’s recent decision in Aortic Innovations LLC v. Edwards Lifesciences Corp. highlights that patentees can act as their own lexicographers through consistent, interchangeable usage of terms across the specification, effectively defining terms by implication....