Opposition · USPTO

Opposition 91220920

OtherUSPTO

Opposition 91220920 at USPTO between Apple Inc. and Swatch AG (Swatch SA) (Swatch Ltd.), over the mark I POP, filed Mar 4, 2015. Status in the office record: other.

View I POPGet this data via the API
Status
Other
Result
Other
Filed
Mar 4, 2015
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Respondent

Swatch AG (Swatch SA) (Swatch Ltd.)

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the I POP filing.

  1. I POP filed

    Application 86134220 filed at the USPTO.

  2. Opposition filed

    Apple Inc. started opposition 91220920 at USPTO against I POP.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
I POPContested86134220USPTO
IPODRelied on75982871USPTO
IPODRelied on78018061USPTO
IPODRelied on78089144USPTO
IPODRelied on78521796USPTO
IPODRelied on78532252USPTO
IPODRelied on78653661USPTO
IPODRelied on78653667USPTO
IPODRelied on78653669USPTO
MADE FOR IPODRelied on78689534USPTO
IPODRelied on78981523USPTO
MADE FOR IPOD IPHONERelied on85028983USPTO
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_81694c3f-57a3-4d9c-b237-f48f3808b0f8
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_81694c3f-57a3-4d9c-b237-f48f3808b0f8",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91220920",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-03-04",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Swatch AG (Swatch SA) (Swatch Ltd.)",
      "role": "respondent"
    }
  ]
}