Brad Hards brings up a twist to the whole kpdf, "to DRM or not to DRM?" question. Would kpdf infringe Adobe's copyright on the pdf spec if they did not include "reasonable efforts" at implementing DRM?
Are we sure it is even legally possible to copyright a specification? That seems absolutely ridiculous to me. How can implementing a given specification result in copyright infringement. After all, you're not supposed to be able to copyright an idea.
More food for thought: If Adobe can copyright their specification to the point that they can choose to license (or not license) according to their rules... what is to keep MS from copyrighting all of their interop interfaces. Seems this is a door big enough to close all efforts at reverse engineering. Which is another right we should possess. Not that MS isn't trying to do the very same thing with patent law...
Anyways, I don't buy this one.

Copyrights on Expressions
Copyrights only apply to expressions, not ideas. See US Title 17 102 for a precise definition of copyright's boundaries.
Thus, the Adobe specification document itself (the actual printout you hold in your grubby little hands) is copyrighted, but the specification of the PDF standard is not copyrighted. The document is merely Adobe's expression of the specification. You cannot take it and distribute it willy-nilly. But you are free to create your own (non-derivative) expression of it, or to implement the ideas within.