Certainly one can argue that facts for a book or module can be found elsewhere, but I think that the addition of this information is necessary for completion, as some of my examples indicate. Other examples: the reviewer claims that this book packs everything one needs to know about perl into it; I'd question that claim if the book is less than 100 pages long. alternatively, if a reviewer claims that the book is lacking and yet is 1000 pages long, I'd again question the reviewer.
Of course, as you state, there's no way to control the quality of reviews here on PM; we can only use the voting system to let reviewers know if it was acceptable or not. In my case, I don't plan to downgrade any reviews unless they are completely baseless ("The Camel book is completely worthless because I say so!"), and upgrade those that I find useful, but I'll take a neutral stance on reviews that seem so-so.
Dr. Michael K. Neylon - email@example.com
"You've left the lens cap of your mind on again, Pinky" - The Brain
It's not what you know, but knowing how to find it if you don't know that's important
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||