Opposition · USPTO

Opposition 91182596

OtherUSPTO

Opposition 91182596 at USPTO between The Wiggles Pty Limited and Sandra Whitted, over the mark WIGGLY DE ZIGGLY, filed Feb 22, 2008. Status in the office record: other.

Status
Other
Result
Other
Filed
Feb 22, 2008
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

The Wiggles Pty Limited

Company trademarks
Respondent

Sandra Whitted

Timeline

How the case has moved

Dates from the USPTO record and the WIGGLY DE ZIGGLY filing.

  1. WIGGLY DE ZIGGLY filed

    Application 77111719 filed at the USPTO.
  2. Opposition filed

    The Wiggles Pty Limited started opposition 91182596 at USPTO against WIGGLY DE ZIGGLY.
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
WIGGLY DE ZIGGLYContested77111719USPTO
THE WIGGLESRelied on75027874USPTO
THE WIGGLESRelied on75976942USPTO
THE WIGGLESRelied on75977386USPTO
WIGGLYRelied on76248690USPTO
WIGGLESRelied on76248691USPTO
WIGGLYRelied on76248693USPTO
WIGGLY SAFARIRelied on76391610USPTO
WIGGLY SAFARIRelied on76391617USPTO
WIGGLY PLAY CENTERRelied on78703407USPTO
WIGGLE AND LEARNRelied on78852382USPTO
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_8289b6bb-8c0c-4dda-923c-597ec89a398f
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_8289b6bb-8c0c-4dda-923c-597ec89a398f",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91182596",
  "status": "other",
  "office_code": "US",
  "filed_date": "2008-02-22",
  "parties": [
    {
      "name": "The Wiggles Pty Limited",
      "role": "opponent"
    },
    {
      "name": "Sandra Whitted",
      "role": "respondent"
    }
  ]
}