Opposition · USPTO

Opposition 91180798

OtherUSPTO

Opposition 91180798 at USPTO between CaseMark, Inc. and Christopher P. Santos, over the mark XX, filed Nov 19, 2007. Status in the office record: other.

Status
Other
Result
Other
Filed
Nov 19, 2007
Marks involved
14
Parties

Who is involved

The parties as named in the office record.

Opponent

CaseMark, Inc.

Respondent

Christopher P. Santos

Timeline

How the case has moved

Dates from the USPTO record and the XX filing.

  1. XX filed

    Application 78819446 filed at the USPTO.
  2. Opposition filed

    CaseMark, Inc. started opposition 91180798 at USPTO against XX.
Marks

Marks involved

1 contested mark, 13 marks the challenger relies on.

MarkRoleApplicationOffice
XXContested78819446USPTO
TESTED XXRelied on71013405USPTO
CASE XXRelied on71553070USPTO
CASE TESTED XXRelied on71553071USPTO
XX-CHANGERRelied on73702146USPTO
CASE XX SELECTRelied on75209472USPTO
CASE XXRelied on75694840USPTO
CASE XXRelied on75695687USPTO
CASE XXRelied on76285953USPTO
CASE XXRelied on76386007USPTO
CASE XXRelied on76475972USPTO
CASE AMERICAN WORKMAN XX MADE BY AMERICAN WORKMEN FOR AMERICAN WORKMENRelied on76476456USPTO

+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_e8bbc187-bb31-4cb8-b509-2933b1e46c67
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_e8bbc187-bb31-4cb8-b509-2933b1e46c67",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91180798",
  "status": "other",
  "office_code": "US",
  "filed_date": "2007-11-19",
  "parties": [
    {
      "name": "CaseMark, Inc.",
      "role": "opponent"
    },
    {
      "name": "Christopher P. Santos",
      "role": "respondent"
    }
  ]
}