Opposition 91225666
OtherUSPTO
Opposition 91225666 at USPTO between Duke University and Aomori Hoei Industries, Ltd., over the mark DEVIL LINE, filed Jan 4, 2016. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Jan 4, 2016
- Marks involved
- 16
Parties
Who is involved
The parties as named in the office record.
Timeline
How the case has moved
Dates from the USPTO record and the DEVIL LINE filing.
DEVIL LINE filed
Application 79160917 filed at the USPTO.Opposition filed
Duke University started opposition 91225666 at USPTO against DEVIL LINE.
Marks
Marks involved
1 contested mark, 15 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| DEVIL LINE | Contested | 79160917 | USPTO |
| BLUE DEVILS | Relied on | 73587834 | USPTO |
| BLUE DEVILS | Relied on | 73588037 | USPTO |
| [Design mark] | Relied on | 74208937 | USPTO |
| [Design mark] | Relied on | 74209060 | USPTO |
| [Design mark] | Relied on | 74209061 | USPTO |
| D | Relied on | 74209062 | USPTO |
| DEVILS' DUPLICATES | Relied on | 75057960 | USPTO |
| DEVILNET | Relied on | 75892148 | USPTO |
| D | Relied on | 76465255 | USPTO |
| D | Relied on | 77409399 | USPTO |
| DUKE | Relied on | 78944306 | USPTO |
+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 /v1/proceedings/{id}
ID=prc_3a31be93-de48-46a2-9210-9b9cb2cc7f18
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_3a31be93-de48-46a2-9210-9b9cb2cc7f18",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91225666",
"status": "other",
"office_code": "US",
"filed_date": "2016-01-04",
"parties": [
{
"name": "Duke University",
"role": "opponent"
},
{
"name": "Aomori Hoei Industries, Ltd.",
"role": "respondent"
}
]
}