From: Jay Sulzberger <jays@panix.com>
To: guile-user <guile-user@gnu.org>
Subject: Re: re-writing algorithms in Guile
Date: Tue, 29 Jun 2021 05:26:38 +0000 () [thread overview]
Message-ID: <Pine.NEB.4.64.2106290504410.21076@panix3.panix.com> (raw)
In-Reply-To: <CACgrOxK1FNRArALUv_ZUryCk7rJwo6doSJA+Wu0aCh8EhRaauw@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed, Size: 2281 bytes --]
On Mon, 28 Jun 2021, Tim Meehan <btmeehan@gmail.com> wrote:
> Say for instance, I have found an algorithm for scalar function
> minimization on a website, written in C. It is posted with a license for
> use. If I write something based on this hypothetical code, is it then
> clearly also licensed in the same manner?
>
> Granted, I know that this is guile-user and not guile-lawyer, but in many
> cases the transformation from procedural to functional is kind of a radical
> re-imagining. I usually try to contact the people and ask them directly,
> but was wondering what was the general consensus in cases where the
> original author did not answer?
Algorithms cannot be copyrighted.
See
https://www.copyright.gov/circs/circ31.pdf
Here is a quote from the article:
United States Copyright Office
Ideas, Methods, or Systems
What Is Not Protected by Copyright
Copyright law does not protect ideas, methods, or systems.
Copyright protection is therefore not available for ideas or
procedures for doing, making, or building things scientific or
technical methods or discoveries; business operations or
procedures; mathematical principles; formulas or algorithms; or
any other concept, process, or method of operation
Section 102 of the Copyright Act (title 17 of the U.S. Code)
clearly expresses this principle: “In no case does copyright
protection for an original work of authorship extend to any idea,
procedure, process, system, method of operation, concept,
principle, or discovery, regardless of the form in which it is
described, explained, illustrated, or embodied in such
work.”
Inventions are subject matter for patents, not copyrights.
For information about patent laws, contact
Commissioner for Patents
U. S. Patent and Trademark Office
P. O . Box 1450
Alexandria, VA 22313-1450
(800) 786-9199
www.uspto.gov
Your program in Guile Scheme which realizes an algorithm is not a
derivative work of the program you read, which program is written in
C. Even in the case that your program realizes the same algorithm as
the C program does. The above official article of the US Copyright
Office clearly states this.
oo--JS.
next prev parent reply other threads:[~2021-06-29 5:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 21:38 re-writing algorithms in Guile Tim Meehan
2021-06-28 21:50 ` Zelphir Kaltstahl
2021-06-29 4:09 ` Nate Rosenbloom
2021-06-29 4:38 ` Vivien Kraus via General Guile related discussions
2021-06-29 13:52 ` Nate Rosenbloom
2021-06-29 14:20 ` tomas
2021-06-29 23:48 ` Tim Meehan
2021-06-30 7:29 ` tomas
2021-06-29 5:26 ` Jay Sulzberger [this message]
2021-06-29 6:08 ` Dr. Arne Babenhauserheide
2021-06-29 6:08 ` Dr. Arne Babenhauserheide
2021-06-29 7:56 ` tomas
2021-06-29 8:56 ` Vivien Kraus via General Guile related discussions
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.NEB.4.64.2106290504410.21076@panix3.panix.com \
--to=jays@panix.com \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).