Opposition · USPTO

Opposition 91292738

OtherUSPTO

Opposition 91292738 at USPTO between Apple Inc. and Cheng Jinhua, over the mark SEYMAC STOCK, filed Jul 17, 2024. Status in the office record: other.

View SEYMAC STOCKGet this data via the API
Status
Other
Result
Other
Filed
Jul 17, 2024
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Cheng Jinhua

Timeline

How the case has moved

Dates from the USPTO record and the SEYMAC STOCK filing.

  1. SEYMAC STOCK filed

    Application 98189210 filed at the USPTO.

  2. Opposition filed

    Apple Inc. started opposition 91292738 at USPTO against SEYMAC STOCK.
Marks

Marks involved

1 contested mark, 12 marks the challenger relies on.

MarkRoleApplicationOffice
SEYMAC STOCKContested98189210USPTO
MACRelied on74357318USPTO
MAC OSRelied on74547403USPTO
IMACRelied on76070198USPTO
MACINTOSHRelied on77532612USPTO
MACBOOKRelied on78821058USPTO
MAC PRORelied on78885695USPTO
MACBOOK PRORelied on85236152USPTO
MAC MINIRelied on86751917USPTO
MACOSRelied on87158259USPTO
MACOSRelied on87158287USPTO
IMAC PRORelied on87527432USPTO

+1 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_808c1a90-4cc5-4fc5-a7b9-62b9b0d26ea5
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_808c1a90-4cc5-4fc5-a7b9-62b9b0d26ea5",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91292738",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-07-17",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Cheng Jinhua",
      "role": "respondent"
    }
  ]
}