Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
I agree with tye's analysis. It is fact (as he and Old Gray Bear both noted) that posting to a forum such as this DOES restrict one's ability to later cause that contribution -- no matter how wise or trollish -- to disappear

But, more important, I believe such posting SHOULD be tantamount to irrevocable waiver of any right to revoke what tye calls "license to distribute."

Hence, tye's "'legal notice'" deserves support and action... even if some could argue that it smacks of a "shrink-wrap license" scheme.

Tangent: I quibble -- nay, even quarrel-- with this one section of Old Gray Bear's presention:

On the one hand, I have to support X in his wish to remove his writings from general circulation. He wrote them. There was no 'license' attached to it releasing the words and ideas to the Public Domain. He is able to edit the node content at will. His retraction is merely a severe form of editing, but it is His Right.

  • Why (this is a serious question; neither troll nor flame) do you feel obliged "to support X..." re removal?
    Legal reasons; human rights? some other consideration?
  • Retraction may be "merely a severe form of editing" but in light of the fact that doing so reduces or destroys the value of others' contributions, I can't agree that it is "His Right."

I suspect we'd be well served with the view that the right to edit one's comments in a thread to which others have contributed should be restricted to strikethrough and insert. The would-be retracter can easily enough use available mechanisms (css such as:
    &nbgsp; <style="font-family: serif; color: #bo400f; background-color: transparent;">
might work) to highlight the retraction/disavowal of a comment which s/he later decided is untenable (in the light of further reflection or new evidence -- perhaps even an illuminating comment farther down the same thread).

Posted, knowing that some flaw in my current thinking may someday have me wishing I could not merely retract, but could actually delete this rambling. <G>

In reply to Re^2: Musing on Monastery Content by ww
in thread Musing on Monastery Content by Old_Gray_Bear

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, 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
  • 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others scrutinizing the Monastery: (1)
    As of 2018-02-22 07:26 GMT
    Find Nodes?
      Voting Booth?
      When it is dark outside I am happiest to see ...

      Results (288 votes). Check out past polls.