Opposition · USPTO

Opposition 91264506

OtherUSPTO

Opposition 91264506 at USPTO between Apple Inc. and Gitanjali Saluja Taneja, over the mark FIVE APPLES, filed Aug 31, 2020. Status in the office record: other.

Status
Other
Result
Other
Filed
Aug 31, 2020
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Gitanjali Saluja Taneja

Timeline

How the case has moved

Dates from the USPTO record and the FIVE APPLES filing.

  1. FIVE APPLES filed

    Application 88648545 filed at the USPTO.
  2. Opposition filed

    Apple Inc. started opposition 91264506 at USPTO against FIVE APPLES.
Marks

Marks involved

1 contested mark, 12 marks the challenger relies on.

MarkRoleApplicationOffice
FIVE APPLESContested88648545USPTO
[Design mark]Relied on76426501USPTO
APPLERelied on77172511USPTO
APPLERelied on77428980USPTO
[Design mark]Relied on77648705USPTO
[Design mark]Relied on78156920USPTO
[Design mark]Relied on78943482USPTO
APPLE WATCHRelied on86389914USPTO
APPLE WATCHRelied on86390028USPTO
WATCHRelied on86390778USPTO
WATCHRelied on86390818USPTO
WATCH EDITIONRelied on86512737USPTO

+1 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_474799f6-2790-4ba9-a33b-2f389df8c521
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_474799f6-2790-4ba9-a33b-2f389df8c521",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91264506",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-08-31",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Gitanjali Saluja Taneja",
      "role": "respondent"
    }
  ]
}