comment on

This issue will no doubt be revisited at trial, but at this stage of the proceedings we cannot say that the district court clearly erred.

A tentative conclusion drawn during a pre-trial motion, that a decision made by a previous court may have erred, does not place that tentative conclusion "in fact".

And there you have it.

And there, you have nothing. Even if your reading of this:

The API is part of the structure, sequence and organization and user interface and therefore is potentially copyrightable.

is exactly correct, (which is obviously still open for legal debate),

there is a substantial difference between: "user interface and therefore is potentially copyrightable."

And: APIs are in fact copyrightable.

And you do not need to be a lawyer to see it.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?

In reply to Re^5: Copyright on languages by BrowserUk
in thread Copyright on languages by ikegami

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.


We don't bite newbies here... much
	PerlMonks