Opposition · USPTO

Opposition 91216852

OtherUSPTO

Opposition 91216852 at USPTO between PRL USA Holdings, Inc. and Gidon Anabi Blanga, over the mark HPC POLO, filed Jun 13, 2014. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 13, 2014
Marks involved
18
Parties

Who is involved

The parties as named in the office record.

Opponent

PRL USA Holdings, Inc.

Company trademarks
Respondent

Gidon Anabi Blanga

Timeline

How the case has moved

Dates from the USPTO record and the HPC POLO filing.

  1. HPC POLO filed

    Application 86040733 filed at the USPTO.
  2. Opposition filed

    PRL USA Holdings, Inc. started opposition 91216852 at USPTO against HPC POLO.
Marks

Marks involved

1 contested mark, 17 marks the challenger relies on.

MarkRoleApplicationOffice
HPC POLOContested86040733USPTO
POLORelied on71120684USPTO
POLORelied on71301815USPTO
POLO BY RALPH LAURENRelied on72406019USPTO
POLORelied on73333206USPTO
POLORelied on73630297USPTO
POLORelied on73655027USPTO
POLO BY RALPH LAURENRelied on73710831USPTO
POLORelied on73716257USPTO
POLO PRLCRelied on73832438USPTO
POLO SPORTRelied on74660375USPTO
POLORelied on75060273USPTO

+6 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_336879d2-bb91-4cdd-a9d3-8230478c9e42
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_336879d2-bb91-4cdd-a9d3-8230478c9e42",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91216852",
  "status": "other",
  "office_code": "US",
  "filed_date": "2014-06-13",
  "parties": [
    {
      "name": "PRL USA Holdings, Inc.",
      "role": "opponent"
    },
    {
      "name": "Gidon Anabi Blanga",
      "role": "respondent"
    }
  ]
}