Opposition · USPTO

Opposition 91208662

OtherUSPTO

Opposition 91208662 at USPTO between New York Yankees Partnership and Joaquim Da Costa, over the mark NY !! BIG MALUM, filed Dec 27, 2012. Status in the office record: other.

Status
Other
Result
Other
Filed
Dec 27, 2012
Marks involved
18
Parties

Who is involved

The parties as named in the office record.

Opponent

New York Yankees Partnership

Respondent

Joaquim Da Costa

Timeline

How the case has moved

Dates from the USPTO record and the NY !! BIG MALUM filing.

  1. NY !! BIG MALUM filed

    Application 79111220 filed at the USPTO.
  2. Opposition filed

    New York Yankees Partnership started opposition 91208662 at USPTO against NY !! BIG MALUM.
Marks

Marks involved

1 contested mark, 17 marks the challenger relies on.

MarkRoleApplicationOffice
NY !! BIG MALUMContested79111220USPTO
NYRelied on73097286USPTO
NEW YORK YANKEESRelied on73097307USPTO
NYRelied on73222037USPTO
NEW YORKRelied on73746645USPTO
NEW YORK YANKEESRelied on73746675USPTO
NYRelied on73746676USPTO
NYRelied on73764426USPTO
NYRelied on74294048USPTO
NYRelied on76213615USPTO
NYRelied on78637641USPTO
NYRelied on78637642USPTO

+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 /v1/proceedings/{id}
ID=prc_906c0d73-54fe-47a6-ab12-29606d2f39b7
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_906c0d73-54fe-47a6-ab12-29606d2f39b7",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91208662",
  "status": "other",
  "office_code": "US",
  "filed_date": "2012-12-27",
  "parties": [
    {
      "name": "New York Yankees Partnership",
      "role": "opponent"
    },
    {
      "name": "Joaquim Da Costa",
      "role": "respondent"
    }
  ]
}