She Named Her Clothing Line After Her Son. The USPTO Refused It Anyway.
Here's a scenario I want you to sit with for a second.
You start a clothing line. You name it after your kid. Not a focus group name, not a name a consultant sold you, a name that means something to you. You file your trademark application. And the USPTO refuses it, not because someone else already owns it, and not because the word describes your clothes, but because the word describes something your clothes could have been and aren't.
That's what happened in a decision the Trademark Trial and Appeal Board issued on September 29, 2026, covered on the TTABlog a few days later.
What happened
The applicant filed JASPE for clothing, including shirts and pants. The examining attorney refused it as deceptively misdescriptive, and the Board agreed.
The problem is that jaspe is a thing. It's a fabric, made by weaving together threads of different colors, which gives it a variegated, streaky look. The record included evidence of 13 third parties selling jaspe clothing. So when a shopper who buys clothes sees JASPE on a shirt, there's a real chance they read it as a description of the fabric.
The applicant's shirts and pants aren't jaspe. She told the Board she chose the word as a tribute to her son, Jasper. She also argued that the word has no stable, commonly understood meaning, and pointed out that jaspe means jasper in Spanish.
None of it moved the outcome. Judge Christen M. English wrote that the word jaspe "merely describes a significant feature ... that Applicant's shirts and pants might plausibly possess but do not in fact possess." The feature in question was jaspe fabric, or a jaspe design.
The rule nobody warns you about
Most founders have heard some version of "you can't trademark a word that just describes your product." That's the descriptiveness rule, and it's the reason FRESH ORANGE JUICE isn't available to you.
Deceptively misdescriptive is the other half of that coin, and it catches people who think they're safely clear of the first rule. The Board asks two questions. First, does the term misdescribe a quality or feature of the goods, meaning something they don't actually have? Second, would consumers be likely to believe the misdescription?
If the answer to both is yes, the mark gets refused. The logic is that the register shouldn't hand someone exclusive rights to a word that quietly misleads people about what they're buying.
Sit with how those two rules fit together. A word that accurately describes a feature you do have is merely descriptive. A word that describes a feature you don't have, but that buyers would believe you do, is deceptively misdescriptive. Both get refused. The space between them is narrower than most people assume, and it's the space almost every founder is naming inside.
Why "that's not what I meant" isn't an argument
This is the part I'd underline for anyone naming a brand right now.
Your reason for choosing a word carries no weight in this analysis. Not your kid's name, not the street you grew up on, not the Latin root you found at 2 a.m. The test isn't what you meant. It's what a buyer in your market is likely to think when they see the word on your product.
That's a hard thing to hear when the name is personal, and it's why I'd rather you hear it from me now than from an Office Action in eight months. The USPTO isn't judging your intentions. It's judging the word against the vocabulary of your industry.
And every industry has a vocabulary like this. Fabrics, cuts, finishes, weaves. Roast levels and processing methods in coffee. Grades, cuts and certifications in jewelry. Strains, extraction methods and carrier oils in skincare and wellness. Techniques and materials in anything handmade. These words sound like clean, invented, ownable brand names to outsiders, and they sound like product specs to the people who buy in that category every week.
What to do before you commit to a name
Three things, in order.
Find out what your word already means in your market. Not what it means in a dictionary. What it means to a buyer scrolling your category. Search it alongside your product type and read what comes back. If vendors are using it as a feature, you've found your problem early, which is the cheapest time to find it.
Then ask yourself an honest question: if the word does describe a real feature in your category, is that a feature your product has? If yes, you may have a descriptiveness problem. If no, and a buyer would assume otherwise, you may have the problem this applicant had. Either answer tells you something useful, and neither one means the name is dead. It means the name needs a plan, which might be adding a distinctive element, going after the design instead of the word, or keeping the personal name for the story and building the registrable brand around it.
Then get a clearance search and a real opinion before you print labels, buy the domain or open the shop. A search looks for conflicting marks, and it also puts eyes on exactly this kind of problem, the kind you can't see from inside your own idea.
One related thing while we're here. I'd advise against slapping TM on a name you haven't cleared. It's free and it's legal, and it's still a bad idea, because it's a public claim on a name nobody has checked yet. Clear the name first.
Where to go from here
A refusal like this one isn't a catastrophe. It's expensive, it's slow, and it is almost always avoidable with a few hours of work at the front end instead of a fight at the back end.
If you're in the middle of naming something, or you've already named it and that paragraph about industry vocabulary made your stomach drop, let's talk. You can see how the search and filing packages work on the services page, and the FAQs page answers most of what comes up before a first call.
Book a free 15-minute discovery call
(No legal advice is given on the discovery call. It's a chance to tell me what you're building and hear how the process works.)
Sources
TTABlog, "TTAB Finds JASPE Deceptively Misdescriptive of Clothing," In re Teresa Michelle Lee, Serial No. 98081572 (Sept. 29, 2026) (not precedential): https://thettablog.blogspot.com/2026/10/ttab-finds-jaspe-deceptively.html
This article is general information, not legal advice. Reading it does not create an attorney-client relationship.