Opposition 91192276
OtherUSPTO
Opposition 91192276 at USPTO between Apple Inc. and Sherlock Kingsley Dow, over the mark APPLESEED ENGINEERING, filed Oct 14, 2009. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Oct 14, 2009
- Marks involved
- 11
Parties
Who is involved
The parties as named in the office record.
Respondent
Sherlock Kingsley Dow
Timeline
How the case has moved
Dates from the USPTO record and the APPLESEED ENGINEERING filing.
APPLESEED ENGINEERING filed
Application 77669549 filed at the USPTO.Opposition filed
Apple Inc. started opposition 91192276 at USPTO against APPLESEED ENGINEERING.
Marks
Marks involved
1 contested mark, 10 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| APPLESEED ENGINEERING | Contested | 77669549 | USPTO |
| APPLE | Relied on | 73120444 | USPTO |
| [Design mark] | Relied on | 73162799 | USPTO |
| APPLECARE | Relied on | 73425447 | USPTO |
| APPLE | Relied on | 74527910 | USPTO |
| APPLE STORE | Relied on | 76400649 | USPTO |
| [Design mark] | Relied on | 76426501 | USPTO |
| APPLECARE | Relied on | 77499829 | USPTO |
| [Design mark] | Relied on | 77648705 | USPTO |
| [Design mark] | Relied on | 78146716 | 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_da013f16-642c-4ef0-ae29-b964baff4481
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_da013f16-642c-4ef0-ae29-b964baff4481",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91192276",
"status": "other",
"office_code": "US",
"filed_date": "2009-10-14",
"parties": [
{
"name": "Apple Inc.",
"role": "opponent"
},
{
"name": "Sherlock Kingsley Dow",
"role": "respondent"
}
]
}