Opposition 91203689
OtherUSPTO
Opposition 91203689 at USPTO between Exelon Corporation and Scansys CCTV Inc., over the mark EXELON, filed Feb 6, 2012. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Feb 6, 2012
- Marks involved
- 14
Parties
Who is involved
The parties as named in the office record.
Respondent
Scansys CCTV Inc.
Timeline
How the case has moved
Dates from the USPTO record and the EXELON filing.
EXELON filed
Application 85278495 filed at the USPTO.Opposition filed
Exelon Corporation started opposition 91203689 at USPTO against EXELON.
Marks
Marks involved
1 contested mark, 13 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| EXELON | Contested | 85278495 | USPTO |
| EXELON | Relied on | 75494120 | USPTO |
| EXELON | Relied on | 75979886 | USPTO |
| EXELON | Relied on | 76054187 | USPTO |
| EXELON | Relied on | 76054380 | USPTO |
| EXELON | Relied on | 76054381 | USPTO |
| EXELON | Relied on | 76054386 | USPTO |
| EXELON | Relied on | 76055033 | USPTO |
| EXELON | Relied on | 76055038 | USPTO |
| EXELON ENERGY | Relied on | 76115024 | USPTO |
| EXELON | Relied on | 77105327 | USPTO |
| EXEL N 2020 A LOW-CARBON ROADMAP | Relied on | 77465737 | USPTO |
+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_567b6951-0b0c-47e7-be00-22f62ec42e49
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_567b6951-0b0c-47e7-be00-22f62ec42e49",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91203689",
"status": "other",
"office_code": "US",
"filed_date": "2012-02-06",
"parties": [
{
"name": "Exelon Corporation",
"role": "opponent"
},
{
"name": "Scansys CCTV Inc.",
"role": "respondent"
}
]
}