Thanks, DDPM. Yes, "means" are the things not justified by the ends. [forehead-slap]
Although, let me get this clear for myself: method claims --> claim only method, means claims --> claim device/apparatus/instrument (described in the spec) that performs the method. Correct? Thanks.
Normally, you don't see a pure means claim. I claim: 1. A means for..... In fact, I've never seen one. You typically see some sort of device claim like the one Blakesq presented, where "means for" is/are elements of the device claim.
Briefly, "means for [performing some function]" covers exactly what the
specific specification describes as performing that function -- exactly -- "and equivalents thereof". "means for" used to cover any means for performing the function -- very broad. But Section 112, paragraph 6 put an end to that. Why on Earth should English phrases mean what they mean?
And, the caselaw developing around S 112, p 6 shows that the "equivalents" are extremely narrow -- meaning almost none at all. I believe the tendency of many specifications to list excessively long (attempts at exhaustive) lists of things that can do this or that is a legacy left over from the days where people were trying to fill out their means+function claims. I haven't written a means+function claim in over a decade, probably.
Personally, I think it's worse to attempt to present an exhaustive list of alternative and fall short than to not attempt the exhaustive list in the first place. Don't want to ever admit on the stand that the list represents everything (literally) that I intended to be covered in a particular claim element. I'd much prefer to admit that many things were left off the list because the list was never intended to be exhaustive, only to be illustrative as examples.
Regards.