Opposition · USPTO

Opposition 91202587

OtherUSPTO

Opposition 91202587 at USPTO between Compassion International, Inc. and Compassion4, Inc., over the mark COMPASSION4, filed Nov 17, 2011. Status in the office record: other.

View COMPASSION4Get this data via the API
Status
Other
Result
Other
Filed
Nov 17, 2011
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Opponent

Compassion International, Inc.

Company trademarks
Respondent

Compassion4, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the COMPASSION4 filing.

  1. COMPASSION4 filed

    Application 85342275 filed at the USPTO.

  2. Opposition filed

    Compassion International, Inc. started opposition 91202587 at USPTO against COMPASSION4.
Marks

Marks involved

1 contested mark, 6 marks the challenger relies on.

MarkRoleApplicationOffice
COMPASSION4Contested85342275USPTO
COMPASSIONRelied on73771658USPTO
COMPASSION RELEASING CHILDREN FROM POVERTY IN JESUS' NAMERelied on76059472USPTO
SPEAK UP WITH COMPASSIONRelied on76421461USPTO
COMPASSIONRelied on76588596USPTO
COMPASSION AT WORKRelied on76679200USPTO
COMPASSIONRelied on77859428USPTO
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_cabf2445-7581-453b-8486-0de793bfffdb
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_cabf2445-7581-453b-8486-0de793bfffdb",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91202587",
  "status": "other",
  "office_code": "US",
  "filed_date": "2011-11-17",
  "parties": [
    {
      "name": "Compassion International, Inc.",
      "role": "opponent"
    },
    {
      "name": "Compassion4, Inc.",
      "role": "respondent"
    }
  ]
}