Bd. of Regents, Univ. of Wis. v. Phoenix Intern.

630 F.3d 570, 2010 U.S. App. LEXIS 26269, 2010 WL 5295853
CourtCourt of Appeals for the Seventh Circuit
DecidedDecember 28, 2010
Docket08-4164
StatusPublished
Cited by1 cases

This text of 630 F.3d 570 (Bd. of Regents, Univ. of Wis. v. Phoenix Intern.) is published on Counsel Stack Legal Research, covering Court of Appeals for the Seventh Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Bd. of Regents, Univ. of Wis. v. Phoenix Intern., 630 F.3d 570, 2010 U.S. App. LEXIS 26269, 2010 WL 5295853 (7th Cir. 2010).

Opinion

630 F.3d 570 (2010)

BOARD OF REGENTS OF the UNIVERSITY OF WISCONSIN SYSTEM, Plaintiff-Appellee,
v.
PHOENIX INTERNATIONAL SOFTWARE, INC., Defendant-Appellant.

No. 08-4164.

United States Court of Appeals, Seventh Circuit.

Argued June 4, 2009.
Decided December 28, 2010.

*573 Anthony A. Tomaselli (argued), Quarles & Brady, Madison, WI, for Plaintiff-Appellee.

Jon E. Brightmire (argued), Doerner, Saunders, Daniel & Anderson, Tulsa, OK, for Defendant-Appellant.

Before FLAUM, WOOD, and TINDER, Circuit Judges.

TINDER, Circuit Judge.

Phoenix International Software created software that it called Condor and registered the CONDOR mark with the Patent and Trademark Office (PTO) for "computer software for on-line programming development, library management and system utilities functioning on mainframe systems." Phoenix used this mark since June 1978 and registered it in January 1997. The delay in registration was due to a prior, separate registered CONDOR mark not at issue here. (We are capitalizing CONDOR when we refer to the mark, as the parties have in their briefs.)

The Board of Regents of the University of Wisconsin System (to whom we will refer simply as Wisconsin, because it is an arm of the state) registered its own CONDOR mark with the PTO in 2001 for "computer network operating system software, downloadable from a global computer network, that delivers large amounts of computational power by utilizing idle computing resources in a network of individual computer workstations...." The question in this case is whether Wisconsin's CONDOR mark is likely to be confused with Phoenix's.

Phoenix filed a petition before the Trademark Trial and Appeal Board (TTAB) to cancel Wisconsin's registration on the grounds that Wisconsin's registration would create confusion in trade. See 15 U.S.C. § 1064 ("A petition to cancel a registration of a mark ... may ... be filed... by any person who believes that he is or will be damaged ... by the registration of a mark on the principal register...."). The confusion in trade allegation refers to 15 U.S.C. § 1052(d), which forbids the registration of a trademark that "[c]onsists of or comprises a mark which so resembles a mark registered in the [PTO] ... as to be likely, when used on or in connection with the goods of the applicant, to cause confusion, or to cause mistake, or to deceive...."

The TTAB granted the petition and cancelled Wisconsin's registration, finding that

the marks are identical in every aspect. In such cases, even when goods or services are not competitive or intrinsically related, the use of identical marks can lead to an assumption that there is a common source.... In addition, the parties' software performs similar functions and, therefore, we cannot find that they are used in unrelated fields. Even sophisticated purchasers would likely believe that there is some relationship or *574 association between the sources of the goods under these circumstances.

Phoenix Software Int'l v. Bd. of Regents of the Univ. of Wis. Sys., Cancellation No. 92042881, at 19 (T.T.A.B. Sept. 26, 2007) (quotations and citations omitted).

Wisconsin brought a civil action in federal district court pursuant to 15 U.S.C. § 1071(b) challenging the TTAB's decision. Phoenix counterclaimed, seeking damages from Wisconsin for trademark infringement and false designation of origin under the Lanham Act (15 U.S.C. §§ 1114, 1125(a)); it also raised state law claims that it later voluntarily dismissed with prejudice. The district court dismissed Phoenix's federal counterclaims on sovereign immunity grounds and granted Wisconsin's motion for summary judgment, reversing the TTAB's determination. Phoenix appeals.

I. Standard of Review

The standard of review in this case is complicated by its initial status as a matter before the TTAB. After losing there, Wisconsin had two options: take an appeal directly to the Court of Appeals for the Federal Circuit or institute an action in a district court. See 15 U.S.C. § 1071. The procedure for appeal to the Federal Circuit conforms to the familiar standard for administrative appeals. The parties present their case based on the closed record developed before the TTAB and the circuit court determines whether substantial evidence before the TTAB supported the decision. CAE, Inc. v. Clean Air Eng'g, Inc., 267 F.3d 660, 673, 675 & n. 9 (7th Cir. 2001).

The choice to institute an action in the district court allows Wisconsin the benefit of expanding the record by offering new evidence to fend off Phoenix's cancellation claim. We have described the district court option as "both an appeal and a new action, which allows the parties to request additional relief and to submit new evidence." Id. at 673; see also Aktieselskabet AF 21. November 2001 v. Fame Jeans Inc., 525 F.3d 8, 12-13 (D.C.Cir. 2008) ("[T]he court may consider both new issues and new evidence that were not before the TTAB."). But a court's posture when considering an appeal and new issues is different, particularly in terms of issues of fact, which we will see are the key issues in this case. There is tension between the level of deference an appellate court pays to the fact-finder (in this case, an administrative body) and the parties' opportunity to present new evidence. See CAE, 267 F.3d at 674 ("[T]he district court is an appellate reviewer of facts found by the TTAB and is also a fact-finder based on new evidence introduced to the court.").

The district court, relying on CAE, adopted a deferential substantial evidence standard to review the TTAB's findings. See id. at 676. The court described its role as one that "affords deference to the findings of fact made by the board but considers the board's decision de novo to the extent the parties present new evidence. The board's findings of fact are properly reviewed under the standard set forth in [the Administrative Procedure Act (APA)] which requires the court to set aside findings and conclusions `unsupported by substantial evidence.'" Bd. of Regents of the Univ. of Wis. Sys. v. Phoenix Software Int'l, Inc., No. 07 C 665, 2008 WL 4950016, at *8 (W.D.Wis. Nov. 18, 2008) (citing CAE, 267 F.3d at 674, 675-76). The district court's formulation of the interplay between both sets of evidence matches ours. "Although the district court's review of the TTAB's decision is considered de novo when the parties present new evidence and assert additional claims, the district court also must afford deference to the fact findings of the *575 TTAB." CAE, 267 F.3d at 674. (We note, however, that the D.C. Circuit has recently held that because the Lanham Act, 15 U.S.C. § 1071(b), provides for judicial review of TTAB decisions, the APA is not directly applicable. See Aktieselskabet, 525 F.3d at 14. The D.C. Circuit did not address how this would affect its deference to the TTAB's fact-finding, except to note that courts have interpreted

Free access — add to your briefcase to read the full text and ask questions with AI

Related

BOBAK SAUSAGE CO. v. a & J Seven Bridges, Inc.
805 F. Supp. 2d 503 (N.D. Illinois, 2011)

Cite This Page — Counsel Stack

Bluebook (online)
630 F.3d 570, 2010 U.S. App. LEXIS 26269, 2010 WL 5295853, Counsel Stack Legal Research, https://law.counselstack.com/opinion/bd-of-regents-univ-of-wis-v-phoenix-intern-ca7-2010.