Opposition · USPTO

Opposition 91243452

OtherUSPTO

Opposition 91243452 at USPTO between Chanel, Inc. and Nina Chanelli LLC, over the mark NINA CHANELLI, filed Sep 5, 2018. Status in the office record: other.

View NINA CHANELLIGet this data via the API
Status
Other
Result
Other
Filed
Sep 5, 2018
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

Chanel, Inc.

Company trademarks
Respondent

Nina Chanelli LLC

Timeline

How the case has moved

Dates from the USPTO record and the NINA CHANELLI filing.

  1. NINA CHANELLI filed

    Application 87401429 filed at the USPTO.

  2. Opposition filed

    Chanel, Inc. started opposition 91243452 at USPTO against NINA CHANELLI.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
NINA CHANELLIContested87401429USPTO
CHANELRelied on71205468USPTO
CHANELRelied on71332645USPTO
CHANELRelied on71550120USPTO
CHANELRelied on73139066USPTO
CHANELRelied on73359658USPTO
CHANELRelied on73494952USPTO
CHANEL CCRelied on73640896USPTO
CHANELRelied on73778300USPTO
CHANELRelied on74091901USPTO
CHANELRelied on76501797USPTO
CHANELRelied on76615092USPTO
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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_0f5d9063-5597-460d-8e0f-193c853b1b7d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_0f5d9063-5597-460d-8e0f-193c853b1b7d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91243452",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-09-05",
  "parties": [
    {
      "name": "Chanel, Inc.",
      "role": "opponent"
    },
    {
      "name": "Nina Chanelli LLC",
      "role": "respondent"
    }
  ]
}