Opposition 91189249
OtherUSPTO
Opposition 91189249 at USPTO between Board of Regents, The University of Texas System and LonghornUp, Inc., over the mark LONGHORN UP, filed Mar 12, 2009. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Mar 12, 2009
- Marks involved
- 10
Parties
Who is involved
The parties as named in the office record.
Respondent
LonghornUp, Inc.
Timeline
How the case has moved
Dates from the USPTO record and the LONGHORN UP filing.
LONGHORN UP filed
Application 77533388 filed at the USPTO.Opposition filed
Board of Regents, The University of Texas System started opposition 91189249 at USPTO against LONGHORN UP.
Marks
Marks involved
1 contested mark, 9 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| LONGHORN UP | Contested | 77533388 | USPTO |
| LONGHORNS | Relied on | 73321983 | USPTO |
| LONGHORNS | Relied on | 73496763 | USPTO |
| [Design mark] | Relied on | 73637338 | USPTO |
| LONGHORNS | Relied on | 73637369 | USPTO |
| [Design mark] | Relied on | 73637611 | USPTO |
| TEXAS | Relied on | 74476553 | USPTO |
| UT | Relied on | 74476567 | USPTO |
| TEXAS LONGHORNS | Relied on | 77558123 | USPTO |
| TEXAS LONGHORNS | Relied on | 77558155 | USPTO |
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_236ef771-62f1-4ba9-9f1a-ee4bb32b452b
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_236ef771-62f1-4ba9-9f1a-ee4bb32b452b",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91189249",
"status": "other",
"office_code": "US",
"filed_date": "2009-03-12",
"parties": [
{
"name": "Board of Regents, The University of Texas System",
"role": "opponent"
},
{
"name": "LonghornUp, Inc.",
"role": "respondent"
}
]
}