Opposition · USPTO

Opposition 91201573

OtherUSPTO

Opposition 91201573 at USPTO between Apple Inc. and Barnes & Noble, Inc., over the mark [Design Mark], filed Sep 12, 2011. Status in the office record: other.

View [Design Mark]Get this data via the API
Status
Other
Result
Other
Filed
Sep 12, 2011
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Barnes & Noble, Inc.

Company trademarks
Timeline

How the case has moved

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

  1. [Design Mark] filed

    Application 85146646 filed at the USPTO.

  2. Opposition filed

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

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
[Design mark]Contested85146646USPTO
APPLERelied on73120444USPTO
[Design mark]Relied on73162799USPTO
APPLE STORERelied on75857151USPTO
[Design mark]Relied on76117498USPTO
APPLE STORERelied on76400649USPTO
[Design mark]Relied on76426501USPTO
APPLERelied on77172511USPTO
[Design mark]Relied on77648705USPTO
[Design mark]Relied on78155188USPTO
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_a68c06a2-263a-4931-916f-962b4c4fa52b
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_a68c06a2-263a-4931-916f-962b4c4fa52b",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91201573",
  "status": "other",
  "office_code": "US",
  "filed_date": "2011-09-12",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Barnes & Noble, Inc.",
      "role": "respondent"
    }
  ]
}