Opposition · USPTO

Opposition 91211848

OtherUSPTO

Opposition 91211848 at USPTO between Cleveland Indians Baseball Company Limited Partnership and Light Tribe Creations N.V., over the mark LIGHT TRIBE, filed Sep 30, 2015. Status in the office record: other.

View LIGHT TRIBEGet this data via the API
Status
Other
Result
Other
Filed
Sep 30, 2015
Marks involved
6
Parties

Who is involved

The parties as named in the office record.

Opponent

Cleveland Indians Baseball Company Limited Partnership

Respondent

Light Tribe Creations N.V.

Timeline

How the case has moved

Dates from the USPTO record and the LIGHT TRIBE filing.

  1. LIGHT TRIBE filed

    Application 79108570 filed at the USPTO.

  2. Opposition filed

    Cleveland Indians Baseball Company Limited Partnership started opposition 91211848 at USPTO against LIGHT TRIBE.
Marks

Marks involved

1 contested mark, 5 marks the challenger relies on.

MarkRoleApplicationOffice
LIGHT TRIBEContested79108570USPTO
THE TRIBERelied on74321715USPTO
TRIBE TIMERelied on77296666USPTO
IT'S TRIBE TIME NOWRelied on77296679USPTO
TRIBERelied on78743054USPTO
TRIBERelied on78743057USPTO
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_936e5064-1644-422f-b7cc-5de5e0d1f385
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_936e5064-1644-422f-b7cc-5de5e0d1f385",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91211848",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-09-30",
  "parties": [
    {
      "name": "Cleveland Indians Baseball Company Limited Partnership",
      "role": "opponent"
    },
    {
      "name": "Light Tribe Creations N.V.",
      "role": "respondent"
    }
  ]
}