Opposition · USPTO

Opposition 91285872

OtherUSPTO

Opposition 91285872 at USPTO between HUGO BOSS Trade Mark Management GmbH & Co., KG and Melichsia Boss, over the mark MOCHA BOSS, filed Jul 5, 2023. Status in the office record: other.

Status
Other
Result
Other
Filed
Jul 5, 2023
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

HUGO BOSS Trade Mark Management GmbH & Co., KG

Company trademarks
Respondent

Melichsia Boss

Timeline

How the case has moved

Dates from the USPTO record and the MOCHA BOSS filing.

  1. MOCHA BOSS filed

    Application 97506145 filed at the USPTO.
  2. Opposition filed

    HUGO BOSS Trade Mark Management GmbH & Co., KG started opposition 91285872 at USPTO against MOCHA BOSS.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
MOCHA BOSSContested97506145USPTO
BOSS HUGO BOSSRelied on74352816USPTO
HUGO BOSSRelied on75367506USPTO
BOSS BESPOKERelied on79172085USPTO
BOSS BEYOUTIFULRelied on88614656USPTO
BOSSRelied on90617708USPTO
BOSSRelied on90617734USPTO
BOSSRelied on90617770USPTO
BOSSRelied on97269538USPTO
BOSSRelied on97622849USPTO
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_67b3dd8f-b8fb-4f35-a727-9a3c7743ea54
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_67b3dd8f-b8fb-4f35-a727-9a3c7743ea54",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91285872",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-07-05",
  "parties": [
    {
      "name": "HUGO BOSS Trade Mark Management GmbH & Co., KG",
      "role": "opponent"
    },
    {
      "name": "Melichsia Boss",
      "role": "respondent"
    }
  ]
}