Opposition · USPTO

Opposition 91181791

OtherUSPTO

Opposition 91181791 at USPTO between Ford Motor Company and Sager, R David, over the mark ROCKY FORD, filed Jan 9, 2008. Status in the office record: other.

View ROCKY FORDGet this data via the API
Status
Other
Result
Other
Filed
Jan 9, 2008
Marks involved
19
Parties

Who is involved

The parties as named in the office record.

Opponent

Ford Motor Company

Company trademarks
Respondent

Sager, R David

Timeline

How the case has moved

Dates from the USPTO record and the ROCKY FORD filing.

  1. ROCKY FORD filed

    Application 78960962 filed at the USPTO.

  2. Opposition filed

    Ford Motor Company started opposition 91181791 at USPTO against ROCKY FORD.
Marks

Marks involved

1 contested mark, 18 marks the challenger relies on.

MarkRoleApplicationOffice
ROCKY FORDContested78960962USPTO
FORDRelied on71041417USPTO
FORDRelied on72002776USPTO
FORDRelied on74231430USPTO
FORDRelied on74429898USPTO
FORDRelied on74459532USPTO
FORDRelied on74459539USPTO
FORDRelied on74459557USPTO
FORDRelied on74459558USPTO
FORDRelied on75164745USPTO
FORDRelied on75249541USPTO
FORDRelied on76276250USPTO

+7 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_bd3dba82-e5d7-4178-83e3-ba97c3c34b07
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_bd3dba82-e5d7-4178-83e3-ba97c3c34b07",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91181791",
  "status": "other",
  "office_code": "US",
  "filed_date": "2008-01-09",
  "parties": [
    {
      "name": "FORD MOTOR COMPANY",
      "role": "opponent"
    },
    {
      "name": "Sager, R David",
      "role": "respondent"
    }
  ]
}