Opposition · USPTO

Opposition 91231804

OtherUSPTO

Opposition 91231804 at USPTO between Zynga Inc. and Mark Douglas Grissom, over the mark GOATZVILLE, filed Dec 16, 2016. Status in the office record: other.

Status
Other
Result
Other
Filed
Dec 16, 2016
Marks involved
38
Parties

Who is involved

The parties as named in the office record.

Opponent

Zynga Inc.

Company trademarks
Respondent

Mark Douglas Grissom

Timeline

How the case has moved

Dates from the USPTO record and the GOATZVILLE filing.

  1. GOATZVILLE filed

    Application 86889880 filed at the USPTO.
  2. Opposition filed

    Zynga Inc. started opposition 91231804 at USPTO against GOATZVILLE.
Marks

Marks involved

1 contested mark, 37 marks the challenger relies on.

MarkRoleApplicationOffice
GOATZVILLEContested86889880USPTO
FARMVILLE BY ZYNGARelied on77798840USPTO
FARMVILLERelied on77804837USPTO
CITYVILLERelied on77920777USPTO
FARMVILLERelied on77969341USPTO
PETVILLERelied on77979543USPTO
FARMVILLERelied on77980346USPTO
FRONTIERVILLERelied on77983529USPTO
POISONVILLERelied on79074916USPTO
CITYVILLERelied on85187572USPTO
FRONTIERVILLERelied on85187815USPTO
FARMVILLERelied on85187825USPTO

+26 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_f09dff31-f571-4f8c-8b53-36ae854a4bef
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_f09dff31-f571-4f8c-8b53-36ae854a4bef",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91231804",
  "status": "other",
  "office_code": "US",
  "filed_date": "2016-12-16",
  "parties": [
    {
      "name": "Zynga Inc.",
      "role": "opponent"
    },
    {
      "name": "Mark Douglas Grissom",
      "role": "respondent"
    }
  ]
}