Opposition · USPTO

Opposition 91206357

OtherUSPTO

Opposition 91206357 at USPTO between John Wayne Enterprises, LLC and Jon Wayne Heating & Air Conditioning, Ltd., over the mark JON WAYNE HEATING & AIR CONDITIONING, LTD., filed Aug 1, 2012. Status in the office record: other.

Status
Other
Result
Other
Filed
Aug 1, 2012
Marks involved
5
Parties

Who is involved

The parties as named in the office record.

Opponent

John Wayne Enterprises, LLC

Respondent

Jon Wayne Heating & Air Conditioning, Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the JON WAYNE HEATING & AIR CONDITIONING, LTD. filing.

  1. JON WAYNE HEATING & AIR CONDITIONING, LTD. filed

    Application 85430822 filed at the USPTO.
  2. Opposition filed

    John Wayne Enterprises, LLC started opposition 91206357 at USPTO against JON WAYNE HEATING & AIR CONDITIONING, LTD..
Marks

Marks involved

1 contested mark, 4 marks the challenger relies on.

MarkRoleApplicationOffice
JON WAYNE HEATING & AIR CONDITIONING, LTD.Contested85430822USPTO
JOHN WAYNERelied on73619940USPTO
JOHN WAYNERelied on76546716USPTO
JOHN WAYNERelied on76546727USPTO
JOHN WAYNERelied on76631139USPTO
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_d774c476-6a55-4426-acee-c70a7c86984d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_d774c476-6a55-4426-acee-c70a7c86984d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91206357",
  "status": "other",
  "office_code": "US",
  "filed_date": "2012-08-01",
  "parties": [
    {
      "name": "John Wayne Enterprises, LLC",
      "role": "opponent"
    },
    {
      "name": "Jon Wayne Heating & Air Conditioning, Ltd.",
      "role": "respondent"
    }
  ]
}