Opposition · USPTO

Opposition 91210654

OtherUSPTO

Opposition 91210654 at USPTO between E. & J. Gallo Winery and Agave Oaxaca, LLC, over the mark GALON, filed May 15, 2013. Status in the office record: other.

Status
Other
Result
Other
Filed
May 15, 2013
Marks involved
15
Parties

Who is involved

The parties as named in the office record.

Opponent

E. & J. Gallo Winery

Company trademarks
Respondent

Agave Oaxaca, LLC

Timeline

How the case has moved

Dates from the USPTO record and the GALON filing.

  1. GALON filed

    Application 85704395 filed at the USPTO.
  2. Opposition filed

    E. & J. Gallo Winery started opposition 91210654 at USPTO against GALON.
Marks

Marks involved

1 contested mark, 14 marks the challenger relies on.

MarkRoleApplicationOffice
GALONContested85704395USPTO
GALLORelied on71496376USPTO
GALLORelied on72316889USPTO
GALLORelied on73784199USPTO
ERNEST GALLORelied on74357631USPTO
JULIO R GALLORelied on74357632USPTO
GALLORelied on75330379USPTO
GALLORelied on77073560USPTO
GALLO FAMILY VINEYARDSRelied on77319119USPTO
GALLO FAMILYRelied on78477414USPTO
GALLORelied on78802659USPTO
GALLO FAMILY VINEYARDSRelied on78891422USPTO

+3 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_6b65e9aa-4306-4ece-b16a-1504ea0dcb99
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_6b65e9aa-4306-4ece-b16a-1504ea0dcb99",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91210654",
  "status": "other",
  "office_code": "US",
  "filed_date": "2013-05-15",
  "parties": [
    {
      "name": "E. & J. Gallo Winery",
      "role": "opponent"
    },
    {
      "name": "Agave Oaxaca, LLC",
      "role": "respondent"
    }
  ]
}