Opposition · USPTO

Opposition 91197049

OtherUSPTO

Opposition 91197049 at USPTO between HS TM, LLC and Ridley Inc., over the mark [Design Mark], filed Oct 21, 2010. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 21, 2010
Marks involved
19
Parties

Who is involved

The parties as named in the office record.

Opponent

HS TM, LLC

Respondent

Ridley Inc.

Timeline

How the case has moved

Dates from the USPTO record and the [Design Mark] filing.

  1. [Design Mark] filed

    Application 77883068 filed at the USPTO.
  2. Opposition filed

    HS TM, LLC started opposition 91197049 at USPTO against [Design Mark].
Marks

Marks involved

1 contested mark, 18 marks the challenger relies on.

MarkRoleApplicationOffice
[Design mark]Contested77883068USPTO
S HENRY SCHEINRelied on74613705USPTO
S HENRY SCHEINRelied on74613706USPTO
S HENRY SCHEINRelied on74613707USPTO
S HENRY SCHEINRelied on74613708USPTO
S HENRY SCHEINRelied on74613709USPTO
S HENRY SCHEINRelied on74613710USPTO
S HENRY SCHEINRelied on74613711USPTO
HENRY SCHEINRelied on75121973USPTO
HENRY SCHEINRelied on75891167USPTO
[Design mark]Relied on78307111USPTO
[Design mark]Relied on78307128USPTO

+7 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_61c9c7a5-ffa2-479f-af91-481a5a122a02
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_61c9c7a5-ffa2-479f-af91-481a5a122a02",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91197049",
  "status": "other",
  "office_code": "US",
  "filed_date": "2010-10-21",
  "parties": [
    {
      "name": "HS TM, LLC",
      "role": "opponent"
    },
    {
      "name": "Ridley Inc.",
      "role": "respondent"
    }
  ]
}