Opposition · USPTO

Opposition 91179438

OtherUSPTO

Opposition 91179438 at USPTO between Apple Inc. and Douglass Rabess, over the mark ROTTEN@PPLE RECORDS, filed Sep 10, 2007. Status in the office record: other.

Status
Other
Result
Other
Filed
Sep 10, 2007
Marks involved
15
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Respondent

Douglass Rabess

Timeline

How the case has moved

Dates from the USPTO record and the ROTTEN@PPLE RECORDS filing.

  1. ROTTEN@PPLE RECORDS filed

    Application 78573123 filed at the USPTO.
  2. Opposition filed

    Apple Inc. started opposition 91179438 at USPTO against ROTTEN@PPLE RECORDS.
Marks

Marks involved

1 contested mark, 14 marks the challenger relies on.

MarkRoleApplicationOffice
ROTTEN@PPLE RECORDSContested78573123USPTO
APPLERelied on73120444USPTO
[Design mark]Relied on73162799USPTO
APPLERelied on74660120USPTO
[Design mark]Relied on74693680USPTO
[Design mark]Relied on74693838USPTO
APPLERelied on74693839USPTO
[Design mark]Relied on76426501USPTO
[Design mark]Relied on78146716USPTO
[Design mark]Relied on78155188USPTO
[Design mark]Relied on78157042USPTO
APPLERelied on78170383USPTO

+3 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_e9426a27-0984-4fc9-827e-21b7a71d5a7c
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_e9426a27-0984-4fc9-827e-21b7a71d5a7c",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91179438",
  "status": "other",
  "office_code": "US",
  "filed_date": "2007-09-10",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Douglass  Rabess",
      "role": "respondent"
    }
  ]
}