throbber
Trademark Trial and Appeal Board Electronic Filing System. http://estta.uspto.gov
`
`ESTTA Tracking number:
`
`ESTTA1032022
`
`Filing date:
`
`01/28/2020
`
`IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`BEFORE THE TRADEMARK TRIAL AND APPEAL BOARD
`
`Proceeding
`
`91235429
`
`Party
`
`Correspondence
`Address
`
`Defendant
`Platform Beers LLC
`
`STEVEN E LAURIDSEN
`TUCKER ELLIS LLP
`950 MAIN AVE, STE 1100
`CLEVELAND, OH 44113-7213
`UNITED STATES
`trademarks@tuckerellis.com, carlos.garritano@tuckerellis.com,
`steven.lauridsen@tuckerellis.com, heather.barnes@tuckerellis.com, bri-
`an.brookey@tuckerellis.com
`216-696-3952
`
`Submission
`
`Filer's Name
`
`Filer's email
`
`Reply in Support of Motion
`
`Brian K. Brookey
`
`trademarks@tuckerellis.com, steven.lauridsen@tuckerellis.com, bri-
`an.brookey@tuckerellis.com, carlos.garritano@tuckerellis.com
`
`Signature
`
`Date
`
`/Brian K. Brookey/
`
`01/28/2020
`
`Attachments
`
`PLATFORM - Reply Brief Supporting Motion To Compel.pdf(312362 bytes )
`
`

`

`TRADEMARK
`Docket No. 015397-000016
`
`
`
`IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`TRADEMARK TRIAL AND APPEAL BOARD
`
`
`
`
`BOTTLE LOGIC BREWING LLC,
`
` Plaintiff/Bottle Logic,
`
` v.
`
`PLATFORM BEERS LLC,
`
` Defendant/Applicant.
`
`
`
`
`Opposition No. 91235429
`
`Serial No. 87/050,742
`Mark: PLATFORM BEER CO. & Design
`Filing Date: May 26, 2016
`Published: March 7, 2017
`
`
`Serial No. 87/056,210
`Mark: PLATFORM BEER CO. & Design
`Filing Date: June 1, 2016
`Published: March 7, 2017
`
`
`
`
`APPLICANT’S REPLY BRIEF IN FURTHER SUPPORT OF MOTION TO COMPEL
`RESPONSES TO INTERROGATORIES AND REQUESTS FOR PRODUCTION, AND
`TO DETERMINE SUFFICIENCY OF RESPONSES TO REQUESTS FOR ADMISSION
`
`
`
`
`I.
`
`
`
`INTRODUCTION
`
`Bottle Logic’s opposition to Platform’s motion to compel and to determine the
`
`sufficiency of responses to requests for admission demonstrates why the Board should grant
`
`Platform’s motion. In regrettable language, Bottle Logic attacks as “ridiculous” Platform’s
`
`attempts to obtain either facts supporting Bottle Logic’s contentions, or a representation by
`
`Bottle Logic that it will not make such contentions. Bottle Logic also either misapprehends or
`
`mischaracterizes the cases on which it relies. Bottle Logic cannot continue to prosecute a case
`
`while refusing to participate in good faith in the discovery process.
`
`
`
`
`1
`
`

`

`
`
`II.
`
`THE BOARD SHOULD ORDER BOTTLE LOGIC TO PRODUCE DOCUMENTS
`
`RESPONSIVE TO REQUEST FOR PRODUCTION NO. 28.
`
`Bottle Logic stands on its refusal to produce documents supporting or refuting its claims
`
`and defenses, claiming that it cannot possibly be expected to know what evidence in its
`
`possession supports its arguments. Platform’s request, of course, is very similar to what already
`
`is required by Rule 26(a)(1)(A)(ii) of the Federal Rules of Civil Procedure: identification or
`
`production of “all documents, electronically stored information, and tangible things that the
`
`disclosing party has in its possession, custody, or control and may use to support its claims or
`
`defenses, unless the use would be solely for impeachment.” If, as Bottle Logic contends,
`
`Platform’s use of the word “all” renders the request overly broad and the subject of the request
`
`requires Bottle Logic to divulge its “entire legal theory,” then the Federal Rules of Civil
`
`Procedure suffer from those same defects. Unless and until those Rules are amended or repealed,
`
`Bottle Logic must respond to the request as framed.
`
`Bottle Logic argues that the request is overly broad because it “might well encompass
`
`irrelevant information.” But Bottle Logic does not explain how documents that support its
`
`claims, or documents that contradict those claims, could possibly be “irrelevant.” Again, the text
`
`of Rule 26 is instructive: “Parties may obtain discovery regarding any nonprivileged matter that
`
`is relevant to any party’s claim or defense and proportional to the needs of the case….”
`
`Fed.R.Civ.P. 26(b)(1). By definition, a request for documents “supporting or refuting” a party’s
`
`claim or defense is relevant to such a claim or defense.
`
`Finally, Bottle Logic cites a series of cases for the proposition that requests for all
`
`documents “relating to” or “concerning” a topic are overly broad. See Carter v. Archdale Police
`
`
`
`
`2
`
`

`

