Opposition · USPTO

Opposition 91222722

OtherUSPTO

Opposition 91222722 at USPTO between Nikon Corporation and Vikon Surgical, LLC, over the mark VIKON, filed Jul 8, 2015. Status in the office record: other.

View VIKONGet this data via the API
Status
Other
Result
Other
Filed
Jul 8, 2015
Marks involved
18
Parties

Who is involved

The parties as named in the office record.

Opponent

Nikon Corporation

Company trademarks
Respondent

Vikon Surgical, LLC

Timeline

How the case has moved

Dates from the USPTO record and the VIKON filing.

  1. VIKON filed

    Application 86400329 filed at the USPTO.

  2. Opposition filed

    Nikon Corporation started opposition 91222722 at USPTO against VIKON.
Marks

Marks involved

1 contested mark, 17 marks the challenger relies on.

MarkRoleApplicationOffice
VIKONContested86400329USPTO
NIKONRelied on71619405USPTO
NIKONRelied on73465250USPTO
NIKONRelied on73485367USPTO
NIKONRelied on73621453USPTO
NIKONRelied on74026680USPTO
NIKON SCHOOLRelied on75388866USPTO
NIKONRelied on75399350USPTO
NIKON EYESRelied on75864071USPTO
NIKONRelied on78943003USPTO
NIKONRelied on79020944USPTO
NIKONRelied on85535527USPTO

+6 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_aba768d0-b6eb-47a3-b4cc-289a1af9b428
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_aba768d0-b6eb-47a3-b4cc-289a1af9b428",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91222722",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-07-08",
  "parties": [
    {
      "name": "Nikon Corporation",
      "role": "opponent"
    },
    {
      "name": "Vikon Surgical, LLC",
      "role": "respondent"
    }
  ]
}