Opposition · USPTO

Opposition 91209203

OtherUSPTO

Opposition 91209203 at USPTO between Zynga Inc. and Goumbagolf.com LLC, over the mark GOLFVILLE, filed Feb 6, 2013. Status in the office record: other.

Status
Other
Result
Other
Filed
Feb 6, 2013
Marks involved
19
Parties

Who is involved

The parties as named in the office record.

Opponent

Zynga Inc.

Company trademarks
Respondent

Goumbagolf.com LLC

Timeline

How the case has moved

Dates from the USPTO record and the GOLFVILLE filing.

  1. GOLFVILLE filed

    Application 85691102 filed at the USPTO.
  2. Opposition filed

    Zynga Inc. started opposition 91209203 at USPTO against GOLFVILLE.
Marks

Marks involved

1 contested mark, 18 marks the challenger relies on.

MarkRoleApplicationOffice
GOLFVILLEContested85691102USPTO
YOVILLERelied on77678316USPTO
FARMVILLE BY ZYNGARelied on77798840USPTO
FARMVILLERelied on77804837USPTO
FISHVILLERelied on77842158USPTO
CITYVILLERelied on77920777USPTO
PETVILLERelied on77979543USPTO
POISONVILLERelied on79074916USPTO
CITYVILLERelied on85187572USPTO
FARMVILLERelied on85187825USPTO
REWARDVILLERelied on85283115USPTO
FARMVILLE ENGLISH COUNTRYSIDERelied on85290860USPTO

+7 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_33195043-e0c2-4378-942e-f7e6341a90d7
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_33195043-e0c2-4378-942e-f7e6341a90d7",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91209203",
  "status": "other",
  "office_code": "US",
  "filed_date": "2013-02-06",
  "parties": [
    {
      "name": "Zynga Inc.",
      "role": "opponent"
    },
    {
      "name": "Goumbagolf.com LLC",
      "role": "respondent"
    }
  ]
}