Opposition · USPTO

Opposition 91290062

OtherUSPTO

Opposition 91290062 at USPTO between Chicago Cubs Baseball Club, LLC and Yating Liu, over the mark CUBFAVE, filed Feb 28, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
Feb 28, 2024
Marks involved
25
Parties

Who is involved

The parties as named in the office record.

Opponent

Chicago Cubs Baseball Club, LLC

Respondent

Yating Liu

Timeline

How the case has moved

Dates from the USPTO record and the CUBFAVE filing.

  1. CUBFAVE filed

    Application 97739480 filed at the USPTO.
  2. Opposition filed

    Chicago Cubs Baseball Club, LLC started opposition 91290062 at USPTO against CUBFAVE.
Marks

Marks involved

1 contested mark, 24 marks the challenger relies on.

MarkRoleApplicationOffice
CUBFAVEContested97739480USPTO
CUBSRelied on72278467USPTO
CUBSRelied on73011582USPTO
WRIGLEY FIELD HOME OF CHICAGO CUBSRelied on73752544USPTO
CHICAGO CUBSRelied on73752741USPTO
CUBSRelied on73753285USPTO
CHICAGO CUBSRelied on73762765USPTO
CUBS CARERelied on74173748USPTO
MR. CUBRelied on74446388USPTO
CUBSRelied on77609507USPTO
CUBSRelied on78633651USPTO
CUBSRelied on78633652USPTO

+13 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_0adb0fc7-5f0f-4ce7-92cf-e8c971c64f31
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_0adb0fc7-5f0f-4ce7-92cf-e8c971c64f31",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91290062",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-02-28",
  "parties": [
    {
      "name": "Chicago Cubs Baseball Club, LLC",
      "role": "opponent"
    },
    {
      "name": "Yating Liu",
      "role": "respondent"
    }
  ]
}