Opposition · USPTO

Opposition 91180429

OtherUSPTO

Opposition 91180429 at USPTO between Ford Motor Company and Chic Optic Inc., over the mark LINCOLN ROAD, filed Oct 31, 2007. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 31, 2007
Marks involved
14
Parties

Who is involved

The parties as named in the office record.

Opponent

Ford Motor Company

Company trademarks
Respondent

Chic Optic Inc.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the LINCOLN ROAD filing.

  1. LINCOLN ROAD filed

    Application 77156608 filed at the USPTO.
  2. Opposition filed

    Ford Motor Company started opposition 91180429 at USPTO against LINCOLN ROAD.
Marks

Marks involved

1 contested mark, 13 marks the challenger relies on.

MarkRoleApplicationOffice
LINCOLN ROADContested77156608USPTO
LINCOLNRelied on71174171USPTO
LINCOLNRelied on71544440USPTO
LINCOLNRelied on73401444USPTO
LINCOLNRelied on74441531USPTO
LINCOLNRelied on74459544USPTO
LINCOLNRelied on74459545USPTO
LINCOLNRelied on74459667USPTO
LINCOLNRelied on75077984USPTO
LINCOLNRelied on75145828USPTO
LINCOLNRelied on75249531USPTO
LINCOLNRelied on75419707USPTO

+2 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_30e13111-408a-4f56-83d2-e1851bcb6319
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_30e13111-408a-4f56-83d2-e1851bcb6319",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91180429",
  "status": "other",
  "office_code": "US",
  "filed_date": "2007-10-31",
  "parties": [
    {
      "name": "Ford Motor Company",
      "role": "opponent"
    },
    {
      "name": "Chic Optic Inc.",
      "role": "respondent"
    }
  ]
}