Opposition · USPTO

Opposition 91252340

OtherUSPTO

Opposition 91252340 at USPTO between Chicago Cubs Baseball Club, LLC and Team Char Chalk, LLC, over the mark C, filed Nov 18, 2019. Status in the office record: other.

View CGet this data via the API
Status
Other
Result
Other
Filed
Nov 18, 2019
Marks involved
23
Parties

Who is involved

The parties as named in the office record.

Opponent

Chicago Cubs Baseball Club, LLC

Respondent

Team Char Chalk, LLC

Timeline

How the case has moved

Dates from the USPTO record and the C filing.

  1. C filed

    Application 88316329 filed at the USPTO.

  2. Opposition filed

    Chicago Cubs Baseball Club, LLC started opposition 91252340 at USPTO against C.
Marks

Marks involved

1 contested mark, 22 marks the challenger relies on.

MarkRoleApplicationOffice
CContested88316329USPTO
CUBSRelied on72278467USPTO
CUBSRelied on73011582USPTO
CRelied on73240066USPTO
CRelied on73393194USPTO
CRelied on73752545USPTO
CHICAGO CUBSRelied on73752742USPTO
CUBSRelied on73753285USPTO
CHICAGO CUBSRelied on73762807USPTO
CRelied on74552991USPTO
CRelied on76147633USPTO
CRelied on76159416USPTO

+11 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_a6327471-09f3-4b78-aff0-8fa460b1aa6a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_a6327471-09f3-4b78-aff0-8fa460b1aa6a",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91252340",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-11-18",
  "parties": [
    {
      "name": "Chicago Cubs Baseball Club, LLC",
      "role": "opponent"
    },
    {
      "name": "Team Char Chalk, LLC",
      "role": "respondent"
    }
  ]
}