Opposition · USPTO

Opposition 91247582

OtherUSPTO

Opposition 91247582 at USPTO between Apple Inc. and Spencer Stewart, over the mark APPLES ARE ROUND, filed Apr 15, 2019. Status in the office record: other.

Status
Other
Result
Other
Filed
Apr 15, 2019
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Spencer Stewart

Timeline

How the case has moved

Dates from the USPTO record and the APPLES ARE ROUND filing.

  1. APPLES ARE ROUND filed

    Application 87872486 filed at the USPTO.
  2. Opposition filed

    Apple Inc. started opposition 91247582 at USPTO against APPLES ARE ROUND.
Marks

Marks involved

1 contested mark, 12 marks the challenger relies on.

MarkRoleApplicationOffice
APPLES ARE ROUNDContested87872486USPTO
APPLERelied on73120444USPTO
[Design mark]Relied on73162799USPTO
[Design mark]Relied on76426501USPTO
APPLERelied on77172511USPTO
[Design mark]Relied on77648705USPTO
APPLE WATCHRelied on86389914USPTO
APPLE WATCHRelied on86389945USPTO
APPLE WATCHRelied on86390028USPTO
WATCHRelied on86390818USPTO
WATCHRelied on86390853USPTO
[Design mark]Relied on86658546USPTO

+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_04f51f78-fabc-4078-a438-a045f027b823
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_04f51f78-fabc-4078-a438-a045f027b823",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91247582",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-04-15",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Spencer Stewart",
      "role": "respondent"
    }
  ]
}