Opposition 91228197
OtherUSPTO
Opposition 91228197 at USPTO between KIND Management Inc. and Da Kind Colorado, LLC, over the mark DAKIND COLORADO, filed Jun 1, 2016. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Jun 1, 2016
- Marks involved
- 11
Parties
Who is involved
The parties as named in the office record.
Opponent
KIND Management Inc.
Respondent
Da Kind Colorado, LLC
Timeline
How the case has moved
Dates from the USPTO record and the DAKIND COLORADO filing.
DAKIND COLORADO filed
Application 86694868 filed at the USPTO.Opposition filed
KIND Management Inc. started opposition 91228197 at USPTO against DAKIND COLORADO.
Marks
Marks involved
1 contested mark, 10 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| DAKIND COLORADO | Contested | 86694868 | USPTO |
| KIND | Relied on | 76596770 | USPTO |
| KIND | Relied on | 77333800 | USPTO |
| KIND FRUIT + NUT | Relied on | 77721453 | USPTO |
| KINDTASTIC | Relied on | 77816084 | USPTO |
| KINDELICIOUS | Relied on | 77816085 | USPTO |
| KIND | Relied on | 77827342 | USPTO |
| KINDINGS | Relied on | 77903894 | USPTO |
| KIND | Relied on | 77981723 | USPTO |
| KIND | Relied on | 86098903 | USPTO |
| KIND | Relied on | 86724964 | 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_eae8d209-8621-46cf-92cb-a78d9adbc375
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_eae8d209-8621-46cf-92cb-a78d9adbc375",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91228197",
"status": "other",
"office_code": "US",
"filed_date": "2016-06-01",
"parties": [
{
"name": "KIND Management Inc.",
"role": "opponent"
},
{
"name": "Da Kind Colorado, LLC",
"role": "respondent"
}
]
}