Opposition · USPTO

Opposition 91200892

OtherUSPTO

Opposition 91200892 at USPTO between McDonald's Corporation and Mccrown, over the mark MCCROWN, filed Jul 26, 2011. Status in the office record: other.

View MCCROWNGet this data via the API
Status
Other
Result
Other
Filed
Jul 26, 2011
Marks involved
16
Parties

Who is involved

The parties as named in the office record.

Opponent

McDonald's Corporation

Respondent

Mccrown

Timeline

How the case has moved

Dates from the USPTO record and the MCCROWN filing.

  1. MCCROWN filed

    Application 85162426 filed at the USPTO.

  2. Opposition filed

    McDonald's Corporation started opposition 91200892 at USPTO against MCCROWN.
Marks

Marks involved

1 contested mark, 15 marks the challenger relies on.

MarkRoleApplicationOffice
MCCROWNContested85162426USPTO
MCRIBRelied on73369229USPTO
MC DOUBLERelied on73370485USPTO
MCNUGGETSRelied on73396610USPTO
MCDONALDSRelied on73397665USPTO
MC DONALD'SRelied on73426936USPTO
MCMUFFINRelied on73465519USPTO
MCCLIPRelied on73804079USPTO
MCPOOLRelied on73820641USPTO
MCRelied on74192851USPTO
MCDIRECT SHARESRelied on74735211USPTO
MCSCHOLARRelied on75603447USPTO

+4 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_c4f818d3-2507-4ae7-a6d6-97a38099d3ac
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_c4f818d3-2507-4ae7-a6d6-97a38099d3ac",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91200892",
  "status": "other",
  "office_code": "US",
  "filed_date": "2011-07-26",
  "parties": [
    {
      "name": "McDonald's Corporation",
      "role": "opponent"
    },
    {
      "name": "Mccrown",
      "role": "respondent"
    }
  ]
}