Opposition 91200926
OtherUSPTO
Opposition 91200926 at USPTO between Apple Inc. and Elliott Bay Communications, Inc., over the mark APPLE.AERO, filed Jul 27, 2011. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Jul 27, 2011
- Marks involved
- 11
Parties
Who is involved
The parties as named in the office record.
Opponent
Apple Inc.
Respondent
Elliott Bay Communications, Inc.
Timeline
How the case has moved
Dates from the USPTO record and the APPLE.AERO filing.
APPLE.AERO filed
Application 85139067 filed at the USPTO.Opposition filed
Apple Inc. started opposition 91200926 at USPTO against APPLE.AERO.
Marks
Marks involved
1 contested mark, 10 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| APPLE.AERO | Contested | 85139067 | USPTO |
| APPLE | Relied on | 73120444 | USPTO |
| [Design mark] | Relied on | 73162799 | USPTO |
| APPLE | Relied on | 74660120 | USPTO |
| [Design mark] | Relied on | 76426501 | USPTO |
| [Design mark] | Relied on | 76432531 | USPTO |
| APPLE | Relied on | 77172511 | USPTO |
| [Design mark] | Relied on | 77648705 | USPTO |
| [Design mark] | Relied on | 78146716 | USPTO |
| [Design mark] | Relied on | 78157042 | USPTO |
| APPLE | Relied on | 78170383 | 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_8170aa4a-1247-486f-8e66-b7877f53fb60
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_8170aa4a-1247-486f-8e66-b7877f53fb60",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91200926",
"status": "other",
"office_code": "US",
"filed_date": "2011-07-27",
"parties": [
{
"name": "Apple Inc.",
"role": "opponent"
},
{
"name": "Elliott Bay Communications, Inc.",
"role": "respondent"
}
]
}