Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I know this is an old thread but I noticed it and wanted to write: This is a good discussion and thank you for posting it. I don't think, however, that email makes a good example.

I am unfamiliar with case law on the topic but I believe that under US law once something is given to someone without an express contract, or understanding of quid pro quo, it is wholly owned by the recipient.

This happens with paper mail. If it didn't, I could sue an ex to return all love letters as they were my intellectual property. The ownership transfers. I know that email is probably still up in the air legally but I would argue that if I write an email to you, and we don't have an agreement on its status, I do not hold the copyright on it. You now own the content. If I have a personal letter from Ernest Hemingway, I can publish it in my own book of letters without fear from his estate attorneys.

So, while an interesting topic and I'd generally agree that the SSSCA sounds like it's riddled with problems, email may not be the best example.

update: make sure to read tilly's rebuttal. The copyright to the content stays with the author even if the physical letter (or the bits and headers, I s'pose) are owned by the recipient.


In reply to Re: The SSSCA considered harmful by Your Mother
in thread The SSSCA considered harmful by tilly

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others contemplating the Monastery: (6)
As of 2024-03-28 19:30 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found