Opposition · USPTO

Opposition 91200182

OtherUSPTO

Opposition 91200182 at USPTO between Zynga Inc. and Babbleville, Inc, over the mark BABBLEVILLE, filed May 31, 2011. Status in the office record: other.

Status
Other
Result
Other
Filed
May 31, 2011
Marks involved
14
Parties

Who is involved

The parties as named in the office record.

Opponent

Zynga Inc.

Company trademarks
Respondent

Babbleville, Inc

Timeline

How the case has moved

Dates from the USPTO record and the BABBLEVILLE filing.

  1. BABBLEVILLE filed

    Application 85058401 filed at the USPTO.
  2. Opposition filed

    Zynga Inc. started opposition 91200182 at USPTO against BABBLEVILLE.
Marks

Marks involved

1 contested mark, 13 marks the challenger relies on.

MarkRoleApplicationOffice
BABBLEVILLEContested85058401USPTO
YOVILLERelied on77678316USPTO
FARMVILLE BY ZYNGARelied on77798840USPTO
FARMVILLERelied on77804837USPTO
FISHVILLERelied on77842158USPTO
OFFICEVILLERelied on77876584USPTO
ANIMALVILLERelied on77894854USPTO
CRIMEVILLERelied on77894895USPTO
FRONTIERVILLERelied on77894903USPTO
HOSPITALVILLERelied on77894907USPTO
HOTELVILLERelied on77894921USPTO
TREASUREVILLERelied on77898693USPTO

+2 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_77684280-5ed8-46e6-9f8f-e48b440ce35d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_77684280-5ed8-46e6-9f8f-e48b440ce35d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91200182",
  "status": "other",
  "office_code": "US",
  "filed_date": "2011-05-31",
  "parties": [
    {
      "name": "Zynga Inc.",
      "role": "opponent"
    },
    {
      "name": "Babbleville, Inc",
      "role": "respondent"
    }
  ]
}