Opposition · USPTO

Opposition 91254032

OtherUSPTO

Opposition 91254032 at USPTO between Quantum Corporation and William Ragan, over the mark QUANTUM LOCK, filed Feb 12, 2020. Status in the office record: other.

Status
Other
Result
Other
Filed
Feb 12, 2020
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Quantum Corporation

Company trademarks
Respondent

William Ragan

Timeline

How the case has moved

Dates from the USPTO record and the QUANTUM LOCK filing.

  1. QUANTUM LOCK filed

    Application 88314692 filed at the USPTO.
  2. Opposition filed

    Quantum Corporation started opposition 91254032 at USPTO against QUANTUM LOCK.
Marks

Marks involved

1 contested mark, 12 marks the challenger relies on.

MarkRoleApplicationOffice
QUANTUM LOCKContested88314692USPTO
QUANTUMRelied on72327773USPTO
QUANTUMRelied on73127739USPTO
QUANTUMRelied on74242149USPTO
QUANTUMRelied on75052261USPTO
QUANTUMRelied on75387699USPTO
QUANTUMRelied on75601999USPTO
QUANTUMRelied on75604153USPTO
QUANTUMRelied on75608837USPTO
QUANTUM VISIONRelied on77530641USPTO
QUANTUM DX-SERIESRelied on85476482USPTO
QUANTUMRelied on86066721USPTO

+1 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_4bb80374-2559-44a0-a351-416fc2064efe
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_4bb80374-2559-44a0-a351-416fc2064efe",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91254032",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-02-12",
  "parties": [
    {
      "name": "Quantum Corporation",
      "role": "opponent"
    },
    {
      "name": "William  Ragan",
      "role": "respondent"
    }
  ]
}