[gojomo]

Yes, I didn't mean to imply that was the exact case here... rather another often-related problem.

This case is bad enough, in that even a relatively well-considered notice, and a default reaction, can crudely impair a lot of other legitimate publishing.

It's not clear to me, though, whether Pearson tried contacting the Edublogs administrators first, or just skipped to the ISP. (I'm also not sure if http://edublogs.org/abuse/ existed before the incident -- but even if not, DMCA practice should require an attempt to contact the narrowest service-providers first, and only move 'upstream' if that doesn't generate either action or a counternotification.)