Opposition · USPTO

Opposition 91226918

OtherUSPTO

Opposition 91226918 at USPTO between Citrix Systems, Inc. and Silicon Studio Corporation, over the mark XENKO, filed Mar 16, 2016. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 16, 2016
Marks involved
16
Parties

Who is involved

The parties as named in the office record.

Opponent

Citrix Systems, Inc.

Company trademarks
Respondent

Silicon Studio Corporation

Timeline

How the case has moved

Dates from the USPTO record and the XENKO filing.

  1. XENKO filed

    Application 86681984 filed at the USPTO.
  2. Opposition filed

    Citrix Systems, Inc. started opposition 91226918 at USPTO against XENKO.
Marks

Marks involved

1 contested mark, 15 marks the challenger relies on.

MarkRoleApplicationOffice
XENKOContested86681984USPTO
XENCENTERRelied on77155395USPTO
XENSERVERRelied on77255154USPTO
XENMOTIONRelied on77255869USPTO
XENDESKTOPRelied on77255873USPTO
CITRIX XENAPPRelied on77382028USPTO
XENAPPRelied on77703290USPTO
XENCLIENTRelied on77895265USPTO
XEN SUMMITRelied on77895410USPTO
XEN MATCHRelied on77909948USPTO
XENRelied on78571964USPTO
XENRelied on78681950USPTO

+4 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 /v1/proceedings/{id}
ID=prc_9055c5e4-4ea2-4a0d-b350-41623f04a56a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_9055c5e4-4ea2-4a0d-b350-41623f04a56a",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91226918",
  "status": "other",
  "office_code": "US",
  "filed_date": "2016-03-16",
  "parties": [
    {
      "name": "Citrix Systems, Inc.",
      "role": "opponent"
    },
    {
      "name": "Silicon Studio Corporation",
      "role": "respondent"
    }
  ]
}