From: Attila Kinali <attila@kinali.ch>
To: Graeme Sheppard <nodes@rillion.net>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Patent or not patent a new idea
Date: Tue, 26 Jun 2007 00:34:05 +0200 [thread overview]
Message-ID: <20070626003405.c3dceba9.attila@kinali.ch> (raw)
In-Reply-To: <46803772.7020408@rillion.net>
On Tue, 26 Jun 2007 09:45:22 +1200
Graeme Sheppard <nodes@rillion.net> wrote:
> I am seeking advice on how to proceed. It could be used as a defensive
> patent in which case I can email an expert who can file it. If that is the
> concept is sound. I am not expecting any royalties from this myself. The
> alternative is to dump it here to the LKML.
Do what anyone with a little bit of brain would do: publish it[1]!
Patenting it and using as defensive patent wont work. Unless
you are able to control Saurons Ring. If you want to know more
just read up on current patent practice. IEEE has quite a few
articles on that issue, i'm sure that ACM and the like should
have also a few.
Attila Kinali
[1] I know of at least one larger company here that stopped
issuing patents but publishes its developments in a local newspaper.
--
Linux ist... wenn man einfache Dinge auch mit einer kryptischen
post-fix Sprache loesen kann
-- Daniel Hottinger
next prev parent reply other threads:[~2007-06-25 22:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 21:45 Patent or not patent a new idea Graeme Sheppard
2007-06-25 22:04 ` alan
2007-06-25 22:26 ` Graeme Sheppard
2007-06-25 22:33 ` alan
2007-06-25 22:34 ` Attila Kinali [this message]
2007-06-25 22:37 ` manningc2
2007-06-26 0:11 ` Bryan Henderson
2007-06-26 1:32 ` Graeme Sheppard
2007-06-26 2:20 ` Neil Brown
2007-06-26 3:20 ` Graeme Sheppard
2007-06-26 3:38 ` Neil Brown
2007-06-26 4:22 ` Graeme Sheppard
2007-06-26 4:33 ` Neil Brown
2007-06-26 16:53 ` Bryan Henderson
2007-06-26 17:38 ` Andreas Dilger
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=20070626003405.c3dceba9.attila@kinali.ch \
--to=attila@kinali.ch \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nodes@rillion.net \
/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 NNTP newsgroup(s).