Opposition · USPTO

Opposition 91199635

OtherUSPTO

Opposition 91199635 at USPTO between Penguin Books Limited and Swartz Enterprises, Inc., over the mark PURPLEPENGUIN, filed May 2, 2011. Status in the office record: other.

View PURPLEPENGUINGet this data via the API
Status
Other
Result
Other
Filed
May 2, 2011
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

Penguin Books Limited

Company trademarks
Respondent

Swartz Enterprises, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the PURPLEPENGUIN filing.

  1. PURPLEPENGUIN filed

    Application 85062344 filed at the USPTO.

  2. Opposition filed

    Penguin Books Limited started opposition 91199635 at USPTO against PURPLEPENGUIN.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
PURPLEPENGUINContested85062344USPTO
[Design mark]Relied on71615020USPTO
PENGUINRelied on71619310USPTO
PENGUINRelied on73586327USPTO
[Design mark]Relied on74435477USPTO
PENGUINRelied on76333015USPTO
[Design mark]Relied on76333016USPTO
[Design mark]Relied on76333017USPTO
PENGUIN CORERelied on77936257USPTO
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_b695529b-256e-4e0e-adc6-4e4a781e8801
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_b695529b-256e-4e0e-adc6-4e4a781e8801",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91199635",
  "status": "other",
  "office_code": "US",
  "filed_date": "2011-05-02",
  "parties": [
    {
      "name": "Penguin Books Limited",
      "role": "opponent"
    },
    {
      "name": "Swartz Enterprises, Inc.",
      "role": "respondent"
    }
  ]
}