<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Thanks, Chris, I am doing well; I hope you are, too. <br>
<br>
I want to be clear that I'm not trying to take a position on the
rightness or wrongness of intellectual property, the Google-Oracle
case, or the contentious claims about API access and copyright. I'm
only trying to shed light on how one could claim a copyright on APIs
within our existing system of laws, in response to Rick's question.<br>
<br>
-Bill<br>
<br>
<div class="moz-cite-prefix">On 2016-05-12 22:24, Chris Embree
wrote:<br>
</div>
<blockquote
cite="mid:CAMDYSCk7_BTRTTnVaZntz0EghduGCYxJYiH219EdKwqvwb6mmA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Yeah, but you believe in "intellectual property" as tho it
exists. ;) </div>
<div><br>
</div>
<div>We've debated before and I'll just reiterate; IP is a faux
legal construct that pretends that a thought process is equal
to "tangible property" which leads to a debate about legal
precedent. Just because a few, ignorant and/or paid off,
and/or misguided and/or malicious judges decided something
once, does not constitute proof, fact, or guided decisions
regarding cases like this. I don't care that all the layers
agreed to this as a concept; it's malformed. $0.02</div>
<div><br>
</div>
<div>I only had to explain in as much detail because I know you.
;) </div>
<div><br>
</div>
<div>BTW, hope you're doing well. </div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, May 12, 2016 at 10:08 PM,
William Yang <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:wyang@gcfn.net" target="_blank">wyang@gcfn.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">#include
<std_disclaimer_i_am_not_a_lawyer.h><br>
<br>
I suspect it stems from copyright including the right to
control whether<br>
someone's allowed to create a derivative work.<br>
<br>
Using the API is being construed as derivative, as it relies<br>
specifically on the creative expression of the API. The
layout and<br>
design of the API is also being construed as creative and
expressive, in<br>
that there are many other ways to say the same essential
thing.<br>
<br>
On 2016-05-10 18:12, Rick Hornsby wrote:<br>
> I'm a little bit confused by the $9B Oracle-Google
fight[1]. I don't understand how using an API is a
copyright violation, which makes me think I'm missing some
salient point here. I'm not a fan of Oracle, but Google is
big enough to handle themselves so this isn't an attempt to
construct a defense of any bad behavior on their part.<br>
><br>
> If you build a java library, a ruby gem, or a perl
module and license it for open use as Sun (Oracle) has done
with Java (correct me if I'm wrong), how can you then turn
around and sue me for using the API exposed by your
library/gem/module? If the Java code itself was
copyrighted, say like a DLL from Microsoft might be, and I
blatantly rip that off from you, copy the code, and include
that copied library code in my own commercial product in
clear violation of a *copy*right -- that's different, no?<br>
><br>
> To put it another way, if I make a hugely popular
Windows application (the horror...) that makes me a
bajillion dollars and it uses the APIs exposed by Windows,
how does Microsoft sue me for a copyright violation?<br>
><br>
> [1] <a moz-do-not-send="true"
href="http://arstechnica.com/tech-policy/2016/05/oracles-lawyer-grills-googles-eric-schmidt-on-the-nature-of-apis/"
rel="noreferrer" target="_blank">http://arstechnica.com/tech-policy/2016/05/oracles-lawyer-grills-googles-eric-schmidt-on-the-nature-of-apis/</a><br>
> _______________________________________________<br>
> colug-432 mailing list<br>
> <a moz-do-not-send="true"
href="mailto:colug-432@colug.net">colug-432@colug.net</a><br>
> <a moz-do-not-send="true"
href="http://lists.colug.net/mailman/listinfo/colug-432"
rel="noreferrer" target="_blank">http://lists.colug.net/mailman/listinfo/colug-432</a><br>
><br>
<br>
_______________________________________________<br>
colug-432 mailing list<br>
<a moz-do-not-send="true" href="mailto:colug-432@colug.net">colug-432@colug.net</a><br>
<a moz-do-not-send="true"
href="http://lists.colug.net/mailman/listinfo/colug-432"
rel="noreferrer" target="_blank">http://lists.colug.net/mailman/listinfo/colug-432</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
colug-432 mailing list
<a class="moz-txt-link-abbreviated" href="mailto:colug-432@colug.net">colug-432@colug.net</a>
<a class="moz-txt-link-freetext" href="http://lists.colug.net/mailman/listinfo/colug-432">http://lists.colug.net/mailman/listinfo/colug-432</a>
</pre>
</blockquote>
<br>
</body>
</html>