Opposition · USPTO

Opposition 91160404

OtherUSPTO

Opposition 91160404 at USPTO between The National Hockey League and National Hockey League Players' Association, over the mark NATIONAL HOCKEY LEAGUE PLAYERS' ASSOCIATION, filed Apr 29, 2004. Status in the office record: other.

View NATIONAL HOCKEY LEAGUE PLAYERS' ASSOCIATIONGet this data via the API
Status
Other
Result
Other
Filed
Apr 29, 2004
Marks involved
2
Parties

Who is involved

The parties as named in the office record.

Opponent

The National Hockey League

Respondent

National Hockey League Players' Association

Timeline

How the case has moved

Dates from the USPTO record and the NATIONAL HOCKEY LEAGUE PLAYERS' ASSOCIATION filing.

  1. NATIONAL HOCKEY LEAGUE PLAYERS' ASSOCIATION filed

    Application 75320139 filed at the USPTO.

  2. Opposition filed

    The National Hockey League started opposition 91160404 at USPTO against NATIONAL HOCKEY LEAGUE PLAYERS' ASSOCIATION.
Marks

Marks involved

1 contested mark, 1 mark the challenger relies on.

MarkRoleApplicationOffice
NATIONAL HOCKEY LEAGUE PLAYERS' ASSOCIATIONContested75320139USPTO
NHLRelied on75106358USPTO
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_d66b3ea0-2ebf-4af5-9f06-1218808487a8
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_d66b3ea0-2ebf-4af5-9f06-1218808487a8",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91160404",
  "status": "other",
  "office_code": "US",
  "filed_date": "2004-04-29",
  "parties": [
    {
      "name": "THE NATIONAL HOCKEY LEAGUE",
      "role": "opponent"
    },
    {
      "name": "NATIONAL HOCKEY LEAGUE PLAYERS' ASSOCIATION",
      "role": "respondent"
    }
  ]
}