Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Of course, BrowerUK, you are absolutely correct. I just don't understand why the judge did not use that reasoning.

Imagine if writers were able to copyright phrases -- short combinations of common words. It would very soon lead to the situation where it became impossible to communicate in writing at all.
First of all, you don't "copyright things", other than by creating it. And copyright law doesn't say "well, a work has to be at least N words large". Yet, noone has to worry that if they write down a short phrase they are infringing a copyright, even if someone else has written down the same phrase before them. Yet, they aren't free to copy an entire book.

Now, if APIs were copyrightable (and let me make it clear, I do not have the opinion they should), why should they be treated differently? That is, one shouldn't have to worry about int add( int, int ), but from that, it doesn't imply you can copy a large API like Java.

My point is no more than "I don't think it's obvious that APIs aren't copyrightable". And the mere fact there was a court case, and it wasn't thrown out as frivolous makes me think I wasn't the only one thinking it wasn't obvious.


In reply to Re^3: Copyright on languages by JavaFan
in thread Copyright on languages by ikegami

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 lurking in the Monastery: (8)
As of 2024-03-28 17:07 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found