Opposition · USPTO

Opposition 91182635

OtherUSPTO

Opposition 91182635 at USPTO between PomWonderful LLC and Verdure Sciences Inc., over the mark POMELLA, filed Feb 25, 2008. Status in the office record: other.

View POMELLAGet this data via the API
Status
Other
Result
Other
Filed
Feb 25, 2008
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

PomWonderful LLC

Respondent

Verdure Sciences Inc.

Timeline

How the case has moved

Dates from the USPTO record and the POMELLA filing.

  1. POMELLA filed

    Application 77116574 filed at the USPTO.

  2. Opposition filed

    PomWonderful LLC started opposition 91182635 at USPTO against POMELLA.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
POMELLAContested77116574USPTO
POM WONDERFULRelied on76244362USPTO
POMRelied on76245687USPTO
POM WONDERFULRelied on76286258USPTO
POM WONDERFULRelied on76347919USPTO
POMARITARelied on76473207USPTO
POMTINIRelied on76473209USPTO
POM WONDERFULRelied on76534468USPTO
POMTINIRelied on76538618USPTO
POM BEACHRelied on76538619USPTO
POMARITARelied on76538620USPTO
POMRelied on76553991USPTO
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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_1a2a7965-44e1-4467-ba4a-82db5bc8ef53
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1a2a7965-44e1-4467-ba4a-82db5bc8ef53",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91182635",
  "status": "other",
  "office_code": "US",
  "filed_date": "2008-02-25",
  "parties": [
    {
      "name": "PomWonderful LLC",
      "role": "opponent"
    },
    {
      "name": "Verdure Sciences Inc.",
      "role": "respondent"
    }
  ]
}