Opposition · USPTO

Opposition 91202362

OtherUSPTO

Opposition 91202362 at USPTO between Apple Inc. and Harry N. Abrams, Inc., over the mark ABRAMS APPLESEED, filed Oct 31, 2011. Status in the office record: other.

View ABRAMS APPLESEEDGet this data via the API
Status
Other
Result
Other
Filed
Oct 31, 2011
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Harry N. Abrams, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the ABRAMS APPLESEED filing.

  1. ABRAMS APPLESEED filed

    Application 85203635 filed at the USPTO.

  2. Opposition filed

    Apple Inc. started opposition 91202362 at USPTO against ABRAMS APPLESEED.
Marks

Marks involved

2 contested marks, 8 marks the challenger relies on.

MarkRoleApplicationOffice
ABRAMS APPLESEEDContested85203635USPTO
APPLESEED BOOKSContested85203642USPTO
APPLERelied on73120444USPTO
[Design mark]Relied on73162799USPTO
APPLERelied on76116541USPTO
[Design mark]Relied on76117498USPTO
[Design mark]Relied on76426501USPTO
APPLERelied on77172511USPTO
[Design mark]Relied on77648705USPTO
[Design mark]Relied on78943482USPTO
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_f10c05d6-2880-4173-91ce-6e9a667d808a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_f10c05d6-2880-4173-91ce-6e9a667d808a",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91202362",
  "status": "other",
  "office_code": "US",
  "filed_date": "2011-10-31",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Harry N. Abrams, Inc.",
      "role": "respondent"
    }
  ]
}