`Dep’t, 2014 WL 1774471, at *5 (M.D.N.C.) May 2, 2014) and Sonnino v. Univ. of Kan. Hosp.
`
`Auth., 2004 WL 764085, at *5 (D. Kan. April 8, 2004). The problem for Bottle Logic is that
`
`Platform’s request does not ask for all documents “relating to” or “concerning” a particular topic.
`
`It is far narrower, asking for documents that either support or refute Bottle Logic’s claims. Thus,
`
`each of the cases on which Bottle Logic relies is inapposite.
`
`There is no basis for Bottle Logic’s refusal to produce documents that go to the heart of
`
`its claims, and Bottle Logic should be ordered to provide those documents to Platform.
`
`III. THE
`
`BOARD
`
`SHOULD
`
`COMPEL
`
`PROPER
`
`RESPONSES
`
`TO
`
`INTERROGATORY NOS. 8, 11, 13, AND 14.
`
`In its moving papers, Platform argued that proper discovery responses are essential to
`
`prevent trial by ambush. Bottle Logic’s response is to argue that trial by ambush is exactly its
`
`strategy, complaining that having to provide the factual bases for its claims would amount to a
`
`“sneak peek” of its arguments on the merits. 50 TTABVUE 5.
`
`As Platform has explained, the purpose of discovery is to provide just such a “sneak
`
`peek” by obtaining the factual and evidentiary support for a party’s claims. Bottle Logic tries to
`
`have it both ways, arguing that it does not have to provide any evidence as to any DuPont factor,
`
`while reserving the right to spring new theories on Platform in its trial brief. See id. The issues
`
`before the Board are simple: either Bottle Logic must provide the factual bases for its
`
`contentions as to each DuPont factor that is the subject of the disputed interrogatories, or Bottle
`
`Logic must represent that it will never argue those factors. Bottle Logic should not be permitted
`
`to withhold information in its possession, only to provide it for the first time at trial.
`
`
`
`
`3
`
`

`

`IV.
`
`BOTTLE LOGIC’S OPPOSITION CONFIRMS THAT THE BOARD SHOULD
`
`DEEM THE DISPUTED REQUESTS FOR ADMISSION ADMITTED
`
`Attempting to defend its refusal to admit or deny straightforward requests for admission,
`
`Bottle Logic argues that its ability to admit or deny those requests “hinges on the words
`
`Applicant selected in its requests.” 50 TTABVUE 6. Platform agrees. It asked Bottle Logic to
`
`admit whether certain marks and other third-party uses “depict” lightbulbs. The word “depict”
`
`means, among other things, to “represent by or as if by painting; portray; delineate”; or “to
`
`represent by or as if by a picture.” See https://www.dictionary.com/browse/depict?s=t and
`
`https://www.merriam-webster.com/dictionary/depict.
`
`There can be no question that each of the designs at issue in the disputed requests for
`
`admission “depicts” – i.e., includes a picture or other representation of – a lightbulb. The word
`
`“depict” is not, as Bottle Logic posits, “sloppy,” nor does it matter whether or not the depictions
`
`are “stylized” or contain additional matter. Despite Bottle Logic’s protestations to the contrary,
`
`in opposing Platform’s motion for summary judgment Bottle Logic had no difficulty
`
`acknowledging that cited third-party uses depicted lightbulbs. Bottle Logic argued that “the
`
`existence of third party registrations for or use of light bulbs, and the effect of such use and
`
`registrations on the scope of Bottle Logic’s rights in its mark” presented issues inappropriate for
`
`resolution on summary judgment. Bottle Logic also argued that the existence of third-party uses
`
`of light bulb designs is itself an issue of fact,” and that evidence of “beer logos that incorporate
`
`light bulbs does not meet the high burden of proof necessary to prevail in a summary judgment
`
`proceeding.” Bottle Logic also argued that “some designs that incorporate light bulb designs are
`
`more similar than others, as is the case in the present case.” Bottle Logic’s Combined Reply
`
`Brief in Support of its Motion for Partial Summary Judgment and Opposition and Response to
`
`
`
`
`4
`
`

`

