Opposition · USPTO

Opposition 91251667

OtherUSPTO

Opposition 91251667 at USPTO between Apple Inc. and Share Our Strength, over the mark [Design Mark], filed Oct 16, 2019. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 16, 2019
Marks involved
16
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Share Our Strength

Timeline

How the case has moved

Dates from the USPTO record and the [Design Mark] filing.

  1. [Design Mark] filed

    Application 87939774 filed at the USPTO.
  2. Opposition filed

    Apple Inc. started opposition 91251667 at USPTO against [Design Mark].
Marks

Marks involved

1 contested mark, 15 marks the challenger relies on.

MarkRoleApplicationOffice
[Design mark]Contested87939774USPTO
[Design mark]Relied on76426501USPTO
APPLERelied on77172511USPTO
APPLE STORERelied on77388365USPTO
APPLERelied on77428980USPTO
APPLECARERelied on77499837USPTO
[Design mark]Relied on77648705USPTO
[Design mark]Relied on78156920USPTO
[Design mark]Relied on78943482USPTO
APPLE WATCHRelied on86389914USPTO
APPLE WATCHRelied on86390028USPTO
WATCHRelied on86390778USPTO

+4 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_5d05a458-1381-4588-8da0-3bf6b985381b
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_5d05a458-1381-4588-8da0-3bf6b985381b",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91251667",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-10-16",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Share Our Strength",
      "role": "respondent"
    }
  ]
}