Thanks for taking the time to actually read through my stuff.

The "dry, academic approach" of the paper is easily explained. If you want to engage in dialogue with your academic peers (and supervisors... in my case) via writing you normally try to use the code of your trade, don't you? Especially if you try to express some thoughts and concepts that deviate from the mainstream in particular ways. So... I guess it is all about purpose.

I certainly agree that writing for a more diverse audience would require a different approach... and that there is still a lot of room for improvement in my English writing skills.

I strongly disagree that any knowledge can be "transmitted" efficiently...

A sort of summary of the article is available in form of a presentation that I did at the BlogTalk conference. (http://static.cognitivearchitects.com/gems/Seblogging/ConversationalLearningTool.ppt)

I would also be happy to answer further questions or reply to your comments over at http://seblogging.cognitivearchitects.com/discuss/msgReader$964

Greetings
Sebastian

In reply to Re: Re: Designing conversational learning environments with personal Webpublishing practices and technologies by Anonymous Monk
in thread Designing conversational learning environments with personal Webpublishing practices and technologies by zby

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.