From: "Martin Schröder" <gschroeder@onlinehome.de>
To: <gdb@sourceware.org>
Subject: Re: generic query regarding GPL and licensing terms associated with gdb
Date: Fri, 13 Aug 2010 07:56:00 -0000 [thread overview]
Message-ID: <53EE6DB2F971468D9FEEC38287F36875@igor> (raw)
In-Reply-To: <350785.50982.qm@web112515.mail.gq1.yahoo.com>
paawan oza wrote:
> If I understood correctly,
>
> -> if the idea is patented by the organization then it may not be
> discussed.
I am not a lawyer, but I think that the contrary is true. As soon as the
idea is patented, you're absolutely free to discuss it in whatever detail
you desire. Of course, you should at least mention that the idea is
patented.
I mean, that's the whole purpose of patenting: To open up the implementation
details to allow the progress of science, while ensuring that you still get
money for it. A patent is simply a trade where the state offers full
protection of the law that the methods described in the patent were invented
by you and all they demand back is that you get rid of the trade secrets
therein and open up the methods for science to exploit. And if they expand
upon it, they can either pay your licensing fees, sell it to you, or wait
till the patent expires.
> -> if idea is not patented but implemented under GPL (which uses and
> modifies original gdb source code), then it can be discussed.
Yup. If you can freely get the source code, you can freely talk about its
details. After all, whatever the source makes the machine do, can also be
emulated inside the human brain. ;)
> -> that means organization has no way to claim the idea legally in
> any terms
That's the point of patenting (claiming that you invented it), and the
reason why patents should only be awarded for actual manufacturing processes
instead of ideas or concepts. And some argue that software is nothing but
concepts and ideas. ;)
Apart from that, there's pretty much only "prior art". If they can prove
that they had the idea first, the same idea becomes difficult to patent. Of
course, you can still use and sell it, but you run the risk of the original
implementor eventually patenting the process.
Just my two cents,
Martin.
next prev parent reply other threads:[~2010-08-13 7:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 4:08 paawan oza
2010-08-13 5:04 ` Robert Dewar
2010-08-13 6:16 ` paawan oza
2010-08-13 7:56 ` Martin Schröder [this message]
2010-08-13 14:26 ` Robert Dewar
2010-08-13 15:35 ` Martin Schröder
2010-08-13 16:18 ` Robert Dewar
2010-08-13 17:50 ` paawan oza
2010-08-13 18:15 ` Martin Schröder
2010-08-24 21:13 ` Steffen Dettmer
2010-08-24 21:33 ` Robert Dewar
2010-08-27 11:38 ` Steffen DETTMER
2010-08-15 16:40 ` Florian Weimer
2010-08-13 14:24 ` Robert Dewar
2010-08-13 15:50 ` Tom Tromey
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53EE6DB2F971468D9FEEC38287F36875@igor \
--to=gschroeder@onlinehome.de \
--cc=gdb@sourceware.org \
--cc=lionhead@onlinehome.de \
/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