Opposition · USPTO

Opposition 91210453

OtherUSPTO

Opposition 91210453 at USPTO between Retail Royalty Company and Myung Suk Lim, over the mark V EAGLE, filed May 1, 2013. Status in the office record: other.

View V EAGLEGet this data via the API
Status
Other
Result
Other
Filed
May 1, 2013
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Retail Royalty Company

Company trademarks
Respondent

Myung Suk Lim

Timeline

How the case has moved

Dates from the USPTO record and the V EAGLE filing.

  1. V EAGLE filed

    Application 85537599 filed at the USPTO.

  2. Opposition filed

    Retail Royalty Company started opposition 91210453 at USPTO against V EAGLE.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
V EAGLEContested85537599USPTO
AMERICAN EAGLERelied on76617085USPTO
[Design mark]Relied on77616823USPTO
AMERICAN EAGLERelied on78447838USPTO
[Design mark]Relied on78803194USPTO
AMERICAN EAGLERelied on78803216USPTO
AMERICAN EAGLERelied on78980680USPTO
AMERICAN EAGLERelied on78981085USPTO
[Design mark]Relied on78981443USPTO
[Design mark]Relied on85184589USPTO
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_d8163f44-db68-4012-84e7-efda0e07bd62
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_d8163f44-db68-4012-84e7-efda0e07bd62",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91210453",
  "status": "other",
  "office_code": "US",
  "filed_date": "2013-05-01",
  "parties": [
    {
      "name": "Retail Royalty Company",
      "role": "opponent"
    },
    {
      "name": "Myung Suk Lim",
      "role": "respondent"
    }
  ]
}