Opposition · USPTO

Opposition 91287962

OtherUSPTO

Opposition 91287962 at USPTO between Hachette Filipacchi Presse and Shenzhen Aike Technology Co., Ltd., over the mark ELLEMAKE, filed Oct 31, 2023. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 31, 2023
Marks involved
37
Parties

Who is involved

The parties as named in the office record.

Opponent

Hachette Filipacchi Presse

Respondent

Shenzhen Aike Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the ELLEMAKE filing.

  1. ELLEMAKE filed

    Application 97901937 filed at the USPTO.
  2. Opposition filed

    Hachette Filipacchi Presse started opposition 91287962 at USPTO against ELLEMAKE.
Marks

Marks involved

1 contested mark, 36 marks the challenger relies on.

MarkRoleApplicationOffice
ELLEMAKEContested97901937USPTO
ELLERelied on72157211USPTO
ELLERelied on72237756USPTO
ELLERelied on72276692USPTO
ELLERelied on73452244USPTO
ELLERelied on73452261USPTO
ELLERelied on73452264USPTO
ELLERelied on73512968USPTO
ELLERelied on73566634USPTO
ELLERelied on73566750USPTO
ELLERelied on73585396USPTO
ELLERelied on73814081USPTO

+25 more marks in this case

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_7c05901b-0c58-4696-8125-7aaecd27cdef
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7c05901b-0c58-4696-8125-7aaecd27cdef",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91287962",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-10-31",
  "parties": [
    {
      "name": "Hachette Filipacchi Presse",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Aike Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}