Opposition · USPTO

Opposition 91264320

OtherUSPTO

Opposition 91264320 at USPTO between Wrangler Apparel Corp. and Gary Clark, over the mark HOG WRANGLER, filed Aug 19, 2020. Status in the office record: other.

Status
Other
Result
Other
Filed
Aug 19, 2020
Marks involved
15
Parties

Who is involved

The parties as named in the office record.

Opponent

Wrangler Apparel Corp.

Company trademarks
Respondent

Gary Clark

Timeline

How the case has moved

Dates from the USPTO record and the HOG WRANGLER filing.

  1. HOG WRANGLER filed

    Application 88976711 filed at the USPTO.
  2. Opposition filed

    Wrangler Apparel Corp. started opposition 91264320 at USPTO against HOG WRANGLER.
Marks

Marks involved

1 contested mark, 14 marks the challenger relies on.

MarkRoleApplicationOffice
HOG WRANGLERContested88976711USPTO
WRANGLERRelied on71522610USPTO
WRANGLERRelied on72224579USPTO
WRANGLERRelied on72282320USPTO
WRANGLERRelied on72343463USPTO
WRANGLERRelied on73112793USPTO
WRANGLERRelied on73163186USPTO
WRANGLERRelied on73375489USPTO
WRANGLERRelied on73404739USPTO
WRANGLERRelied on77273014USPTO
WRANGLERRelied on77977590USPTO
WRANGLERRelied on77979041USPTO

+3 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_bfbc997f-c6d0-462e-a1e4-f00e054e350d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_bfbc997f-c6d0-462e-a1e4-f00e054e350d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91264320",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-08-19",
  "parties": [
    {
      "name": "Wrangler Apparel Corp.",
      "role": "opponent"
    },
    {
      "name": "Gary Clark",
      "role": "respondent"
    }
  ]
}