Opposition · USPTO

Opposition 91223919

OtherUSPTO

Opposition 91223919 at USPTO between Zynga Inc. and iDeaUSA Products, Inc., over the mark CHARMVILLE, filed Sep 21, 2015. Status in the office record: other.

Status
Other
Result
Other
Filed
Sep 21, 2015
Marks involved
40
Parties

Who is involved

The parties as named in the office record.

Opponent

Zynga Inc.

Company trademarks
Respondent

iDeaUSA Products, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the CHARMVILLE filing.

  1. CHARMVILLE filed

    Application 86321950 filed at the USPTO.
  2. Opposition filed

    Zynga Inc. started opposition 91223919 at USPTO against CHARMVILLE.
Marks

Marks involved

1 contested mark, 39 marks the challenger relies on.

MarkRoleApplicationOffice
CHARMVILLEContested86321950USPTO
YOVILLERelied on77678316USPTO
FARMVILLE BY ZYNGARelied on77798840USPTO
FARMVILLERelied on77804837USPTO
FRONTIERVILLERelied on77894903USPTO
CITYVILLERelied on77920777USPTO
FARMVILLERelied on77969341USPTO
PETVILLERelied on77979543USPTO
FARMVILLERelied on77980346USPTO
FRONTIERVILLERelied on77983529USPTO
CITYVILLERelied on85187572USPTO
FRONTIERVILLERelied on85187815USPTO

+28 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_013418fb-9d42-49e7-bfa8-7731fae2a96a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_013418fb-9d42-49e7-bfa8-7731fae2a96a",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91223919",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-09-21",
  "parties": [
    {
      "name": "Zynga Inc.",
      "role": "opponent"
    },
    {
      "name": "iDeaUSA Products, Inc.",
      "role": "respondent"
    }
  ]
}