Opposition · USPTO

Opposition 91191698

OtherUSPTO

Opposition 91191698 at USPTO between McDonald's Corporation and Lance R. Kaufman, over the mark MCPHONE, filed Aug 28, 2009. Status in the office record: other.

Status
Other
Result
Other
Filed
Aug 28, 2009
Marks involved
28
Parties

Who is involved

The parties as named in the office record.

Opponent

McDonald's Corporation

Company trademarks
Respondent

Lance R. Kaufman

Timeline

How the case has moved

Dates from the USPTO record and the MCPHONE filing.

  1. MCPHONE filed

    Application 77650095 filed at the USPTO.
  2. Opposition filed

    McDonald's Corporation started opposition 91191698 at USPTO against MCPHONE.
Marks

Marks involved

1 contested mark, 27 marks the challenger relies on.

MarkRoleApplicationOffice
MCPHONEContested77650095USPTO
MCDONALD'SRelied on72119302USPTO
MCDONALDLANDRelied on72398083USPTO
MC DOUBLERelied on73370485USPTO
MORNING MONEYRelied on73370586USPTO
MCHAPPY DAYRelied on73373321USPTO
MRelied on73394630USPTO
M MCDONALDSRelied on73395990USPTO
MCMUFFINRelied on73465519USPTO
MCJOBSRelied on73480984USPTO
MCSTOPRelied on73615990USPTO
MCBUCKSRelied on73649751USPTO

+16 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_ddabf778-5ea0-4e88-b678-f4953ebddfd2
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_ddabf778-5ea0-4e88-b678-f4953ebddfd2",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91191698",
  "status": "other",
  "office_code": "US",
  "filed_date": "2009-08-28",
  "parties": [
    {
      "name": "McDonald's Corporation",
      "role": "opponent"
    },
    {
      "name": "Lance R. Kaufman",
      "role": "respondent"
    }
  ]
}