Opposition · USPTO

Opposition 91221187

OtherUSPTO

Opposition 91221187 at USPTO between Swatch AG (Swatch SA) (Swatch Ltd.) and Davis Media, LLC, over the mark SWATCHBUCKLE, filed Mar 23, 2015. Status in the office record: other.

View SWATCHBUCKLEGet this data via the API
Status
Other
Result
Other
Filed
Mar 23, 2015
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Swatch AG (Swatch SA) (Swatch Ltd.)

Respondent

Davis Media, LLC

Timeline

How the case has moved

Dates from the USPTO record and the SWATCHBUCKLE filing.

  1. SWATCHBUCKLE filed

    Application 86268535 filed at the USPTO.

  2. Opposition filed

    Swatch AG (Swatch SA) (Swatch Ltd.) started opposition 91221187 at USPTO against SWATCHBUCKLE.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
SWATCHBUCKLEContested86268535USPTO
SWATCHRelied on73506848USPTO
SWATCHRelied on74079220USPTO
SWATCHRelied on74248413USPTO
SWATCHRelied on74578861USPTO
SWATCHRelied on74579325USPTO
SWATCHRelied on74641474USPTO
SWATCHRelied on74801004USPTO
SWATCHRelied on78124477USPTO
SWATCHRelied on78194325USPTO
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_7c9e6cbb-f50b-4024-bfc6-2c1450261105
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7c9e6cbb-f50b-4024-bfc6-2c1450261105",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91221187",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-03-23",
  "parties": [
    {
      "name": "Swatch AG (Swatch SA) (Swatch Ltd.)",
      "role": "opponent"
    },
    {
      "name": "Davis Media, LLC",
      "role": "respondent"
    }
  ]
}