Opposition · USPTO

Opposition 91237050

OtherUSPTO

Opposition 91237050 at USPTO between Roots Corporation and Common Roots Brewing Company, Inc., over the mark COMMON ROOTS BREWING COMPANY, filed Oct 4, 2017. Status in the office record: other.

View COMMON ROOTS BREWING COMPANYGet this data via the API
Status
Other
Result
Other
Filed
Oct 4, 2017
Marks involved
6
Parties

Who is involved

The parties as named in the office record.

Opponent

Roots Corporation

Company trademarks
Respondent

Common Roots Brewing Company, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the COMMON ROOTS BREWING COMPANY filing.

  1. COMMON ROOTS BREWING COMPANY filed

    Application 87290103 filed at the USPTO.

  2. Opposition filed

    Roots Corporation started opposition 91237050 at USPTO against COMMON ROOTS BREWING COMPANY.
Marks

Marks involved

1 contested mark, 5 marks the challenger relies on.

MarkRoleApplicationOffice
COMMON ROOTS BREWING COMPANYContested87290103USPTO
ROOTSRelied on73779721USPTO
BABY ROOTSRelied on74567683USPTO
ROOTS KIDSRelied on77116560USPTO
ROOTS ATHLETICSRelied on78306720USPTO
ROOTS 73Relied on86982204USPTO
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_42a1d6de-144d-4805-b303-19bbaadb503d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_42a1d6de-144d-4805-b303-19bbaadb503d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91237050",
  "status": "other",
  "office_code": "US",
  "filed_date": "2017-10-04",
  "parties": [
    {
      "name": "Roots Corporation",
      "role": "opponent"
    },
    {
      "name": "Common Roots Brewing Company, Inc.",
      "role": "respondent"
    }
  ]
}