Opposition · USPTO

Opposition 91178716

OtherUSPTO

Opposition 91178716 at USPTO between The Board of Regents of The University of Texas System and Shenzhen Longhorn Industry Co., Ltd., over the mark LONGHORN, filed Aug 1, 2007. Status in the office record: other.

Status
Other
Result
Other
Filed
Aug 1, 2007
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Opponent

The Board of Regents of The University of Texas System

Respondent

Shenzhen Longhorn Industry Co., Ltd.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the LONGHORN filing.

  1. LONGHORN filed

    Application 79022938 filed at the USPTO.
  2. Opposition filed

    The Board of Regents of The University of Texas System started opposition 91178716 at USPTO against LONGHORN.
Marks

Marks involved

1 contested mark, 6 marks the challenger relies on.

MarkRoleApplicationOffice
LONGHORNContested79022938USPTO
LONGHORNSRelied on73321983USPTO
LONGHORNSRelied on73496763USPTO
LONGHORNSRelied on73637347USPTO
LONGHORNSRelied on73637348USPTO
LONGHORNSRelied on73637351USPTO
LONGHORNSRelied on73637369USPTO
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_2181b5d2-dadf-4c7c-8559-3ffa9eb9bb1d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_2181b5d2-dadf-4c7c-8559-3ffa9eb9bb1d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91178716",
  "status": "other",
  "office_code": "US",
  "filed_date": "2007-08-01",
  "parties": [
    {
      "name": "The Board of Regents of The University of Texas System",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Longhorn Industry Co., Ltd.",
      "role": "respondent"
    }
  ]
}