Cancellation · CIPO

Cancellation 1

OtherCIPO

Cancellation 1 at CIPO between McFadden, Fincham and Conseillers Trevayne Inc., over the mark MONTANE, filed May 31, 2007. Status in the office record: other.

Status
Other
Result
Other
Filed
May 31, 2007
Marks involved
200
Parties

Who is involved

The parties as named in the office record.

Petitioner

McFadden, Fincham

Respondent

Conseillers Trevayne Inc.

Timeline

How the case has moved

Dates from the CIPO record and the MONTANE filing.

  1. MONTANE filed

    Application 1000151 filed at the CIPO.
  2. MONTANE registered

  3. Cancellation filed

    McFadden, Fincham started cancellation 1 at CIPO against MONTANE.
Marks

Marks involved

200 contested marks.

MarkRoleApplicationOffice
MONTANEContested1000151CIPO
UGGLY BOOTSContested1000217CIPO
KABOOContested1000218CIPO
CONNEXUS FINANCIAL GROUPContested1000471CIPO
SOLARAContested1000486CIPO
PEPPERSContested1000538CIPO
NEW FACESContested1000549CIPO
CLIFFHANGERContested1000580CIPO
ONSITE EQUIPMENT RENTALS DESIGNContested1000683CIPO
RICHTER SOURCINGContested1000728CIPO
RICHTER BI ADVISORContested1000729CIPO
RICHTER BI ANALYSERContested1000730CIPO

+188 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_2a669ecb-2359-45e5-9be9-51a80a9c2094
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_2a669ecb-2359-45e5-9be9-51a80a9c2094",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "1",
  "status": "other",
  "office_code": "CA",
  "filed_date": "2007-05-31",
  "parties": [
    {
      "name": "MCFADDEN, FINCHAM",
      "role": "petitioner"
    },
    {
      "name": "CONSEILLERS TREVAYNE INC.",
      "role": "respondent"
    }
  ]
}