[davidtgoldblatt]

I don't totally follow the conclusion you're trying to draw w.r.t. the definition of a patent troll; clearly there's a lot of people who think that filing and then attempting to enforce a bogus patent applies (though people differ in which patents they think are bogus). Is this some sort of prescriptivist/descriptivist thing?

> The University of Tennessee Knoxville isn't a one man shop.

I mean, sure; but so what? Clearly they were unable or unwilling to fight this battle. Maybe you're right that they should have better protected Plank and society from StreamScale, but I think it makes more sense to put the blame on StreamScale for engaging in this behavior, and our broken patent for encouraging it. Likewise, the paper has multiple authors, but that doesn't really affect the argument at all.

> Ok, if you're going to attack the patent on novelty grounds, you have an easy case to make

I feel like you're deliberately missing the point. Where do you think I'll make this case? I'm certainly not going to spend tens of thousands of dollars fighting the good fight in court. "Technique" in the quote referred to the use of blocking and vector instructions for matrix multiplication. Lots of matrix libraries had such techniques well before the priority date of the patent.

The patent is on using those existing techniques for matrix multiplication, when that matrix multiplication happens to be a part of an error correcting code. I don't think those sorts of patents should exist. (The "matrix multiplication" here is tricky because it's multiplication in a Galois field, but that's not what the patent claims cover).

[CalChris]

> I don't totally follow the conclusion you're trying to draw w.r.t. the definition of a patent troll

Then let me make my view of StreamScale not being a troll perfectly clear. I think they're good faith entrepreneurs taking a risk and developing something new, patenting it ($30-50,000) and selling it. That's not trolling. Shutting down academics from the UofTK is not a realistic source of revenue; it is however reasonably defending their rights which is expected of them now if they're to defend themselves later.

> that's not what the patent claims cover

Careful. You're not a patent attorney (and neither am I). But my attorney told me the engineer to not read claims and certainly not to read them to understand them. (Definitely don't write claims either but that's another matter entirely.) The Supreme Court has said that the claims section is the hardest legal document to write. You both want to avoid prior art (narrow) and preclude inventing around (broad). That's hard to do and hard to understand.

Read the specification for what it's teaching. That's what it's there for. The specification has to teach+support the claims and this one says Galois field all over the place.

Lastly, never say I feel like you're deliberately missing the point. Just don't.

[countingteeth]

> Careful. You're not a patent attorney (and neither am I). But my attorney told me the engineer to not read claims and certainly not to read them to understand them.

Yes, a standard engineer's employment agreement prohibits engineers from performing patent searches.

Isn't this all a good argument that patents are hindering their intended purpose, e.g., PUBLIC DISCLOSURE OF INVENTIONS to advance the state of the art? If claims are written virtually incomprehensibly and are so useless as to not even be allowed as references to actual practitioners, I would argue they are not serving their purpose of public disclosure to advance the state of the art.

[CalChris]

> Yes, a standard engineer's employment agreement prohibits engineers from performing patent searches.

Patent searches are one thing and yeah, big companies like Apple don't want their engineers reading patents at all since it puts them in line for treble damages should they lose an infringement suit. Startups on the other hand, are a different breed and they're not going to fail based on infringement. So you won't see those terms in a startup's employment agreement. Later, maybe.

Also, patent search != reading claims. First, a patent is broken into roughly two halves: specification and claims. Claims are written in a very stylized legal manner which is not meant to teach at all. The specification teaches and supports the claims. Everything that's in the claims must be supported in the specification AND the specification must effectively teach the invention.

So when I say that you shouldn't read claims, I'm saying that you the engineer who's trying to learn from the patent's teaching is wasting your time trying to figure things out from the claims. Figure that out from the specification.

But saying don't read the claims doesn't mean don't do a patent search.

> patents are hindering their intended purpose, e.g., PUBLIC DISCLOSURE OF INVENTIONS to advance the state of the art

This is mistaken. The purpose of patents is to reward the development of new inventions with a temporary monopoly. In exchange for that monopoly, the patent must teach. Public disclosure is not the purpose, it's the other half of the deal. In house lawyers who say never do a patent search are being well, unnecessarily careful.