Cancellation · USPTO

Cancellation 92047712

OtherUSPTO

Cancellation 92047712 at USPTO between medi Bayreuth GmbH & Co., KG. and Extra Wide Sock Company, over the mark EXTRA WIDE MEDI SOCK, filed Jun 22, 2007. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 22, 2007
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Petitioner

medi Bayreuth GmbH & Co., KG.

Respondent

Extra Wide Sock Company

Timeline

How the case has moved

Dates from the USPTO record and the EXTRA WIDE MEDI SOCK filing.

  1. EXTRA WIDE MEDI SOCK filed

    Application 78766132 filed at the USPTO.
  2. EXTRA WIDE MEDI SOCK registered

  3. Cancellation filed

    medi Bayreuth GmbH & Co., KG. started cancellation 92047712 at USPTO against EXTRA WIDE MEDI SOCK.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
EXTRA WIDE MEDI SOCKContested78766132USPTO
GENUMEDIRelied on73694319USPTO
MEDIRelied on74589040USPTO
MEDIRelied on75119921USPTO
MEDIVENRelied on75250576USPTO
MEDI ACTIVERelied on75445921USPTO
MEDICARERelied on75451625USPTO
MEDIVENRelied on76095790USPTO
MEDI-PRENERelied on78184831USPTO
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_fcccb618-283f-4620-a8ce-da37ab6a1f1a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_fcccb618-283f-4620-a8ce-da37ab6a1f1a",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92047712",
  "status": "other",
  "office_code": "US",
  "filed_date": "2007-06-22",
  "parties": [
    {
      "name": "medi Bayreuth GmbH & Co., KG.",
      "role": "petitioner"
    },
    {
      "name": "Extra Wide Sock Company",
      "role": "respondent"
    }
  ]
}