`Applicant’s Cross-Motion for Summary Judgment, filed March 21, 2019 (36 TTABVUE), at
`
`p. 7 (emphasis added).
`
`Bottle Logic does not attempt to explain why it recognized previous registrations and
`
`third-party uses as depicting lightbulbs for purposes of summary judgment briefing, but is now
`
`incapable of doing so in response to discovery.
`
`In a last-ditch effort to justify its refusal to respond properly to requests for admission,
`
`Bottle Logic cites a Federal Circuit case for the proposition that “the term ‘depict’ is an exclusive
`
`closed-ended term that does not include additional unrecited elements or elements [sic].” order.
`
`50 TTABVUE 6, citing Mars Inc. v. H.J. Heinz Co., 377 F.3d 1369, 1376, 71 USPQ2d 1837,
`
`1843 (Fed. Cir. 2004). There are two fundamental problems with Bottle Logic’s argument. First,
`
`the Mars case on which it relies involves claim construction in a patent infringement case, and
`
`has no relevance to this opposition proceeding. And second, notwithstanding Bottle Logic’s
`
`misleading cite, Mars did not construe the term “depict” at all. In fact, that word does not appear
`
`in any context anywhere in that opinion. Bottle Logic is left with no factual or legal support for
`
`its claim that a design does not depict one feature if it contains others as well.
`
`Attempting to justify its refusal to admit very simple requests for admission, Bottle Logic
`
`derides the language of those requests as “sloppy,” while denying ever making the arguments
`
`that appear in its previous briefs, and citing case law that does not remotely stand for the
`
`proposition for which it is cited. The most appropriate remedy would be for the Board to deem
`
`each request admitted, just as Bottle Logic should have done in the first place.
`
`V.
`
`CONCLUSION
`
`Bottle Logic makes no secret of its strategy in this proceeding: to withhold until the last
`
`possible second the facts and documents that it plans to use to support its claims. In an effort to
`
`keep all its options open, Bottle Logic will not even respond properly to requests that it admit
`
`
`
`
`5
`
`

`

`certain facts that it already has admitted in its own prior representations in this proceeding. And
`
`Bottle Logic goes so far as to misrepresent the content of the discovery requests and the holding
`
`of the sole case on which it relies to justify its refusal to respond to requests for admission.
`
`It is time for the Board to put an end to these games so that the parties can litigate this
`
`case on the merits, with full understanding of each other’s contentions. Accordingly, the Board
`
`should order Bottle Logic to respond properly to Platform’s interrogatories and request for
`
`production, and should deem admitted each request for admission at issue in this motion.
`
`
`
`
`
`Respectfully submitted,
`
`Date: January 28, 2020
`
`TUCKER ELLIS, LLP
`
`By: /s/Brian K. Brookey_____
`Brian K. Brookey
`950 Main Avenue, Suite 1100
`Cleveland, Ohio 44113-7213
`Phone: 216-696-3952
`Fax:
`216-592-5009
`
`brian.brookey@tuckerellis.com
`steven.lauridsen@tuckerellis.com
`trademarks@tuckerellis.com
`carlos.garritano@tuckerellis.com
`heather.barnes@tuckerellis.com
`
`Attorney for Defendant/Applicant
`
`
`
`
`6
`
`

`

`CERTIFICATE OF SERVICE
`
`
`
`I certify that on the January 28, 2020, the foregoing APPLICANT’S REPLY BRIEF IN
`
`FURTHER
`
`SUPPORT OF MOTION TO COMPEL RESPONSES TO
`
`INTERROGATORIES AND REQUESTS FOR PRODUCTION, AND TO DETERMINE
`
`SUFFICIENCY OF RESPONSES TO REQUESTS FOR ADMISSION was sent via email to
`
`the following:
`
`
`
`
`
`
`
`
`
`DANIEL CHRISTOPHERSON
`
`LEHRMAN BEVERAGE LAW PLLC
`
`2911 HUNTER MILL RD STE 303
`
`OAKTON, VA 22124
`
`UNITED STATES
`
`dan.christopherson@bevalw.com, trademarks@bevlaw.com
`
`
`By: /s/Steven E. Lauridsen
`Steven E. Lauridsen
`
`
`4549278.2
`
`7
`
`

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