Re: [DIYbio] Seeking Open Source Licence for new biotech method

Software gets to double dip. There is the right to patent, and the right to copyright. Patents last up to 20 years from filing. Copyright lasts up to 120 years.


Biology at most can patent. Think about it: how many computers or operating systems or even enzymes are still kicking around in the same form and serving a living, ongoing process after 20 years? Sure sure, everyone's got an old VAX or stash of HeLa on ice from the eighties, but not in continuous use, and you're not likely trying to crank up Ubuntu on that old Wang or Vic20 unless you're doing so for the sake of doing so. No one says, jeez, if I only had a Vic 20 to power this code, I could totally solve my problem.

The situation with software and biology are different, unless people want to start copyrighting sequences as code. What we don't want is to continue going down the road that software took, so I'd rather keep the software "license experts" out of this, considering the mess they made of that.

Worse, if renewed every 10 years or so, you can maintain a trademark forever.  With so many potential security holes and bugs, how can any trademark holder like Linus or Bill "protect" users from harm? 

If one piece of living code such as DNA can mutate into any other via natural processes, how can any DNA be patented or copyrighted? For me, arguing about license is dancing on the head of a pin. Are we going to enforce trademark against mutagens?

Or are we seriously trying to protect branded "NEB TAQ" from malicious enzyme suppliers that sneak Ebola in there with it? Software is held to a very crappy standard of self verification relative to biology: no one is going to get peer reviewed if they can't prove that their declared sequence is actually the sequence of the plasmid used. And if you use any chemical off a shelf without verification of identity and purity and reproducibility before pub, you're a crap scientist. Trying to do molecular biology like a computer hacker is not the way to success: it's the way to bugs.

Matt

On Monday, September 16, 2013, William Heath wrote:
Hi Brian Cady,

I emailed Richard Stallman about the extreme need for a copyleft license for synthetic biology etc...  He was not able to assist to my great, great, great surprise.  As a result here is my humble opinion on what you should do:

1.  Anything actually biological/physical use the creative commons license (http://creativecommons.org/choose/)
2.  Anything source code use gpl v3 (http://www.gnu.org/licenses/gpl.html)

Examples of using creative commons are at http://www.thingiverse.com and arduino (http://arduino.cc/en/Main/FAQ).  Examples of gpl v3 are biopython.   

Yet another license that is interesting is the biobricks license which I don't really understand:


-Tim

P.S.

Be aware that you can dual license your offerings.  Coming from the software field I do know that gpl really works.  I have made the argument that dna/proteins are software and that the gpl can be applied to it.  So my humble advice would probably be to release your offering under all three of the above licenses.  That is the best you can do to my knowledge.  I spent both of my masters studying the opensource approach so I know a little bit about what I am talking about.  Let me know if you have questions.


On Mon, Sep 16, 2013 at 3:39 PM, Matthew Harbowy <hbergeronx@gmail.com> wrote:
In the long term, patent and place in trust is a losing strategy. At most, it allows you to prevent anybody from exploiting the idea for commercial gain for a period of about 20 years, during which time you will waste scads of money in a revenge fantasy against evil profit. After that point, it is public domain, no matter what. You might as well reinvest the capital that would be going to lawyers, and undercut competition by producing and selling at a loss, because that strategy keeps evil competition at bay and at least has the opportunity of profit as competition cedes the field. Tech that is off patent or unpatentable due to prior art has so little corporate mindshare that I view it as a massive untapped market. The best strategy in a zero sum game is not to play at all- we need to not play the patent game, and release all tech free for any use, full stop. License free everything.

How much of biotech day to day hardware is free of ip? Do you think that would commonly exist if it were bound up in ip? Gel boxes, illuminators, PCR? PCR went off patent in 2006: how much PCR equipment do you know of that's older than that? Taq polymerase lost its patent in 1999. Pfu lost it this year. Get cracking. The for profit companies tack on innovations to bleed out the life of protection, when we could be wiping the floor with them if we weren't trying so hard to imitate them. Beat them to publication is the only winner.

Matt


On Monday, September 16, 2013, briancady413@yahoo.com wrote:
Thanks, John,

Folks, How does the patent-and-place-in-trust method compare with placing the concept in the public domain, so no-one can patent it, by publishing it publicly without any patenting attempts?

Brian


From: John Griessen <john@industromatic.com>
To: diybio@googlegroups.com
Cc: Brian Cady <briancady413@yahoo.com>
Sent: Monday, September 16, 2013 8:39 PM
Subject: Re: [DIYbio] Seeking Open Source Licence for new biotech method

On 09/16/2013 01:42 PM, Brian Cady wrote:
> I'm patenting a genetic engineering method so that I can make it freely available through an open source licence. Does anyone know
> of good open source licences for intellectual property, so that this concept, and any others that use it, will remain in the
> commons, available to all?

No.  The way to lock it open is to hire a good, yet oddball patent attorney to help you decide
how to make claims, patent them, then assign the rights to a trust-fund-like foundation to manage
in perpetuity for benefit of ______, and you fill in "__for_everyone___", and hand it over to them
forever.  IP is still old fashioned -- like battling dinosaurs.  Leaving something for everyone
to benefit from is so foreign, some attorneys have difficulty with the language and misunderstand it
until spelled out.



--
-- You received this message because you are subscribed to the Google Groups DIYbio group. To post to this group, send email to diybio@googlegroups.com. To unsubscribe from this group, send email to diybio+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/diybio?hl=en
Learn more at www.diybio.org
---
You received this message because you are subscribed to the Google Groups "DIYbio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to diybio+unsubscribe@googlegroups.com.
To post to this group, send email to diybio@googlegroups.com.
Visit this group at http://groups.google.com/group/diybio.
To view this discussion on the web visit https://groups.google.com/d/msgid/diybio/1379380215.35500.YahooMailNeo%40web125503.mail.ne1.yahoo.com.
F
To view this discussion on the web visit https://groups.google.com/d/msgid/diybio/CA%2BRBL9%3DbZ%2B54zFwXBLX11BobE0_B5q9qXxpOhmtmDLF8HZ6HNw%40mail.gmail.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
-- You received this message because you are subscribed to the Google Groups DIYbio group. To post to this group, send email to diybio@googlegroups.com. To unsubscribe from this group, send email to diybio+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/diybio?hl=en
Learn more at www.diybio.org
---
You received this message because you are subscribed to the Google Groups "DIYbio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to diybio+unsubscribe@googlegroups.com.
To post to this group, send email to diybio@googlegroups.com.
Visit this group at http://groups.google.com/group/diybio.
To view this discussion on the web visit https://groups.google.com/d/msgid/diybio/CAAcUL6mEsUY5pNttZ-AuhoPpUZvPg9NU73uWDxgz_3-UV%3D76zg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
-- You received this message because you are subscribed to the Google Groups DIYbio group. To post to this group, send email to diybio@googlegroups.com. To unsubscribe from this group, send email to diybio+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/diybio?hl=en
Learn more at www.diybio.org
---
You received this message because you are subscribed to the Google Groups "DIYbio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to diybio+unsubscribe@googlegroups.com.
To post to this group, send email to diybio@googlegroups.com.
Visit this group at http://groups.google.com/group/diybio.
To view this discussion on the web visit https://groups.google.com/d/msgid/diybio/CA%2BRBL9%3Do1eGg5S7Q8hvg_L4Aw_aCZfSX7O_dRC_cabNWNFTxXA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

  • Digg
  • Del.icio.us
  • StumbleUpon
  • Reddit
  • RSS

0 comments:

Post a Comment