Opposition · USPTO

Opposition 91221475

OtherUSPTO

Opposition 91221475 at USPTO between Ford Motor Company and Shannon Ford New York LLC, over the mark SHANNON FORD NEW YORK, filed Apr 13, 2015. Status in the office record: other.

View SHANNON FORD NEW YORKGet this data via the API
Status
Other
Result
Other
Filed
Apr 13, 2015
Marks involved
8
Parties

Who is involved

The parties as named in the office record.

Opponent

Ford Motor Company

Company trademarks
Respondent

Shannon Ford New York LLC

Timeline

How the case has moved

Dates from the USPTO record and the SHANNON FORD NEW YORK filing.

  1. SHANNON FORD NEW YORK filed

    Application 86289338 filed at the USPTO.

  2. Opposition filed

    Ford Motor Company started opposition 91221475 at USPTO against SHANNON FORD NEW YORK.
Marks

Marks involved

1 contested mark, 7 marks the challenger relies on.

MarkRoleApplicationOffice
SHANNON FORD NEW YORKContested86289338USPTO
FORDRelied on71041417USPTO
FORDRelied on72002776USPTO
FORDRelied on74459539USPTO
FORDRelied on74459560USPTO
FORDRelied on74459675USPTO
FORD MOTOR COMPANY OFFICIAL LICENSED PRODUCTRelied on74467857USPTO
FORDRelied on75020547USPTO
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_d68db531-1d51-4485-9fb3-c44b0f18bd5b
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_d68db531-1d51-4485-9fb3-c44b0f18bd5b",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91221475",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-04-13",
  "parties": [
    {
      "name": "Ford Motor Company",
      "role": "opponent"
    },
    {
      "name": "Shannon Ford New York LLC",
      "role": "respondent"
    }
  ]
}