Opposition · USPTO

Opposition 91235600

OtherUSPTO

Opposition 91235600 at USPTO between La-Z-Boy Incorporated and PuTwo Inc., over the mark LAZYCAT, filed Jul 17, 2017. Status in the office record: other.

Status
Other
Result
Other
Filed
Jul 17, 2017
Marks involved
18
Parties

Who is involved

The parties as named in the office record.

Opponent

La-Z-Boy Incorporated

Company trademarks
Respondent

PuTwo Inc.

Timeline

How the case has moved

Dates from the USPTO record and the LAZYCAT filing.

  1. LAZYCAT filed

    Application 87304897 filed at the USPTO.
  2. Opposition filed

    La-Z-Boy Incorporated started opposition 91235600 at USPTO against LAZYCAT.
Marks

Marks involved

2 contested marks, 16 marks the challenger relies on.

MarkRoleApplicationOffice
LAZYCATContested87304897USPTO
LAZYCATContested87304914USPTO
LA-Z-BOY CLASSICSRelied on73732043USPTO
LA-Z-BOYRelied on73744482USPTO
LA-Z-BOY FURNITURE GALLERIESRelied on74207077USPTO
LA-Z-TIMERelied on74273131USPTO
LA-Z-TOUCHRelied on74399703USPTO
LA-Z-BOYRelied on74409893USPTO
LAZBOYRelied on76304425USPTO
LA-Z-GIRLRelied on76449897USPTO
LAZBOYRelied on76505203USPTO
LAZY BOYRelied on76544909USPTO

+6 more marks in this case

API

Get this data via the API

Every fact on this page comes from the Signa API. Track oppositions and cancellations on any mark with one request.

  • GET/v1/proceedings/{id}

    Parties, dates, outcome and every mark in the case

  • GET/v1/proceedings?trademark_id={trademark_id}

    Every proceeding on a mark

GET /v1/proceedings/{id}
ID=prc_9629948d-76ef-43fd-abf3-0cc41d1ff8fa
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_9629948d-76ef-43fd-abf3-0cc41d1ff8fa",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91235600",
  "status": "other",
  "office_code": "US",
  "filed_date": "2017-07-17",
  "parties": [
    {
      "name": "La-Z-Boy Incorporated",
      "role": "opponent"
    },
    {
      "name": "PuTwo Inc.",
      "role": "respondent"
    }
  ]
}