Opposition · USPTO

Opposition 91191016

OtherUSPTO

Opposition 91191016 at USPTO between Intellectual Reserve, Inc. and Kendal M. Sheets, over the mark SECRET MORMON, filed Jul 13, 2009. Status in the office record: other.

View SECRET MORMONGet this data via the API
Status
Other
Result
Other
Filed
Jul 13, 2009
Marks involved
8
Parties

Who is involved

The parties as named in the office record.

Opponent

Intellectual Reserve, Inc.

Company trademarks
Respondent

Kendal M. Sheets

Timeline

How the case has moved

Dates from the USPTO record and the SECRET MORMON filing.

  1. SECRET MORMON filed

    Application 77337325 filed at the USPTO.

  2. Opposition filed

    Intellectual Reserve, Inc. started opposition 91191016 at USPTO against SECRET MORMON.
Marks

Marks involved

1 contested mark, 7 marks the challenger relies on.

MarkRoleApplicationOffice
SECRET MORMONContested77337325USPTO
MORMON HANDICRAFTRelied on73592323USPTO
MORMON HANDICRAFTRelied on73592324USPTO
MORMON TABERNACLE CHOIRRelied on76340212USPTO
BOOK OF MORMONRelied on76405608USPTO
MORMON TABERNACLE CHOIRRelied on76505493USPTO
MORMON.ORGRelied on77179068USPTO
MORMONRelied on78977858USPTO
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_fd5c84ca-22b7-4cb6-b793-dbb4fa0cf6fd
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_fd5c84ca-22b7-4cb6-b793-dbb4fa0cf6fd",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91191016",
  "status": "other",
  "office_code": "US",
  "filed_date": "2009-07-13",
  "parties": [
    {
      "name": "Intellectual Reserve, Inc.",
      "role": "opponent"
    },
    {
      "name": "Kendal M. Sheets",
      "role": "respondent"
    }
  ]
}