Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • At the Apprenticeship Hour at YAPC::NA last year, Uri Guttman asked for help in developing books.perl.org for this sort of purpose.
    • What about using something PODish for inline book reviews in the online journals? =bookreview Core Perl This book ruined my recent Jamaican vacation. I couldn't but it down ... yada yada =cut You could always parse and export to books.perl.org if/when put into production. Spearhead the semantic web with simplistic inline comments. WOOHOO!
      • (cursed submit button)

        What about using something PODish for inline book reviews in the online journals?

        =bookreview Core Perl This book ruined my recent Jamaican vacation. I couldn't but it down ... yada yada

        =cut

        You could always parse and export to books.perl.org if/when put into production. Spearhead the semantic web with simplistic inline comments. WOOHOO!
        • Well, it would require a fairly complex bit of POD (title, edition, author(s), publisher, categories, rating, etc).

          And people'd screw it up (or forget about it) on a regular basis. With a nice simple set of web forms it'd be easy to add info.
          • I'm not talking about creating the whole application with one tag. Just the text of the review.

            There's something terrific about not having to interrupt your blog train of thought, log in to a separate application, look up all those attributes you mentioned, then type in your book review. Instead, use a tag to mark off your review, and either Slash outputs the necessary RSS-like file for bot consumption, or a web harvester comes along, parses your blog and dumps the text into some web-accessible ratings Db. This is the semantic web.

            If the bookreview tag only had a title (ISBN optional), I'm guessing you could intuit the rest of the items you mentioned, except for ratings. Ratings would be entered on the web site that harvested reviews from blogs, as well as directly inputted in the traditional CGI fashion you describe.

            With the straight CGI system you describe there's no technical risk, just the (large?) risk that people won't bother to enter the data they're already entering in their blogs.