{"id":319,"date":"2017-06-24T13:11:35","date_gmt":"2017-06-24T17:11:35","guid":{"rendered":"https:\/\/ipmanagement.harnessip.com\/?p=319"},"modified":"2017-06-24T13:11:35","modified_gmt":"2017-06-24T17:11:35","slug":"gnireenigne","status":"publish","type":"post","link":"https:\/\/ipmanagement.harnessip.com\/?p=319","title":{"rendered":"Gnireenigne"},"content":{"rendered":"<p>Reverse engineering (now does the title make sense?) is a common and legitimate business practice. \u00a0The recent federal Defend Trade Secrets Act specifically excludes reverse engineering from the definition of misappropriation. \u00a018 USC \u00a71839(6) (&#8220;the term &#8216;improper means&#8217; . . . (B) does not include reverse \u00a0engineering.&#8221;). \u00a0 While the Uniform Trade Secrets Act (some form of which is in force in 48 states and the District of Colombia) does not expressly mention reverse engineering, the Comments to Section 1 adopt the Restatement of Torts position that &#8220;Discovery by &#8216;reverse engineering&#8217;, that is, by starting with the known product and working backward to find the method by which it was developed&#8221; is not an improper means of acquiring a trade secret (provided the acquisition of the product was by a fair and honest means).<\/p>\n<p>Thus if an unpatented product is acquired legally, and there is no enforceable promise not to reverse engineer, the owner of the product is free to analyze and copy the product. \u00a0 Some courts have enforced \u00a0&#8220;no reverse engineering&#8221; clauses[1]. \u00a0However after <a href=\"https:\/\/www.supremecourt.gov\/opinions\/16pdf\/15-1189_ebfj.pdf\">Impression Products, Inc. v. v. Lexmark International, Inc,<\/a>\u00a0 such restrictions may not be enforceable beyond the first purchaser, and in any event, at least some courts have found such &#8220;no reverse engineering&#8221; clauses unenforceable, for example where they interfere with the fair use of computer software.[2]<\/p>\n<p>A business including reverse engineering as part of its product development process should be careful not to cast its own activities in a false light. \u00a0Emails and other internal documents referring to the business&#8217; reverse engineering efforts as &#8220;knocking off&#8221; or similarly disparaging terms, may unfairly portray the company and its products should there be litigation in which the these documents come to light. \u00a0A business should instead accurately characterize its efforts as developing non-infringing competitive products, of which reverse engineering is just one part.<\/p>\n<p>&nbsp;<\/p>\n<p>[1] See <em>K&amp;G Oil &amp; Tool Service Co. v. G&amp;G\u00a0Fishing Tool Service<\/em>, 158 Tex. 94, 314 S.W.2d 782, 785-86 (1958)(enforcing a negotiated agreement not to reverse engineer);\u00a0<em>Pioneer Hi-Bred Int\u2019l, Inc. v. DeKalb Genetics Corp.<\/em>, 51 U.S.P.Q. 1987 (S.D. Iowa\u00a01999)(enforcing \u201cbag tag\u201d restrictions on use of seed for research purposes).<\/p>\n<p>[2] See\u00a0Vault Corp. v. Quaid Software Ltd., 847 F.2d 255 (5th Cir. 1988).<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Reverse engineering (now does the title make sense?) is a common and legitimate business practice. \u00a0The recent federal Defend Trade Secrets Act specifically excludes reverse engineering from the definition of misappropriation. \u00a018 USC \u00a71839(6) (&#8220;the term &#8216;improper means&#8217; . . &hellip; <a href=\"https:\/\/ipmanagement.harnessip.com\/?p=319\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14,11],"tags":[],"class_list":["post-319","post","type-post","status-publish","format-standard","hentry","category-fair-use","category-trade-secrets"],"_links":{"self":[{"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=\/wp\/v2\/posts\/319","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=319"}],"version-history":[{"count":1,"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=\/wp\/v2\/posts\/319\/revisions"}],"predecessor-version":[{"id":320,"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=\/wp\/v2\/posts\/319\/revisions\/320"}],"wp:attachment":[{"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=319"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=319"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ipmanagement.harnessip.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=319"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}