Cancellation · USPTO

Cancellation 92049067

OtherUSPTO

Cancellation 92049067 at USPTO between Annco, Inc. and Ann Taylor, Inc. and Freche et Fils Associes, over the mark LDB LOFT DESIGN BY..., filed Mar 24, 2008. Status in the office record: other.

View LDB LOFT DESIGN BY...Get this data via the API
Status
Other
Result
Other
Filed
Mar 24, 2008
Marks involved
5
Parties

Who is involved

The parties as named in the office record.

Petitioner

Annco, Inc. and Ann Taylor, Inc.

Respondent

Freche et Fils Associes

Timeline

How the case has moved

Dates from the USPTO record and the LDB LOFT DESIGN BY... filing.

  1. LDB LOFT DESIGN BY... filed

    Application 76226654 filed at the USPTO.

  2. LDB LOFT DESIGN BY... registered

  3. Cancellation filed

    Annco, Inc. and Ann Taylor, Inc. started cancellation 92049067 at USPTO against LDB LOFT DESIGN BY....
Marks

Marks involved

1 contested mark, 4 marks the challenger relies on.

MarkRoleApplicationOffice
LDB LOFT DESIGN BY...Contested76226654USPTO
ANNTAYLOR. LOFTRelied on74585175USPTO
ANNTAYLOR. LOFTRelied on74654403USPTO
ANNTAYLOR LOFTRelied on76417981USPTO
LOFTRelied on78790622USPTO
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_a1e966f2-783c-445d-be97-97a62e47439f
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_a1e966f2-783c-445d-be97-97a62e47439f",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92049067",
  "status": "other",
  "office_code": "US",
  "filed_date": "2008-03-24",
  "parties": [
    {
      "name": "Annco, Inc. and Ann Taylor, Inc.",
      "role": "petitioner"
    },
    {
      "name": "FRECHE ET FILS ASSOCIES",
      "role": "respondent"
    }
  ]
}