<?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/" version="2.0">
   <channel>
      <title>Virginia Business Law Update</title>
      <link>http://www.virginiabusinesslawupdate.com/</link>
      <description>Virginia Business Lawyers &amp; Attorneys : PCT Law Group : Litigation Defenses, Contract Disputes, Business Formation : Northern Virginia, Arlington, Fairfax, Alexandria</description>
      <language>en</language>
      <copyright>Copyright 2012</copyright>
      <lastBuildDate>Wed, 21 Mar 2012 11:57:18 -0500</lastBuildDate>
      <pubDate>Wed, 21 Mar 2012 11:57:18 -0500</pubDate>
      <generator>http://www.movabletype.org</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

            <feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="virginiabusinesslawupdate" /><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.virginiabusinesslawupdate.com/index.xml" /><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Fwww.virginiabusinesslawupdate.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 xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Fwww.virginiabusinesslawupdate.com%2Findex.xml" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://feeds.my.aol.com/add.jsp?url=http%3A%2F%2Fwww.virginiabusinesslawupdate.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 xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.bloglines.com/sub/http://www.virginiabusinesslawupdate.com/index.xml" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Fwww.virginiabusinesslawupdate.com%2Findex.xml" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://fusion.google.com/add?feedurl=http%3A%2F%2Fwww.virginiabusinesslawupdate.com%2Findex.xml" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.pageflakes.com/subscribe.aspx?url=http%3A%2F%2Fwww.virginiabusinesslawupdate.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 xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.plusmo.com/add?url=http%3A%2F%2Fwww.virginiabusinesslawupdate.com%2Findex.xml" src="http://plusmo.com/res/graphics/fbplusmo.gif">Subscribe with Plusmo</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.thefreedictionary.com/_/hp/AddRSS.aspx?http%3A%2F%2Fwww.virginiabusinesslawupdate.com%2Findex.xml" src="http://img.tfd.com/hp/addToTheFreeDictionary.gif">Subscribe with The Free Dictionary</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.bitty.com/manual/?contenttype=rssfeed&amp;contentvalue=http%3A%2F%2Fwww.virginiabusinesslawupdate.com%2Findex.xml" src="http://www.bitty.com/img/bittychicklet_91x17.gif">Subscribe with Bitty Browser</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.newsalloy.com/?rss=http%3A%2F%2Fwww.virginiabusinesslawupdate.com%2Findex.xml" src="http://www.newsalloy.com/subrss3.gif">Subscribe with NewsAlloy</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.live.com/?add=http%3A%2F%2Fwww.virginiabusinesslawupdate.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 xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://mix.excite.eu/add?feedurl=http%3A%2F%2Fwww.virginiabusinesslawupdate.com%2Findex.xml" src="http://image.excite.co.uk/mix/addtomix.gif">Subscribe with Excite MIX</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://download.attensa.com/app/get_attensa.html?feedurl=http%3A%2F%2Fwww.virginiabusinesslawupdate.com%2Findex.xml" src="http://www.attensa.com/blogs/attensa/WindowsLiveWriter/BadgeredintoBadges_10C02/attensa_feed_button5.gif">Subscribe with Attensa for Outlook</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.webwag.com/wwgthis.php?url=http%3A%2F%2Fwww.virginiabusinesslawupdate.com%2Findex.xml" src="http://www.webwag.com/images/wwgthis.gif">Subscribe with Webwag</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.podcastready.com/oneclick_bookmark.php?url=http%3A%2F%2Fwww.virginiabusinesslawupdate.com%2Findex.xml" src="http://www.podcastready.com/images/podcastready_button.gif">Subscribe with Podcast Ready</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.flurry.com/pushRssFeed.do?r=fb&amp;url=http%3A%2F%2Fwww.virginiabusinesslawupdate.com%2Findex.xml" src="http://www.flurry.com/images/flurry_rss_logo2.gif">Subscribe with Flurry</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.wikio.com/subscribe?url=http%3A%2F%2Fwww.virginiabusinesslawupdate.com%2Findex.xml" src="http://www.wikio.com/shared/img/add2wikio.gif">Subscribe with Wikio</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.dailyrotation.com/index.php?feed=http%3A%2F%2Fwww.virginiabusinesslawupdate.com%2Findex.xml" src="http://www.dailyrotation.com/rss-dr2.gif">Subscribe with Daily Rotation</feedburner:feedFlare><item>
         <title>Inequitable Treatment in Severance Packages May Lead to a Discrimination Claim</title>
         <description><![CDATA[<p>Although not contractually required to do so, many employers offer their management-level employees a <a href="http://en.wikipedia.org/wiki/Severance_package">severance package</a> in the event of a reduction-in-force or some other non-disciplinary event which requires an employer to terminate a relationship with a managerial employee.  The terms and compensation contained in severance packages usually depend upon salary, years of service, and work performance and/or value of the employee to the employer.  However, if an employee can show that the terms of a severance package offered to them are less favorable than those offered to other, similarly situated employees, the employee may be able to state a claim for discrimination.</p>
<p>In the case of <a href="http://pacer.ca4.uscourts.gov/opinion.pdf/111218.P.pdf"><em>Gerner v. City of Chesterfield, Virginia</em></a> (2012), the United States Court of Appeals for the Fourth Circuit reversed a lower court ruling from the <a href="http://www.vaed.uscourts.gov/">Eastern District of Virginia</a> and found that although a severance agreement is offered upon employment termination and is not a contractual right, it is nevertheless an employment benefit upon which a discrimination claim may lie.  Finding that the district court judge (Hudson, J.) erred in his analysis of the legal standard, the appellate court held <a href="http://www.eeoc.gov/laws/statutes/titlevii.cfm">Title VII </a>protects current and former employees from discrimination, as well as those who have not been hired and have been discriminated against in the hiring process.  Further, the Court found that Ms. Gerner's allegations that she was offered a less favorable severance package than her male counter-parts under the City&rsquo;s reduction-in-force plan, were sufficient to allege an adverse employment action for a <a href="http://www.eeoc.gov/laws/types/sex.cfm">gender discrimination claim</a>. In making its ruling, the Court relied upon U.S. Supreme Court precedent and decisions from other Circuit Courts.</p>
<p>This decision by the Fourth Circuit, which is the highest federal appellate court for Virginia, Maryland, West Virginia, and the Carolinas, is a reminder to employers that they must be vigilant in making sure that employment benefits (even severance packages which are often viewed as &ldquo;voluntary&rdquo; or &ldquo;discretionary&rdquo;) are provided on an equitable basis. Alternatively, employers must make sure that they have a strong, non-discriminatory, reason for any difference in the provision of such benefits among similarly situated employees.</p>
<p>&copy; Copyright, PCT Law Group 2012, all rights reserved.<br />
&nbsp;</p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2012/03/articles/employment-law-1/inequitable-treatment-in-severance-packages-may-lead-to-a-discrimination-claim/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2012/03/articles/employment-law-1/inequitable-treatment-in-severance-packages-may-lead-to-a-discrimination-claim/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/tags">Eastern District of Virginia</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Employment Law</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Fourth Circuit Court of Appeals</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Title VII</category><category domain="http://www.virginiabusinesslawupdate.com/tags">employment litigation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">gender discrimination claim</category><category domain="http://www.virginiabusinesslawupdate.com/tags">severance package</category>
         <pubDate>Wed, 21 Mar 2012 11:17:55 -0500</pubDate>
         <dc:creator>Malik Cutlar</dc:creator>
      
      </item>
            <item>
         <title>Use of Misappropriated Trade Secret Not Required For a Trade Secrets Act Violation</title>
         <description><![CDATA[<p>If an employee misappropriates their current or former employer&rsquo;s proprietary information, and discloses such information to its new employer and/or any other unauthorized person(s), that is enough to establish a violation under the <a href="http://leg1.state.va.us/cgi-bin/legp504.exe?000+cod+TOC59010000026000000000000">Virginia Uniform Trade Secrets Act</a> (&ldquo;VUTSA&rdquo;) so says the <a href="http://leg1.state.va.us/cgi-bin/legp504.exe?000+cod+TOC59010000026000000000000">Virginia Supreme Court</a>.  There is no requirement under the Act that the employee or new employer actually use the misappropriated information to compete with the former employer.</p>
<p>In the case of <a href="http://scholar.google.com/scholar_case?case=10159702841232095732&amp;q=geographic+services,+inc.+v.+colello&amp;hl=en&amp;as_sdt=2,47&amp;as_vis=1"><em>Geographic Services, Inc. v. Collelo, et al.</em></a> (2012), the Virginia Supreme Court held that once an employer establishes the existence of a trade secret, all that they are then required to show is that the trade secret was misappropriated as that term is defined under the Trade Secrets Act.  The entity from which the trade secret was misappropriated does not have to show that defendants used the trade secret in order to establish a claim under the VUTSA and recover damages.  Disclosure of the trade secret is sufficient where it can be shown that the new employer and/or person to whom the trade secret was disclosed knew, or had reason to know, that the trade secret was acquired by improper means.  In such cases, where the plaintiff cannot readily prove measurable damages, then the VUTSA provides that the court can impose a reasonable royalty upon the wrongdoers for the unauthorized disclosure of the trade secret.</p>
<p>This decision by Virginia&rsquo;s highest court provides a cautionary note for Virginia employers:  if you know, or should have known, that an employee has obtained proprietary information from its prior employer without its knowledge, you could be on the hook for damages if the employee discloses the information to your company &ndash; even if your company never uses the information.  The disclosure, in and of itself, will be enough to expose companies to monetary damages.  Conversely, companies in which an employee has taken proprietary information can seek legal redress and possibly obtain damages even if the employee and its new company did not use the information.</p>
<p>&nbsp;</p>
<p>&copy; Copyright, PCT Law Group 2012, all rights reserved.<br />
&nbsp;</p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2012/01/articles/litigation/use-of-misappropriated-trade-secret-not-required-for-a-trade-secrets-act-violation/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2012/01/articles/litigation/use-of-misappropriated-trade-secret-not-required-for-a-trade-secrets-act-violation/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/tags">
damages</category><category domain="http://www.virginiabusinesslawupdate.com/tags">
royalties</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Act</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Business Contracts</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Court</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Employment Law</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Intellectual Property</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Litigation</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Non-Compete</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Secrets</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Supreme</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Trade Secrets</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Virginia</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Virginia Business News</category><category domain="http://www.virginiabusinesslawupdate.com/articles/litigation">Virginia Litigation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">information</category><category domain="http://www.virginiabusinesslawupdate.com/tags">misappropriation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">proprietary</category><category domain="http://www.virginiabusinesslawupdate.com/tags">secret</category><category domain="http://www.virginiabusinesslawupdate.com/tags">trade</category>
         <pubDate>Tue, 31 Jan 2012 14:54:09 -0500</pubDate>
         <dc:creator>Malik Cutlar</dc:creator>
      
      </item>
            <item>
         <title>Tips for Saving Money on Initial Patent and Trademark Services</title>
         <description><![CDATA[<p><span style="font-size: small;">It is clear that the economic downturn has lessened the appetite for companies to spend money on anything not perceived as a &ldquo;necessary business expense.&rdquo;  The importance of intellectual property (IP) rights in a 21st century, knowledge economy, however, dictates that individual inventors and small- and medium-sized businesses (&ldquo;SMBs&rdquo;) find capital to file for patents and trademarks relating to their truly innovative products and services.</span></p>
<p><span style="font-size: small;">The above then begs the question:  How can SMBs save money in hiring and engaging IP legal counsel?  Well, the answer to this question contains many variables related to the specific IP attorney being hired.  Such variables include the region where the IP attorney works, the size of law firm in which they practice, their level of experience, the complexity of the IP involved, etc.</span></p>
<p><span style="font-size: small;">The above variables aside, there is one constant in the price equation that I consistently advise SMBs to pay attention to &ndash; the preparation of their <em>disclosure materials </em>BEFORE meeting with any newly-engaged IP counsel.  That is, SMBs (and individual entrepreneurs) can directly and significantly control their IP legal cost through careful preparation of their disclosure materials.  I have seen $5000 legal bills turned into $15000 legal bills through the needless &ldquo;back and forth&rdquo; between an IP attorney who is &ldquo;on the clock&rdquo; and a client who has prematurely engaged such IP attorney.</span> <span style="font-size: small;">So, what do I mean by disclosure materials and how should an SMB prepare them?  Well, I answer in two parts:</span></p>
<p><span style="font-size: small;">With respect to an invention needing a patent application, disclosure materials means an SMB <strong>gathering and organizing</strong> all relevant papers, sketches, drawings, notes, software code, formulations, etc. that provide the IP attorney with the following information:</span></p>
<ul>
    <li><span style="font-size: small;">Title of the invention</span></li>
    <li><span style="font-size: small;">The full legal names, addresses and citizenship of all inventors</span></li>
    <li><span style="font-size: small;">The full name, address and state of incorporation of the company who will own the patent (if any)</span></li>
    <li><span style="font-size: small;">A description of the problem solved by the invention</span></li>
    <li><span style="font-size: small;">A description of how long the problem has been around and how have others tried to solve the problem</span></li>
    <li><span style="font-size: small;">A description of how the invention solves the problem differently than past solutions or attempted solutions</span></li>
    <li><span style="font-size: small;">System diagrams showing all hardware/software components of the invention</span></li>
    <li><span style="font-size: small;">Flowcharts illustrating the steps of the invention</span></li>
    <li><span style="font-size: small;">A list any known websites, publications, patents, products, services, etc. that are relevant to the subject matter of the invention</span></li>
    <li><span style="font-size: small;">A description of how the invention relates to the launch of a new product or service</span></li>
    <li><span style="font-size: small;">Dates the invention was (or will be): first conceived; implemented as a pilot or otherwise used in the public domain; reduced to actual practice; the subject of a publication or public disclosure; sold or offered for sale; and/or internally exploited</span></li>
</ul>
<p><span style="font-size: small;">With respect to a mark or logo needing a trademark application, disclosure materials means an SMB <strong>gathering and organizing</strong> the following information to provide to the IP attorney:</span></p>
<ul>
    <li><span style="font-size: small;">A description of the mark</span></li>
    <li><span style="font-size: small;">The full name, address and state of incorporation of the entity who will own the trademark</span></li>
    <li><span style="font-size: small;">A description of all the types of products and/or services with which the mark is actually used or will be used</span></li>
    <li><span style="font-size: small;">Date of any first sale of goods bearing the mark in interstate commerce</span></li>
    <li><span style="font-size: small;">Copies of any specimens showing the mark as it is currently (or will be) used on or in connection with the goods or services</span></li>
    <li><span style="font-size: small;">A description of how the mark is actually used or intended to be used</span></li>
</ul>
<p><span style="font-size: small;">A prepared and organized client is one who receives efficient IP legal services and a reasonable legal bill from their IP attorney, and is consequently glad to pay that reasonable bill!&nbsp;</span></p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2012/01/articles/intellectual-property/tips-for-saving-money-on-initial-patent-and-trademark-services/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2012/01/articles/intellectual-property/tips-for-saving-money-on-initial-patent-and-trademark-services/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/tags">IP</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Intellectual Property</category><category domain="http://www.virginiabusinesslawupdate.com/tags">patent attorney</category><category domain="http://www.virginiabusinesslawupdate.com/tags">patent services</category><category domain="http://www.virginiabusinesslawupdate.com/tags">trademark services</category>
         <pubDate>Wed, 18 Jan 2012 12:30:52 -0500</pubDate>
         <dc:creator>Ray Millien</dc:creator>
      
      </item>
            <item>
         <title>Non-Compete Ruled Unenforceable by Virginia Circuit Court</title>
         <description><![CDATA[<p><span style="font-size: small;">For several years now, many practitioners that advise and/or draft non-competes for their business clients have stopped including language in non-compete provisions which prohibit a former employee from being an &ldquo;owner&rdquo; or &ldquo;shareholder&rdquo; in a competing business.  Virginia Courts have routinely held that including language which prohibits a former employee from essentially owning stock in a competing business was overbroad and not necessary to protect an employer&rsquo;s legitimate business interest.  Therefore, such non-competes have regularly been invalidated.</span></p>
<p><span style="font-size: small;">Consistent with prior court opinions, a </span><a href="http://www.vbgov.com/vgn.aspx?channel=true&amp;vgnextoid=ba10476215ced010VgnVCM1000006310640aRCRD"><span style="font-size: small;">Virginia Beach Circuit Court</span></a><span style="font-size: small;"> recently invalidated a non-compete provision which prohibited a former employee from, inter alia, being an owner or shareholder in a competing business.  The case, </span><a href="http://www.virginiabusinesslawupdate.com/uploads/file/Patient.pdf"><span style="font-size: small;">Patient First Richmond Medical Group, LLC v. Ameanthea Rica Blanco</span></a><span style="font-size: small;"> (Virginia Beach Circuit Court, Feb. 15, 2011), involved Defendant Blanco, a family nurse practitioner who was employed by Plaintiff Patient First.  According to the allegations in the case, Blanco, while still working at Patient First, began formation of a competing healthcare practice which was to provide primary and urgent care treatment at reasonable or fixed fees during extended weekday and weekend hours without the need for an appointment.  </span></p>
<p><span style="font-size: small;">Blanco also solicited two doctors from Patient First to come work with her at the new medical practice.  After she resigned her position with Patient First, Blanco opened up the competing business within seven miles of her former place of employment.  Patient First brought suit alleging that Blanco violated her employment agreement which contained non-competition and non-solicitation provisions.</span></p>
<p>The covenant not to compete prohibited Blanco from performing medical services of the type performed for Patient First (though the term &ldquo;medical services&rdquo; was not defined) for two years after her employment and within a seven-mile radius as an &ldquo;agent, officer, director, member, partner, shareholder, independent contractor, owner, or employee&rdquo; of the competing business.  The Court found that the non-compete provision was overbroad because its provisions went beyond occupations and businesses that were in competition with Patient First.  The Court reasoned that by barring Blanco from being a shareholder in a competing business, she would be barred from merely owning stock in a publically traded company, even if she were not providing medical services for the company and thus not competing with Patient First.</p>
<p>The Court also held that a number of the terms in the provision were not defined and left too much uncertainty as to which activities of the former employee would, or would not, be in violation of the covenant.  Therefore, an employee would essentially have to guess at which conduct was prohibited.  The Court held that in such cases, the non-compete was unenforceable as offending sound public policy, and sustained Blanco&rsquo;s demurrer without leave for Patient First to amend.<br />
<!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:RelyOnVML />
<o:AllowPNG />
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:TrackMoves />
<w:TrackFormatting />
<w:PunctuationKerning />
<w:ValidateAgainstSchemas />
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF />
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables />
<w:SnapToGridInCell />
<w:WrapTextWithPunct />
<w:UseAsianBreakRules />
<w:DontGrowAutofit />
<w:SplitPgBreakAndParaMark />
<w:DontVertAlignCellWithSp />
<w:DontBreakConstrainedForcedTables />
<w:DontVertAlignInTxbx />
<w:Word11KerningPairs />
<w:CachedColBalance />
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val="Cambria Math" />
<m:brkBin m:val="before" />
<m:brkBinSub m:val="&#45;-" />
<m:smallFrac m:val="off" />
<m:dispDef />
<m:lMargin m:val="0" />
<m:rMargin m:val="0" />
<m:defJc m:val="centerGroup" />
<m:wrapIndent m:val="1440" />
<m:intLim m:val="subSup" />
<m:naryLim m:val="undOvr" />
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
DefSemiHidden="true" DefQFormat="false" DefPriority="99"
LatentStyleCount="267">
<w:LsdException Locked="false" Priority="0" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Normal" />
<w:LsdException Locked="false" Priority="9" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="heading 1" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" />
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" />
<w:LsdException Locked="false" Priority="39" Name="toc 1" />
<w:LsdException Locked="false" Priority="39" Name="toc 2" />
<w:LsdException Locked="false" Priority="39" Name="toc 3" />
<w:LsdException Locked="false" Priority="39" Name="toc 4" />
<w:LsdException Locked="false" Priority="39" Name="toc 5" />
<w:LsdException Locked="false" Priority="39" Name="toc 6" />
<w:LsdException Locked="false" Priority="39" Name="toc 7" />
<w:LsdException Locked="false" Priority="39" Name="toc 8" />
<w:LsdException Locked="false" Priority="39" Name="toc 9" />
<w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" />
<w:LsdException Locked="false" Priority="10" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Title" />
<w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" />
<w:LsdException Locked="false" Priority="11" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtitle" />
<w:LsdException Locked="false" Priority="22" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Strong" />
<w:LsdException Locked="false" Priority="20" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Emphasis" />
<w:LsdException Locked="false" Priority="59" SemiHidden="false"
UnhideWhenUsed="false" Name="Table Grid" />
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" />
<w:LsdException Locked="false" Priority="1" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="No Spacing" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 1" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 1" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 1" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 1" />
<w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" />
<w:LsdException Locked="false" Priority="34" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" />
<w:LsdException Locked="false" Priority="29" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Quote" />
<w:LsdException Locked="false" Priority="30" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 1" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 1" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 1" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 1" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 1" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 2" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 2" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 2" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 2" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 2" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 2" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 2" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 2" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 2" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 3" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 3" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 3" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 3" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 3" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 3" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 3" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 3" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 3" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 4" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 4" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 4" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 4" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 4" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 4" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 4" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 4" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 4" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 5" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 5" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 5" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 5" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 5" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 5" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 5" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 5" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 5" />
<w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 6" />
<w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 6" />
<w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 6" />
<w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" />
<w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" />
<w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 6" />
<w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 6" />
<w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" />
<w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" />
<w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" />
<w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 6" />
<w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 6" />
<w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 6" />
<w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 6" />
<w:LsdException Locked="false" Priority="19" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" />
<w:LsdException Locked="false" Priority="21" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" />
<w:LsdException Locked="false" Priority="31" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" />
<w:LsdException Locked="false" Priority="32" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" />
<w:LsdException Locked="false" Priority="33" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Book Title" />
<w:LsdException Locked="false" Priority="37" Name="Bibliography" />
<w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" />
</w:LatentStyles>
</xml><![endif]--><!--[if gte mso 10]>
<style>
/* 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-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0in;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}
</style>
<![endif]--><u><span style="line-height: 115%; font-family: &quot;Times New Roman&quot;,&quot;serif&quot;;"><br />
</span></u></p>
<p><span style="font-size: small;">&nbsp;</span></p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2012/01/articles/noncompete-agreements/noncompete-ruled-unenforceable-by-virginia-circuit-court/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2012/01/articles/noncompete-agreements/noncompete-ruled-unenforceable-by-virginia-circuit-court/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/articles">Non-Compete</category>
         <pubDate>Wed, 11 Jan 2012 10:46:08 -0500</pubDate>
         <dc:creator>Malik Cutlar</dc:creator>
      
      </item>
            <item>
         <title>Virginia State Court:  Contractor Can Pursue Assets of Subcontractor's Owner</title>
         <description><![CDATA[<p>After a less-than-satisfactory boiler improvement job done by a subcontractor, a Henrico County Circuit Court judge allowed the prime contractor to <a href="http://en.wikipedia.org/wiki/Piercing_the_corporate_veil">pierce the corporate veil</a> and reach the personal assets of the subcontractor&rsquo;s owner for damages related to this job.  In this case, the Court found evidence that the sole shareholder of the subcontractor failed to uphold corporate formalities such as annual meetings and the maintenance of separate financial books for the company.  Moreover, the subcontractor arranged for the corporation to enter into a contract while grossly undercapitalized. The finding resulted in a judgment worth $137,454 against the shareholder personally.</p>
<p>In Virginia, courts regard veil-piercing as an extraordinary remedy.  Generally, each corporation is a separate legal entity with its own debts/liabilities and assets.  However, under Virginia law, a court may pierce the corporate veil to find that an individual owner is the alter ego of a corporation where it finds (1) a unity of interest and ownership between the individual and the corporation, and (2) that the individual used the corporation to evade a personal obligation, to perpetrate fraud or a crime, to commit an injustice, or to gain an unfair advantage.</p>
<p><strong>When deciding whether to pierce the corporate veil, courts consider a variety of factors, including the intermingling of assets of the corporation and of the shareholder; the absence or inaccuracy of company records; and significant undercapitalization of the business entity.</strong> <strong> Virginia businesses must be cognizant of such corporate formalities and protocols in order to protect the personal assets of owners from potential liability.</strong><br />
&nbsp;</p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2012/01/articles/best-practices/virginia-state-court-contractor-can-pursue-assets-of-subcontractors-owner/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2012/01/articles/best-practices/virginia-state-court-contractor-can-pursue-assets-of-subcontractors-owner/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/articles">Best Practices</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Business Incorporation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Henrico County Circuit Court</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Litigation</category><category domain="http://www.virginiabusinesslawupdate.com/articles/litigation">Virginia Litigation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">contractor</category><category domain="http://www.virginiabusinesslawupdate.com/tags">pierce the corporate veil</category><category domain="http://www.virginiabusinesslawupdate.com/tags">subcontractor</category>
         <pubDate>Sun, 01 Jan 2012 14:41:42 -0500</pubDate>
         <dc:creator>Angela France </dc:creator>
      
      </item>
            <item>
         <title>Fairfax County Circuit Court Awards Damages To IT Government Contractor In Non-Compete Case Against Subcontractor</title>
         <description><![CDATA[<p><strong>A <a href="http://www.fairfaxcounty.gov/courts/circuit/">Fairfax County Circuit Court</a> judge awarded a Virginia information technology government contractor $172,395 in damages in a <a href="http://www.virginiabusinesslawupdate.com/uploads/file/Preferred Systems Solutions, Inc_ v_ GP Consulting LLC.pdf">non-compete case against a former subcontractor</a>. </strong>The court determined that the defendant subcontractor breached the covenant not-to-compete provision in its consulting agreement with the plaintiff government contractor.</p>
<p>A Virginia court will enforce a non-compete clause between an employer and an employee if it is: sufficiently narrowly drawn to protect the employer&rsquo;s legitimate business interest; not unduly burdensome on the employee&rsquo;s ability to earn a living; and, not against public policy. As restrictive covenants are generally disfavored in Virginia (as they restrain free trade), the employer bears the burden of proof and any ambiguities in the contract are construed in favor of the employee.</p>
<p>In this case, the court concluded that the covenant not-to-compete at issue was enforceable because it only prevented the subcontractor from working for two companies; it proscribed competition for only a year; and, it was specific as to the type of work that was prohibited under the agreement between the parties.</p>
<p><strong>The damages awarded by the court to the plaintiff government contractor were based on the lost profits that the non-compete clause was supposed to prevent.</strong> As the court noted, &ldquo;[a]warding damages on the breach of the agreement protects plaintiff&rsquo;s legitimate business interest by compensating it for the breach.&rdquo;</p>
<p><em>Preferred Systems Solutions, Inc. v. GP Consulting LLC</em>, Circuit Court for Fairfax County, Virginia (July 28, 2011)</p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2011/12/articles/litigation/virginia-litigation/fairfax-county-circuit-court-awards-damages-to-it-government-contractor-in-noncompete-case-against-subcontractor/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2011/12/articles/litigation/virginia-litigation/fairfax-county-circuit-court-awards-damages-to-it-government-contractor-in-noncompete-case-against-subcontractor/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/articles">Business Contracts</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Fairfax County</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Non-Compete</category><category domain="http://www.virginiabusinesslawupdate.com/articles/litigation">Virginia Litigation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">covenant not-to-compete</category><category domain="http://www.virginiabusinesslawupdate.com/tags">government contractor</category><category domain="http://www.virginiabusinesslawupdate.com/tags">lawsuit</category><category domain="http://www.virginiabusinesslawupdate.com/tags">subcontractor</category>
         <pubDate>Thu, 29 Dec 2011 17:23:49 -0500</pubDate>
         <dc:creator>H. Scott Johnson, Jr.</dc:creator>
      
      </item>
            <item>
         <title>Eastern District of Virginia Court Permanently Enjoins Verizon's VOD Service</title>
         <description><![CDATA[<p>An <a href="http://www.vaed.uscourts.gov/">Eastern District of Virginia Court</a> has permanently enjoined Verizon from infringing upon patents of a California-based Company, ActiveVideo Networks, Inc. (&ldquo;ActiveVideo&rdquo;), including two patents which will have a direct impact upon Verizon&rsquo;s ability to offer its popular Video on Demand (&ldquo;VOD&rdquo;) services.  In the case, <a href="http://www.virginiabusinesslawupdate.com/uploads/file/https___ecf_vaed_uscourts_gov_cgi-bin_show_temp_pl_file=3487970-0--6497.pdf"><em>ActiveVideo Networks, Inc. v. Verizon Communications, Inc., et al.</em></a>, ActiveVideo sued Verizon for allegedly infringing upon several of its patents.  After a three-week jury trial, the jury found in favor of ActiveVideo and awarded it $115,000,000 in damages for Verizon&rsquo;s infringement.  ActiveVideo then sought a permanent injunction from the Court enjoining Verizon from continuing to infringe upon the patents.</p>
<p>In analyzing the injunction standard under the Patent Act, Judge Raymond A. Jackson of the Eastern District of Virginia relied heavily upon the four-part test set forth by the United States Supreme Court in the case of <a href="http://caselaw.lp.findlaw.com/scripts/getcase.pl?court=US&amp;vol=000&amp;invol=05-130"><em>ebay, Inc. v. MercExchange, L.L.C</em><em>.</em></a>  The District Court found in favor of ActiveVideo regarding all four prongs finding that: 1) ActiveVideo had been, and would continue to be, irreparably harmed by Verizon&rsquo;s unauthorized use of its technology; 2) ActiveVideo did not have an adequate monetary remedy at law because the  continuing harm associated with loss of market share and brand recognition of the VOD service were difficult to quantify; 3) the balance of hardships favored ActiveVideo because, as a small company, it relied heavily upon the patents infringed upon by Verizon, while Verizon offered numerous services and would be less affected by having to cease use and/or find alternatives to offering the VOD service; and 4) public interests and public policy were served by protecting patent rights.  Regarding this last prong, the Court specifically noted that, &ldquo;[t]hough Verizon does add other components to be able to offer the completed product, Verizon&rsquo;s FiOS system, and more specifically the VOD aspect of the FiOS system, could not function without the use of ActiveVideo&rsquo;s technology.&rdquo;  <a href="http://www.virginiabusinesslawupdate.com/uploads/file/https___ecf_vaed_uscourts_gov_cgi-bin_show_temp_pl_file=3642692-0--3212.pdf"><em>Mem. Op. at 17</em></a>.</p>
<p>Nevertheless, have no fear Verizon VOD users.  The Court granted Verizon a six-month &ldquo;sunset&rdquo; window of time to come up with a non-infringing alternative to its current VOD system, and Verizon claims it has already been diligently working to come up with an alternative system.  Therefore, before the time is up, it is likely Verizon will have embarked upon an alternative method to provide the popular VOD service to its customers &ndash; thus, enabling it to keep sending out those monthly Verizon bills to its subscribers at a brisk and healthy pace.    <br />
<br />
&copy; Copyright, PCT Law Group 2011.  All rights reserved.<br />
&nbsp;</p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2011/11/articles/intellectual-property/eastern-district-of-virginia-court-permanently-enjoins-verizons-vod-service/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2011/11/articles/intellectual-property/eastern-district-of-virginia-court-permanently-enjoins-verizons-vod-service/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/tags">Eastern District of Virginia</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Intellectual Property</category><category domain="http://www.virginiabusinesslawupdate.com/articles/litigation">Virginia Litigation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">business litigation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">patent infringement litigation</category>
         <pubDate>Mon, 28 Nov 2011 16:18:26 -0500</pubDate>
         <dc:creator>Malik Cutlar</dc:creator>
      
      </item>
            <item>
         <title>Employee Allowed to go Forward with Sexual Harassment &amp; Retaliation Claims</title>
         <description><![CDATA[<p>The Fourth Circuit Court of Appeals allowed a former city employee&rsquo;s sexual harassment and retaliation claims to proceed to trial by reversing a lower court ruling which granted summary judgment in favor of the employer.  Plaintiff Katrina Okoli, formerly an executive assistant for John P. Stewart, the director of Baltimore&rsquo;s Commission on Aging and Retirement, filed a lawsuit alleging <strong>sexual harassment hostile work environment</strong>, <strong>quid pro quo sexual harassment</strong>, and <strong>retaliation</strong>.  In the case of <a href="http://pacer.ca4.uscourts.gov/opinion.pdf/082198.P.pdf"><em>Okoli v. City of Baltimore, et al.</em></a>, Plaintiff Okoli alleged that over a four month span, Defendant Stewart repeatedly sexually propositioned her; told her of his alleged sexual exploits; asked her about her underwear; fondled her leg underneath a table on several occasions; and forcibly tried to kiss her when they were alone in a conference room.  Okoli alleged that she rejected such advances by Stewart and also twice complained about the harassment to officials within the City government, as well as wrote a letter to Baltimore&rsquo;s then-mayor Martin O&rsquo;Malley concerning the harassment.  Okoli was fired by Stewart just hours after her letter was received by the mayor&rsquo;s office.</p>
<p>For its part, the City contended (and apparently the lower court agreed) that Stewart&rsquo;s conduct was sporadic and infrequent and did not rise to the level of a hostile work environment.  Further, the City argued that Okoli&rsquo;s work had deficiencies, and that she was going to be fired even before she wrote the letter complaining of Stewart&rsquo;s behavior.  Additionally, the City argued, Okoli&rsquo;s letter was non-specific and did not state that she was being &ldquo;sexually&rdquo; harassed by Stewart, only &ldquo;harassed.&rdquo;  Therefore, they argued, Okoli did not engage in protected activity under <strong>Title VII</strong> to warrant a retaliation claim against the City.</p>
<p>The Appellate Court disagreed and held that the statements attributed to Stewart were both severe and pervasive.  In addition, the Court held that a plaintiff need not mention the &ldquo;magic words&rdquo; of &ldquo;sex&rdquo; or &ldquo;sexual&rdquo; to effectively advance a sexual harassment complaint.  Citing decisions from other circuit courts, the Court held that the complainant only need put the employer on notice that unlawful behavior is afoot.  Okoli&rsquo;s use of the words &ldquo;unethical,&rdquo; &ldquo;degrading and dehumanizing&rdquo; in her letter complaining about Stewart&rsquo;s behavior were enough to raise a sexual harassment complaint.  Finally, the Court determined that the <a href="http://www.mdd.uscourts.gov/">district court</a> erred in concluding that simply because Stewart had a document on his computer that pre-dated Okoli&rsquo;s letter, such document was a termination letter.  Stewart modified the computer document three times before delivering it to Okoli as a termination letter just hours after her sexual harassment complaint reached the mayor&rsquo;s office.  Under those facts, the Court concluded that there was sufficient evidence to infer that Stewart did not intend to fire Okoli prior to receiving word that she complained about his behavior to the mayor and his staff.</p>
<p>The <a href="http://www.ca4.uscourts.gov/">Fourth Circuit Court of Appeals</a> hears appeals involving <strong>Virginia employment cases</strong>.</p>
<p>&copy; Copyright, <a href="http://www.pctlg.com/PCTLG2.0/index.html">PCT Law Group 2011</a>.  All rights reserved.<br />
&nbsp;</p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2011/09/articles/employment-law-1/employee-allowed-to-go-forward-with-sexual-harassment-retaliation-claims/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2011/09/articles/employment-law-1/employee-allowed-to-go-forward-with-sexual-harassment-retaliation-claims/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/articles">Employment Law</category><category domain="http://www.virginiabusinesslawupdate.com/">Legal</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Litigation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Title VII</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Virginia employment cases</category><category domain="http://www.virginiabusinesslawupdate.com/tags">federal appeals court</category><category domain="http://www.virginiabusinesslawupdate.com/tags">federal district court</category><category domain="http://www.virginiabusinesslawupdate.com/tags">hostile work environment</category><category domain="http://www.virginiabusinesslawupdate.com/tags">quid pro quo</category><category domain="http://www.virginiabusinesslawupdate.com/tags">retaliation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">sexual harassment</category>
         <pubDate>Mon, 26 Sep 2011 15:44:02 -0500</pubDate>
         <dc:creator>Malik Cutlar</dc:creator>
      
      </item>
            <item>
         <title>U.S. District Court (Alexandria): No Personal Jurisdiction Over Defendant In Website Defamation Case</title>
         <description><![CDATA[<p>The <a href="http://www.vaed.uscourts.gov/">U.S. District Court in Alexandria, Virginia</a> (often referred to as the &quot;rocket docket&quot;) recently held that a Canadian businessman who does business in Loudoun County, Virginia cannot sue an out-of-state resident who purportedly defamed the businessman on her website. <em><strong>The court concluded that it could not exercise personal jurisdiction over the defendant because there was no evidence that the defendant intended to target a Virginia audience with its website.</strong></em></p>
<div>
<p>Under Virginia law, in order for a court to exercise personal jurisdiction over a defendant, a plaintiff must demonstrate that its lawsuit arises from activities that occurred in Virginia (&ldquo;specific jurisdiction&rdquo;). Alternatively, a plaintiff can establish a basis for personal jurisdiction over a defendant by showing that the defendant has such &ldquo;continuous and systematic contacts&rdquo; with Virginia that the defendant, for all intents and purposes, is domiciled in Virginia (&ldquo;general jurisdiction&rdquo;).</p>
<p>In this action, as the website did not target Virginia and the plaintiff could not put forth any evidence to show that the out-of-state defendant had a &ldquo;continuous and systematic&rdquo; presence in Virginia, the court held that it could not subject the defendant to jurisdiction in a Virginia court.</p>
<p><em><a href="http://www.virginiabusinesslawupdate.com/uploads/file/Knight v_ Grayson and John Doe # 1.pdf">Knight v. Grayson and John Doe # 1</a>, </em>United States District Court for the Eastern District of Virginia (Alexandria Division)</p>
</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<p>&nbsp;</p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2011/08/articles/litigation/virginia-litigation/us-district-court-alexandria-no-personal-jurisdiction-over-defendant-in-website-defamation-case/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2011/08/articles/litigation/virginia-litigation/us-district-court-alexandria-no-personal-jurisdiction-over-defendant-in-website-defamation-case/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/tags">Alexandria federal court</category><category domain="http://www.virginiabusinesslawupdate.com/articles/litigation">Virginia Litigation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">business litigation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">defamation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">personal jurisdiction</category>
         <pubDate>Thu, 18 Aug 2011 15:45:18 -0500</pubDate>
         <dc:creator>H. Scott Johnson, Jr.</dc:creator>
      
      </item>
            <item>
         <title>Eastern District of Virginia Court Allows FMLA Suit Against Individual County Official</title>
         <description><![CDATA[<p><strong>Individual May Be Deemed an &quot;Employer&quot; Under the FMLA</strong></p>
<p>Plaintiff Patricia Weth, formerly a deputy treasurer for litigation in the Arlington County Treasurer&rsquo;s Office, took leave under the Family and Medical Leave Act (&ldquo;FMLA&rdquo;) for several weeks during December of 2009 until mid-February of 2010 to have medically necessary surgery performed.  On the same day that she returned to work from her medical leave, Weth was told by her boss, Arlington County Treasurer Francis O&rsquo;Leary, that he wanted her to find a new job and that her main focus should be finding a new job.  O&rsquo;Leary promptly stripped Weth of almost all of her job duties, and told her she was no longer to perform other job duties with the exception of one project and the duty of finding a new job.  Predictably, under such facts, Weth filed claims of FMLA interference for the County&rsquo;s failure to place her in the same or similar position after her FMLA leave as she had prior to the leave; and a claim of FMLA retaliation for her demotion and discharge after returning from FMLA leave.  However, Weth&rsquo;s lawsuit ran into a stumbling block concerning the appropriate defendant(s) to sue.</p>
<p>In the case of <a href="http://www.virginiabusinesslawupdate.com/uploads/file/Weth v_ O'Leary.pdf">Weth v. Francis X. O&rsquo;Leary</a>, Plaintiff initially filed suit against Arlington County, the County Treasurer&rsquo;s Office, and Defendant O&rsquo;Leary.  However, since County Treasurers such as O&rsquo;Leary are deemed independent constitutional officers under the Virginia Constitution, the Court dismissed the case against the County and the Treasurer&rsquo;s office as they were improper Defendants.  Weth then filed an Amended Complaint against O&rsquo;Leary in his official and individual capacity.  On summary judgment, after dismissing the case against O&rsquo;Leary in his official capacity based upon sovereign immunity, one of the main issues revolved around whether O&rsquo;Leary, as a County official, could be sued under the FMLA in his individual capacity as an &ldquo;employer&rdquo;.  Acknowledging that the issue remains an open question in the Fourth Circuit, and that there is a split on the issue within the federal courts, the Court looked to the text of the FMLA and the holding of a majority of the district courts that have ruled on the issue.  In particular, the Court looked to the Fifth and Eight Circuits, which (relying upon the text of the FMLA) have held that public agency officials, including state officials, can be sued in their individual capacities if they act directly or indirectly on behalf of the employer.  A prominent example of such authority being the hiring and firing of employees.</p>
<p>In this case, since O&rsquo;Leary clearly had the authority to hire and fire employees such as Plaintiff Weth, the Court held that he could be sued in his individual capacity under the FMLA.  The Court concluded that to rule otherwise would run contrary to the very text of the FMLA, which, in addition to including those with such authority as O&rsquo;Leary in the definition of an employer, also states that &ldquo;public agencies&rdquo; are included within the definition of employer.  Therefore, the Court ruled that Plaintiff Weth will be allowed to pursue her claims against Defendant O&rsquo;Leary in his individual capacity at trial.</p>
<p>&copy; Copyright, PCT Law Group 2011.  All rights reserved.<br />
&nbsp;</p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2011/08/articles/litigation/virginia-litigation/eastern-district-of-virginia-court-allows-fmla-suit-against-individual-county-official/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2011/08/articles/litigation/virginia-litigation/eastern-district-of-virginia-court-allows-fmla-suit-against-individual-county-official/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/tags">Court</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Eastern District of Virginia</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Employment Law</category><category domain="http://www.virginiabusinesslawupdate.com/tags">FMLA</category><category domain="http://www.virginiabusinesslawupdate.com/articles/litigation">Virginia Litigation</category>
         <pubDate>Tue, 09 Aug 2011 10:55:57 -0500</pubDate>
         <dc:creator>Malik Cutlar</dc:creator>
      
      </item>
            <item>
         <title>Small and Medium-sized Enterprises and Cutting Through the Hoopla Over False Patent Marketing</title>
         <description><![CDATA[<p style="text-align: justify"><span style="font-size: small">There has been a lot of recent talk, blog posts, articles, court activity and even proposed legislation in Congress around the issue of &ldquo;False Patent Marking.&rdquo;&nbsp; What does it all mean and why should small- and medium-sized enterprises (SMEs) care!?&nbsp; Well, I present answers, in brief, to these questions below.</span></p>
<p style="text-align: justify"><span style="font-size: small">The first thing to know is that the U.S. Patent Laws allow patent owners to give notice to the public by affixing a notice to the patented product (or its packaging if marking the product is not practical or possible) such as &ldquo;Protected by U.S. Patent No. 3,141,592&rdquo;&nbsp; <em>See</em> </span><a target="_blank" href="http://www.uspto.gov/web/offices/pac/mpep/documents/appxl_35_U_S_C_287.htm"><span style="font-size: small">35 U.S.C. &sect; 287(a)</span></a><span style="font-size: small">.&nbsp; This is colloquially known as the &ldquo;patent marking&rdquo; statute.&nbsp; Absent such a marking, in most cases, a patent owner cannot recover damages for patent infringement unless they can prove the infringer was notified of the infringement.</span></p>
<p style="text-align: justify"><span style="font-size: small">Second, we know that affixing a patent notice to a product (or its packaging) not only acts as a deterrent to competitors by putting them on notice, but it also has some marketing cache!&nbsp; Thus, that is why it is common to see not only actual patent number notices, but also notices of &ldquo;patent pending&rdquo; on many products.</span></p>
<p style="text-align: justify"><span style="font-size: small">Third, there is also what is known as the &ldquo;false marking&rdquo; statute which prohibits anyone from marking a product (or its packaging) with: </span></p>
<ul>
    <li><span style="font-size: small">an expired patent number </span></li>
    <li><span style="font-size: small">a false patent number <br />
    </span></li>
    <li><span style="font-size: small">with the words &ldquo;patent applied for&rdquo; or &ldquo;patent pending&rdquo; when no application for patent has been made or is no longer pending, respectively. <br />
    </span></li>
</ul>
<p><span style="font-size: small"><em>See</em> </span><a target="_blank" href="http://www.uspto.gov/web/offices/pac/mpep/documents/appxl_35_U_S_C_292.htm"><span style="font-size: small">35 U.S.C. &sect; 292</span></a><span style="font-size: small">.&nbsp; Each of these three false marking offenses, however, must be shown to have been done &ldquo;for the purpose of deceiving the public,&rdquo; and not merely done as a result a good faith mistake.<br />
</span></p>
<p style="text-align: justify"><span style="font-size: small">What makes the false marking statute interesting is that it contains a whistleblower-type provision.&nbsp; That is, any private citizen can sue the manufacturer of a product they believe has been falsely marked to recover &ldquo;not more than $500 for every such offense.&rdquo;&nbsp; Thus, one can imagine that if a company produces 1,000,000 units of a product that in some way was falsely marked, a $500M lawsuit becomes very attractive for anyone with the time and the right contingency law firm behind them.&nbsp; <em>See</em> </span><a target="_blank" href="http://www.cafc.uscourts.gov/opinions/09-1044.pdf"><span style="font-size: small"><em>Forest Group, Inc. v. Bon Tool Co.</em>, 590 F.3d 1295 (Fed. Cir. 2009)</span></a><span style="font-size: small">.&nbsp; In fact, over 150 of these types of lawsuits have been filed in the last several months alone!&nbsp; The only drawback is that 50% of any recovery must go to the federal government.&nbsp; (Thus, the private citizen in my example can keep only $250M of the possible recoveries &ndash; still not too shabby!)</span></p>
<p style="text-align: justify"><span style="font-size: small">On June 10, 2010, a federal court of appeals, interpreting the false marking statute, ruled that &ldquo;the combination of a false [patent marking] and knowledge that the [patent marking] was false creates a rebuttable presumption of intent to deceive the public.&rdquo;&nbsp; <em>See</em> </span><a target="_blank" href="http://www.cafc.uscourts.gov/opinions/09-1547.pdf"><span style="font-size: small"><em>Pequignot v. Solo Cup Co.</em>, Case No. 2009-1547 (Fed. Cir.)</span></a><span style="font-size: small">.&nbsp; A defendant in one of these false marking suits can successfully defend itself by showing via &ldquo;a clear preponderance of the evidence that it did not have the requisite purpose to deceive.&rdquo;&nbsp; For example, the defendant in the <em>Solo Cup</em> case successfully obtained a dismissal of the suit by explaining that they knew the patent number on their products had expired but it was prohibitively expensive and disruptive to the business to prematurely replace the manufacturing molds which contained the now-expired patent numbers.</span></p>
<p style="text-align: justify"><span style="font-size: small">So, what should SMEs glean from all this hoopla?&nbsp; Well, four things: </span></p>
<ol>
    <li><span style="font-size: small">If your enterprise manufactures no products covered by U.S. patents, ignore it; </span></li>
    <li><span style="font-size: small">If your company has no patents that cover a specific product, do not &ldquo;fake it until you make it&rdquo; by marking it with one or more non-existent patent numbers; </span></li>
    <li><span style="font-size: small">If your company has not applied for any patents that cover a specific product, do not use the words &ldquo;patent pending&rdquo; in an attempt to obtain marketing cache for such product; and </span></li>
    <li><span style="font-size: small">If any of your competitors are manufacturing products which you suspect are falsely marked with an intent to deceive the public, consult a plaintiff&rsquo;s lawyer!</span></li>
</ol>
<p>&nbsp;</p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2011/05/articles/intellectual-property/small-and-mediumsized-enterprises-and-cutting-through-the-hoopla-over-false-patent-marketing/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2011/05/articles/intellectual-property/small-and-mediumsized-enterprises-and-cutting-through-the-hoopla-over-false-patent-marketing/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/tags">False Patent Marketing</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Intellectual Property</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Small</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Small </category><category domain="http://www.virginiabusinesslawupdate.com/tags">business'</category>
         <pubDate>Wed, 25 May 2011 15:49:02 -0500</pubDate>
         <dc:creator>Ray Millien</dc:creator>
      
      </item>
            <item>
         <title>Virginia Federal Jury Rules on Virginia Tech Equal Pay Case</title>
         <description><![CDATA[<p>&nbsp;A <a href="http://www.vawd.uscourts.gov/">Virginia Federal Court</a> jury recently determined that <a href="http://www.vt.edu/">Virginia Tech</a> violated the <a href="http://www.eeoc.gov/laws/statutes/epa.cfm">Equal Pay Act</a>, and awarded back pay to two women employees of its fundraising office.  The <a href="http://www.eeoc.gov/laws/statutes/epa.cfm">Equal Pay Act</a> is a federal law amending the <a href="http://www.dol.gov/whd/flsa/">Fair Labor Standards Act</a>, which prohibits employers from paying unequal wages to women and men for doing the same or substantially similar work.</p>
<p>To establish a case under the <a href="http://www.eeoc.gov/laws/statutes/epa.cfm">Equal Pay Act</a>, an employee must establish that:</p>
<ul>
    <li>different wages are paid to employees of the opposite sex;</li>
    <li>the employees perform substantially equal work on jobs requiring equal skill, effort and responsibility; and</li>
    <li>the jobs are performed under similar working conditions.</li>
</ul>
<p>However, an employee who proves all the above elements may still not prevail.  A business may avoid liability if it establishes that such payment was made pursuant to a seniority system, a merit system, a system which measures earnings by quantity or quality of production, or a differential based on any other factor other than gender.</p>
<p>In the Virginia Tech cases, the two women claimed their starting salaries were lower than the men who did the same work.  In its defense, Virginia Tech countered that the men had more experience when hired.</p>
<p>Both sides presented extensive statistical evidence.  According to the plaintiff&rsquo;s economist, men&rsquo;s salaries involved with Virginia Tech&rsquo;s fundraising were an average of 15% higher.  Virginia Tech&rsquo;s expert analyzed the experience and duties of the employees, and determined there was only an 8% difference. &nbsp;Tech's expert concluded that this difference could be linked to gender, but opined that there was a chance it occurred randomly since the disparity was not statistically significant.</p>
<p>Notably, one of the women testified that when she inquired about the pay differential between her and her male predecessor, the senior regional director of major gifts replied that her predecessor had a family to support. &nbsp;In addition, the Judge identified other statements that tend to show Virginia Tech's animus toward the women when he previously denied Virginia Tech's motion for summary judgment.</p>
<p><strong>How does your company prevent potential liability under the Equal Pay Act?  Businesses should evaluate its pay structure, including policies regarding seniority systems, merit systems and incentive systems in light of the prohibition of gender pay disparity.  An effective way to prevent managers and supervisors from making compensation decisions based on a protected category under the discrimination laws is to establish and implement a comprehensive job evaluation system. &nbsp;As the lawyers for the women argued during the trial in this matter - if Virginia Tech &quot;had good policies, we wouldn't be here.&quot; &nbsp;</strong></p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2011/04/articles/employment-law-1/virginia-federal-jury-rules-on-virginia-tech-equal-pay-case/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2011/04/articles/employment-law-1/virginia-federal-jury-rules-on-virginia-tech-equal-pay-case/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/articles">Employment Law</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Equal Pay Act</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Litigation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Virginia Federal Court</category><category domain="http://www.virginiabusinesslawupdate.com/articles/litigation">Virginia Litigation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Virginia Tech</category><category domain="http://www.virginiabusinesslawupdate.com/tags">gender discrimination</category><category domain="http://www.virginiabusinesslawupdate.com/tags">job evaluation system</category>
         <pubDate>Thu, 28 Apr 2011 15:36:56 -0500</pubDate>
         <dc:creator>Angela France </dc:creator>
      
      </item>
            <item>
         <title>FLSA Compliance for Company's Unpaid Interns</title>
         <description><![CDATA[<p><img alt="Virginia Business Lawyer" width="150" height="99" align="left" src="http://www.virginiabusinesslawupdate.com/uploads/image/Office(3).jpg" />As summer quickly approaches, businesses begin receiving an increasing number of offers for unpaid internships.  As many businesses already know, there are many advantages to using an intern &ndash; unpaid internships may help fuel growth for your company and also provide an opportunity to mentor young professionals.  However, unpaid interns can create legal troubles for the unwary business owner.  Federal labor laws governing internships provide that the relationship has to benefit the intern more than the company.  If it doesn&rsquo;t, then the business must comply with the <a href="http://www.law.cornell.edu/uscode/129/usc_sup_01_29_10_8.html">Fair Labor Standards Act (&ldquo;FLSA&rdquo;)</a> by paying minimum wages and possibly overtime.</p>
<p>The <a href="http://www.dol.gov/whd/">U.S. Department of Labor&rsquo;s Wage and Hour Division</a> outlined a <a href="http://www.dol.gov/whd/regs/compliance/whdfs71.pdf">list of criteria</a> to determine whether a trainee or intern is an &ldquo;employee&rdquo; under the FLSA, and thus, must comply with Federal wage laws.</p>
<p>The following criteria provide guidance in evaluating internship programs for for-profit organizations, but it is important to note that each program is unique and must be carefully examined:</p>
<ul>
    <li>the training, even though it includes actual operation of the facilities of the employer, is similar to that which would be given in a vocational school;</li>
    <li>the training is for the benefit of the trainee;</li>
    <li>the trainees do not displace regular employees, but work under close observation;</li>
    <li>that the employer that provides the training derives no immediate advantage from the activities of the trainees and on occasion the employer&rsquo;s operations may actually be impeded;</li>
    <li>the trainees are not necessarily entitled to a job at the completion of the training period; and</li>
    <li>the employer and the trainee understand that the trainees are not entitled to wages for the time spent in training.</li>
</ul>
<p>If your company&rsquo;s internship program does not satisfy all of the above criteria, your interns may be considered <a href="http://www.dol.gov/whd/flsa/index.htm">&ldquo;employees&rdquo; under the FLSA</a>. Hiring an intern, which qualifies as an &ldquo;employee&rdquo; may cost your company thousands in unpaid wages and legal fines!</p>
<p><strong>So, how do you ensure compliance? Establish a written internship program outlining the terms and structure of the relationship in a way that the intern is receiving the full benefit of the learning experience, and ensure that your managers and other employees properly implement it.</strong></p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2011/04/articles/best-practices/flsa-compliance-for-companys-unpaid-interns/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2011/04/articles/best-practices/flsa-compliance-for-companys-unpaid-interns/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/articles">Best Practices</category><category domain="http://www.virginiabusinesslawupdate.com/tags">DOL</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Department of Labor</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Employment Law</category><category domain="http://www.virginiabusinesslawupdate.com/tags">FLSA</category><category domain="http://www.virginiabusinesslawupdate.com/tags">unpaid intern</category><category domain="http://www.virginiabusinesslawupdate.com/tags">wages</category>
         <pubDate>Mon, 25 Apr 2011 14:32:47 -0500</pubDate>
         <dc:creator>Angela France </dc:creator>
      
      </item>
            <item>
         <title>Who Owns Newly-Created IP within a University Community?</title>
         <description><![CDATA[<p><span style="font-size: small;">I was recently contacted by a professor who was seeking advice about a piece of intellectually property (IP) he created, and that his university was profitably exploiting.  Who owned the IP?  Can he exploit it himself?  Was he entitled to share in the proceeds above and beyond his university (base) salary?  Not surprisingly, these questions are not rare.  After all, universities, colleges and research institutions are hot beds of creativity.  In 2008, U.S. universities and research institutions spent over $51.47B in R&amp;D and received 3,280 issued U.S. patents, all while forming 595 new companies in IP &ldquo;spin-outs.&rdquo; [1]</span></p>
<p><span style="font-size: small;">Given this setting, who then owns the IP created by someone within a university community?  Intuitively, the answer seems simple in the case of a tenured, research professor who develops IP related to their university research duties &ndash; the university owns it!  But how about the case of an undergraduate student who creates IP totally unrelated to any of her coursework!?  The student?  How about certain university community citizens, such as university executives, administrators, (exempt or nonexempt) staff, graduate students, postdoctoral fellows, wage payroll employees, adjunct faculty, emeritus or retired faculty, visiting scholars and others?  The analysis for those university community citizens is often a fact-intensive endeavor.</span></p>
<p><span style="font-size: small;">In <em>general</em>, under varying applicable state and federal laws where the university employs the individual in question, there is a presumption that the employee owns the rights to their IP, even though it may have been created during the course of their employment.  This general rule, however, has<em> two exceptions</em> and <em>one limitation</em>.</span></p>
<ul>
    <li><span style="font-size: small;">&nbsp;<em>First Exception:</em> If the employee has an express employment agreement, stating the contrary (i.e., an employee agreement assigning all IP to the employer/university), then the general rule does not apply.</span></li>
    <li><span style="font-size: small;"><em>Second Exception:</em> If the employee was specifically &ldquo;hired to invent,&rdquo; later directed to solve a specific problem, or his employment requires that he exercise his &ldquo;inventive faculties,&rdquo; then the above-stated general rule also does not apply.</span></li>
    <li><span style="font-size: small;"><em>Limitation: </em>Even when none of the two exceptions to the above-stated general rule apply, the employer &ndash; in the case of patented inventions &ndash; may have a non-exclusive, non-transferable, royalty-free license to practice the employee&rsquo;s patented invention if it was made using the resources of the employer.  This is known as an employer&rsquo;s &ldquo;shop right.&rdquo;</span></li>
</ul>
<p><span style="font-size: small;">An overwhelming majority of universities have an &ldquo;official intellectual property policy&rdquo; that requires employees, as a condition to employment, to assign their IP rights under certain circumstances (e.g., when university funds or facilities are involved in the creation of the IP).  Thus, most situations fall under the above-stated first exception even though many professors and postdoctoral fellows fail to read such policies when they sign their employment agreements!</span></p>
<p><span style="font-size: small;">So what about the case of the undergraduate student who created IP totally unrelated to any of her coursework?  What if that IP was created without a professor&rsquo;s help?  Well, in a recent reported <a href="http://www.huffingtonpost.com/2011/01/24/young-inventors-prompt-co_n_812907.html">case</a> having those exact facts, a university&rsquo;s lawyers demanded a 25% ownership stake and two-thirds of any profits from four undergraduate students who created a popular iPhone&reg; application in their dorm room!  Although the university eventually backed down, one <a href="http://www.google.com/hostednews/ap/article/ALeqM5ilfjD3zn6ImYtcZIVjuam7MztG8A?docId=1e12e21030c044938bb0f2d37e7c6130">campus technology transfer expert</a> has observed that many universities &ldquo;generally seek to retain ownership, or at least have a formalized mechanism for assessing ownership of a student&rsquo;s work in much the same way they would regarding a faculty member&rsquo;s work.&rdquo;</span></p>
<p><span style="font-size: small;">In sum, those working/learning/creating within a university community should become familiar with their university&rsquo;s intellectual property policy at the start of their affiliation, and pay attention to the agreements they sign as a part of the new university employee &ldquo;on-boarding&rdquo; process. And, when potentially valuable new IP is created, be vigilant about asserting their rights in such IP.</span></p>
<p><br />
&nbsp;[1] Association of University Technology Managers, <em>AUTM U.S. Licensing Activity Survey, FY2008: Survey Summary.</em><br />
<br />
&nbsp;</p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2011/04/articles/intellectual-property/who-owns-newlycreated-ip-within-a-university-community/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2011/04/articles/intellectual-property/who-owns-newlycreated-ip-within-a-university-community/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/tags">IP</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Intellectual Property</category><category domain="http://www.virginiabusinesslawupdate.com/tags">employment agreement</category><category domain="http://www.virginiabusinesslawupdate.com/tags">university</category>
         <pubDate>Mon, 11 Apr 2011 12:14:26 -0500</pubDate>
         <dc:creator>Ray Millien</dc:creator>
      
      </item>
            <item>
         <title>$3 Million Personal Injury Claim Against Virginia Business Dismissed</title>
         <description><![CDATA[<p><span style="font-size: small;">We have all been there.  Walking through the aisle of a store and some store personnel who was stocking a shelf has left a ladder or some supplies right in the middle of the aisle, obstructing the path.  Well, the Plaintiff in this case did what most of us would do.  She attempted to walk around the ladder, but when she did -- <strong>bam!</strong> &ndash; she hit her head on a metal shelf that was on the other side of ladder, and she (sadly) suffered significant, and likely permanent, brain injury.</span></p>
<p><span style="font-size: small;">In this diversity jurisdiction personal injury case, </span><a href="http://www.virginiabusinesslawupdate.com/uploads/file/Zankow v Sears.pdf"><span style="font-size: small;"><em>Zankow v. Sears Holding Corp., et al</em>.</span></a><span style="font-size: small;">, Plaintiff claimed that Sears was negligent because the placement of the ladder combined with the shelves in the narrow aisle created an unreasonably dangerous condition that caused her serious and permanent injuries.  The shelves were 1 to 1.5 inches thick and were connected to the back of a shelving unit with no side walls.  While trying to get around the ladder, Plaintiff apparently did not notice the shelves as she was focused on the ladder &ndash; the original obstruction.</span></p>
<p><span style="font-size: small;">For its part, Defendant claimed that it should not be held liable as the ladder and the shelves were in plain sight; and, in any event, because Plaintiff failed to use ordinary and reasonable care in walking around the ladder, she was contributorily negligent and barred from recovery.</span></p>
<p><span style="font-size: small;">On summary judgment, the Court dismissed Plaintiff&rsquo;s claims.  The Court ruled that from the pictures submitted by the Plaintiff of the scene (which were attached to the Opinion) and the description provided, the shelf and the ladder were &ldquo;<em>open and obvious</em>&rdquo; conditions from which Plaintiff had a duty to use reasonable care to avoid.  The court rejected Plaintiff&rsquo;s argument that the shelf she hit her head on was protruding, because the evidence showed that no one shelf stuck out further than the others.  Further, the Court did not find that the combination of the ladder and the shelves rendered either of the hazards &ldquo;latent&rdquo; such that Plaintiff would not have been expected to notice and avoid the open and obvious hazards.  <em>Citing Virginia Supreme Court precedent, the Court ruled that once a hazard is deemed to be open and obvious, an injured plaintiff&rsquo;s claim must fail as a matter of law since she will be deemed to have failed to exercise reasonable care, and will thus be found contributorily negligent. </em></span><br />
&nbsp;</p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2011/04/articles/litigation/virginia-litigation/3-million-personal-injury-claim-against-virginia-business-dismissed/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2011/04/articles/litigation/virginia-litigation/3-million-personal-injury-claim-against-virginia-business-dismissed/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/tags">Eastern District of Virginia</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Rocket Docket</category><category domain="http://www.virginiabusinesslawupdate.com/articles/litigation">Virginia Litigation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Zankow v. Sears Holding Corp., et al.</category><category domain="http://www.virginiabusinesslawupdate.com/tags">personal injury</category>
         <pubDate>Mon, 04 Apr 2011 12:49:54 -0500</pubDate>
         <dc:creator>Malik Cutlar</dc:creator>
      
      </item>
            <item>
         <title>Federal Employee's Discrimination &amp; Retaliation Claims Dismissed</title>
         <description><![CDATA[<p>Federal employee Robert T. Perry (&ldquo;Perry&rdquo;) had a long-running legal battle with his federal employer, the <a href="http://www.pbgc.gov/">Pension Benefit Guaranty Corporation</a> (&ldquo;PBGC&rdquo;). After three lawsuits, two of which were settled, Perry&rsquo;s claims of hostile work environment and retaliation have now been dismissed on summary judgment.</p>
<p>The case, <a href="http://scholar.google.com/scholar_case?case=15140979480264377114&amp;hl=en&amp;as_sdt=2&amp;as_vis=1&amp;oi=scholarr">Perry v. Gotbaum</a>, was the third lawsuit brought by Perry against the PBGC and centered around Perry&rsquo;s allegations that the PBGC discriminated and retaliated against him based upon a Settlement Agreement entered into by the parties to settle the first two lawsuits. As required under the Settlement Agreement, the PBGC provided Perry with a grade and step increase in salary, paid for $10,000 worth of training, paid Perry a lump sum of $60,000, and placed him on Leave Without Pay (&ldquo;LWOP&rdquo;) Status for a time-period not to exceed six months. In addition to proving Perry with a salary increase and training, it appears that the impetus behind the Settlement Agreement was to provide Perry with an opportunity to find employment outside of the PBGC and give him a lump sum payment during his job search. Per federal government regulations, the personnel actions required under the Settlement Agreement had to be documented using a federal government <a href="http://www.opm.gov/forms/pdfimage/sf50.pdf">Standard Form 50</a> (&ldquo;SF-50&rdquo;).&nbsp;</p>
<p>In his third lawsuit, Perry complained, inter alia, that the comments section of the SF-50 forms used to process the personnel actions included information referencing his prior lawsuits and the Settlement Agreement. According to Perry, such comments would have a chilling effect on his ability to seek employment outside of the PBGC because it would be clear that he had engaged in protected activity. Further, Perry complained that the PBGC had used a more generic code when processing SF-50 forms for other employees, and therefore he should have been afforded the same treatment.&nbsp;</p>
<p>While the Court agreed with Perry that he engaged in protected activity regarding his prior lawsuits and the resulting Settlement Agreement, the Court ruled in favor of the PBGC finding that the Agency actually went back and corrected the SF-50 forms to respond to Perry&rsquo;s concerns about the remarks placed on the forms. Further, since the Settlement Agreement was not confidential and had been filed with the Court, it was a public record and Perry could not base his claims of a retaliatory and/or discriminatory disclosure upon information that was generally available to the public. In addition,<em> the Court found that there was no basis to find the PBGC&rsquo;s &ldquo;honest mistake&rdquo; was an attempt to hamper Perry&rsquo;s future job opportunities since it was in the Agency&rsquo;s interest to have Perry find employment outside of the PBGC as soon as possible</em>. As such, the Court dismissed Perry&rsquo;s federal employment discrimination and retaliation claims.</p>
<p>It should be noted that the legal standard applied by the Court in this public sector case applies to private sector Virginia businesses as well.</p>
<p>&nbsp;</p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2011/03/articles/employment-law-1/federal-employees-discrimination-retaliation-claims-dismissed/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2011/03/articles/employment-law-1/federal-employees-discrimination-retaliation-claims-dismissed/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/articles">Employment Law</category><category domain="http://www.virginiabusinesslawupdate.com/tags">discrimination</category><category domain="http://www.virginiabusinesslawupdate.com/tags">retaliation</category>
         <pubDate>Mon, 28 Mar 2011 11:35:37 -0500</pubDate>
         <dc:creator>Malik Cutlar</dc:creator>
      
      </item>
            <item>
         <title>Fourth Circuit Court of Appeals:  Employer May be Liable for Harassment by Customer</title>
         <description><![CDATA[<p>In an unpublished decision, the <a href="http://www.ca4.uscourts.gov/">Fourth Circuit Court Appeals</a> recently held that an employer may be liable for third-party harassment by a customer if the employer knew or should have known of the harassment and failed to take appropriate actions to halt it.  The evidence of repeated complaints to supervisors and managers by the employee created a triable issue as to whether the employer had notice of the harassment, and thus, the Appeals Court allowed this claim to go forward to trial.</p>
<p>In <a href="http://pacer.ca4.uscourts.gov/opinion.pdf/101476.U.pdf"><em>EEOC v. Cromer Food Services, Incorporated</em></a>, a route driver for a <a href="http://www.cfsvending.com/default.asp">southeastern vending machine company</a> alleged he suffered daily sexual harassment at the hands of two housekeeper employees of one of the company&rsquo;s largest customers &ndash; a hospital.  According to the driver, the harassment began after a co-worker left a note in the hospital cafeteria calling him gay.  Following this incident, the two male hospital employees allegedly began harassing him with unwanted sexual comments.</p>
<p>The driver claims he complained to numerous people at CFS, including his supervisor, his direct supervisor, another supervisor, a manager of the company, and the chairman of the Board.  As the harassment continued, he took more drastic measures by reporting the harassment directly to a human resources professional at the hospital and to the supervisor of the two hospital employees.  But, the hospital employees were unrelenting.</p>
<p>In response to this lawsuit, the company asserted that it did not have actual or constructive knowledge of the harassment because the complaints by the driver were vague and insufficiently detailed for action to be taken.  In addition, the company pointed out that the employee failed to report the harassment to its President in accordance with the company&rsquo;s written sexual harassment protocol.</p>
<p>The Fourth Circuit reversed the trial court&rsquo;s dismissal of the claim.  In doing so, it noted that the District Court focused on only one snippet of the driver&rsquo;s deposition testimony which stated that he did not provide details of the harassment to the company.  The Appeals Court acknowledged that although anti-harassment law requires notice to the employer &ndash; it should not require it to be pellucid.</p>
<p>The Fourth Circuit also pointed out the flaws in the employer&rsquo;s approach in this matter.  The Court stated that harassment claims could not be avoided by utilizing a &ldquo;see no evil, hear no evil&rdquo; strategy, and it criticized the protocol requiring reports to be made to the President by recognizing that such requirement may likely intimate an employee.  Moreover, the Court drew attention to the fact that management failed to report the harassment up the chain of command as required by company policy.</p>
<p><strong>This case illustrates to employers within the Fourth Circuit (which includes Virginia, Maryland,&nbsp; North Carolina, West Virginia and South Carolina) that a company&rsquo;s written policy for reporting harassment may not provide insulation from liability under Title VII.  Virginia businesses must ensure that they have a reasonable process in place to address allegations of harassment by its employees and third parties.</strong><br />
&nbsp;</p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2011/03/articles/litigation/virginia-litigation/fourth-circuit-court-of-appeals-employer-may-be-liable-for-harassment-by-customer/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2011/03/articles/litigation/virginia-litigation/fourth-circuit-court-of-appeals-employer-may-be-liable-for-harassment-by-customer/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/tags">EEOC</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Employment Law</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Fourth Circuit</category><category domain="http://www.virginiabusinesslawupdate.com/articles/litigation">Virginia Litigation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">sexual harassment</category>
         <pubDate>Thu, 17 Mar 2011 11:23:58 -0500</pubDate>
         <dc:creator>Angela France </dc:creator>
      
      </item>
            <item>
         <title>Alexandria Federal Court Transfers Venue to California in Patent Infringement Suit</title>
         <description><![CDATA[<p>Plaintiff&rsquo;s attempt to litigate in the <a href="http://www.vaed.uscourts.gov/">Rocket Docket</a> because it desired a &quot;quick, efficient and consistent resolution of its claims&quot; was recently thwarted.  In an opinion from late January, the <a href="http://www.vaed.uscourts.gov/">United States District Court for the Eastern District of Virginia Federal Court</a> (commonly referred to as the &ldquo;Rocket Docket&rdquo;) transferred venue in a patent infringement case to California because it found the plaintiff patent holding company&rsquo;s connection to this district was tenuous.</p>
<p>Pursuant to the <a href="http://www.law.cornell.edu/uscode/28/1400.shtml">patent venue statute</a>, patent infringement lawsuits may be brought against a defendant anywhere that the company is subject to personal jurisdiction.  The purpose of venue statutes is to provide a logical and efficient forum for the resolution of disputes, but the patent venue statute provides plaintiffs with a great deal flexibility in choosing where to litigate.</p>
<p>The case of <a href="http://www.virginiaiplaw.com/uploads/file/PragmatusvFacebook_VenueTransferOp.pdf"><em>Pragmatus AV, LLC v. Facebook, Inc., YouTube LLC, LinkedIn Corporation, and Photobucket.com Inc.</em></a> involves three patents related to the storage, distribution, and playback of media files.  The plaintiff company, Pragmatus, is a patent holding company that was incorporated in Virginia a week after it acquired the patent portfolio at issue.  A few days after the last patent was issued by the <a href="http://www.uspto.gov/">United States Patent and Trademark Office</a>, Pragmatus filed suit alleging the video uploading and linking technology on the defendant companies&rsquo; websites infringed on its patents.</p>
<p>The Alexandria Federal Court considered the convenience of the parties, and the witness convenience and access in determining to transfer venue to California.  In analyzing this issue, the Court noted that the inventors of the patents and attorney who prosecuted the applications are located in California; and three of the four defendants are headquartered in California, and the other defendant has offices in Denver and San Francisco.  The Court determined that these factors weighed in favor of transferring venue to California.</p>
<p><strong>The Rocket Docket is an attractive forum for business litigation due to its efficiency &ndash; continuances are rare; weekly motions; relatively short discovery period; and trials within eight months from filing.  </strong>However, a party must be able to prove a legitimate connection to the forum in order to maintain suit in this Court.   As this case illustrates, patent holding companies raise a particular concern in this regard since their business is most often limited to enforcement of IP rights &ndash; not invention or development of the technology at issue.<br />
&nbsp;</p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2011/02/articles/litigation/virginia-litigation/alexandria-federal-court-transfers-venue-to-california-in-patent-infringement-suit/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2011/02/articles/litigation/virginia-litigation/alexandria-federal-court-transfers-venue-to-california-in-patent-infringement-suit/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/articles">Intellectual Property</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Rocket Docket</category><category domain="http://www.virginiabusinesslawupdate.com/articles/litigation">Virginia Litigation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">forum shopping</category><category domain="http://www.virginiabusinesslawupdate.com/tags">patent infringement</category><category domain="http://www.virginiabusinesslawupdate.com/tags">venue</category>
         <pubDate>Fri, 18 Feb 2011 15:06:29 -0500</pubDate>
         <dc:creator>Angela France </dc:creator>
      
      </item>
            <item>
         <title>US Supreme Court: Title VII's Antiretaliation Provision Covers Third Parties</title>
         <description><![CDATA[<p>In a unanimous recent opinion, the <a href="http://www.supremecourt.gov/">United States Supreme Court</a> broadly construed the term &ldquo;person aggrieved&rdquo; in Title VII's antiretaliation provision to include a co-worker who is a relative or close associate of a targeted employee.</p>
<p>In the case of <a href="http://www.supremecourt.gov/opinions/10pdf/09-291.pdf"><em>Thompson v. North American Stainless, LP</em></a>, Plaintiff Thompson worked as a metallurgic engineer for <a href="http://www.northamericanstainless.com/">North American Stainless</a> (&ldquo;NAS&rdquo;), the owner and operator of a stainless steel manufacturing facility in Kentucky. Thompson began dating a coworker, and thereafter they became engaged to be married. According to the lawsuit, the couple&rsquo;s engagement was common knowledge at the facility. Three weeks after the <a href="http://www.eeoc.gov/">Equal Employment Opportunity Commission</a> notified NAS that Thompson&rsquo;s fianc&eacute;e had filed a discrimination charge, NAS fired Thompson.&nbsp; Thompson pursued a retaliation claim against NAS for his discharge.</p>
<p>NAS moved for dismissal of the case before trial, contending that Thompson&rsquo;s claim of third-party retaliation under Title VII was insufficient as a matter of law. The trial court granted NAS&rsquo;s motion for summary judgment, which decision was affirmed by the <a href="http://www.ca6.uscourts.gov/internet/index.htm">Sixth Circuit Court of Appeals</a>. In denying Thompson a trial, the Sixth Circuit joined several other appeals courts in holding that the authorized class of claimants under <a href="http://www.eeoc.gov/laws/statutes/titlevii.cfm">Title VII</a>&rsquo;s antiretaliation provision is limited to persons who have personally engaged in protected activity.</p>
<p>The Supreme Court disagreed, and rejected this narrow interpretation of aggrieved persons under the law. However, it declined to expand the provision into the outer boundaries of the standing standard set forth in Article III of the Constitution &ndash; which would allow anyone who claimed an injury by a Title VII violation to sue. The Court noted that such expansive interpretation would allow a shareholder to sue a company for firing a valuable employee for racial discriminatory reasons if he showed a decrease in his stock value as a consequence.</p>
<p>In settling on the middle ground, the Supreme Court stated that &ldquo;Title VII&rsquo;s antiretaliation provision must be construed to cover a broad range of employer conduct.&rdquo; The Court&rsquo;s concern was to prohibit employer action that would dissuade a reasonable employee from asserting or supporting a discrimination claim. Thompson fell within the zone of interests protected by the law.</p>
<p><strong><em>Employment Pointer</em>: This decision clears up the ambiguity over whether third parties have standing to sue for retaliation under Title VII.  Although, the Court noted that there is no bright line test for who is protected. Given the broader scope of persons to be protected under this law, companies must be aware of its management&rsquo;s underlying reasons for adverse employment actions and ensure that indirect revenge against an employee for filing a discrimination charge has not been a contributing factor. </strong></p>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2011/02/articles/employment-law-1/us-supreme-court-title-viis-antiretaliation-provision-covers-third-parties/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2011/02/articles/employment-law-1/us-supreme-court-title-viis-antiretaliation-provision-covers-third-parties/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/articles">Employment Law</category><category domain="http://www.virginiabusinesslawupdate.com/articles">Litigation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Title VII</category><category domain="http://www.virginiabusinesslawupdate.com/tags">US Supreme Court</category><category domain="http://www.virginiabusinesslawupdate.com/tags">retaliation</category>
         <pubDate>Fri, 11 Feb 2011 17:00:04 -0500</pubDate>
         <dc:creator>Angela France </dc:creator>
      
      </item>
            <item>
         <title>Virginia Federal Court: 'Twiqbal' Standard Doesn't Apply To Affirmative Defenses</title>
         <description><![CDATA[<p>&nbsp;An <a href="http://www.vaed.uscourts.gov/locations/ale.htm">Alexandria, Virginia federal court</a> judge has held that the heightened pleading requirements under the so-called &lsquo;Twiqbal&rsquo; cases do not apply to affirmative defenses.</p>
<div>&nbsp;</div>
<div>In a <a href="http://valawyersweekly.com/wp-files/pdf/011-3-038.pdf">recent failure to pay overtime case under the Fair Labor Standards Act</a>, Senior U.S. District Court Judge James C. Cacheris held that the <strong>defendant employer&rsquo;s general, boilerplate affirmative defenses were sufficient under the federal rules as they provided the plaintiff employee with fair notice of the nature of the defense</strong>.&nbsp;</div>
<div>&nbsp;</div>
<div>Judge Cacheris&rsquo; ruling marks a striking departure from the rulings of a majority of the other federal district courts in the Fourth Circuit (comprised of federal courts in Maryland, North Carolina, South Carolina, Virginia, and West Virginia), which had each previously held that the &lsquo;Twiqbal&rsquo; standard should apply equally to a plaintiff&rsquo;s complaint and a defendant&rsquo;s defenses. (Under the &lsquo;Twiqbal&rsquo; standard, which was borne out of the cases of <em>Bell Atlantic v. Twombly</em> and <em>Ashcroft v. Iqb</em><em>al</em>, the U.S. Supreme Court held that a plaintiff&rsquo;s complaint must be based on more than just &ldquo;threadbare recitals&rdquo; to survive a motion to dismiss; instead, a plaintiff&rsquo;s complaint must contain sufficient facts to give rise to a plausible entitlement to relief.)</div>
<div>&nbsp;</div>
<div>While acknowledging that policy considerations such as &ldquo;fairness, common sense, and litigation efficiency&rdquo; are &ldquo;compelling,&rdquo; Judge Cacheris opined that, unlike the federal rules which govern the pleading requirements for a plaintiff&rsquo;s claims for relief, the federal rules which govern a defendant&rsquo;s affirmative defenses merely require a responding party to &ldquo;state in short and plain terms its defenses to each claim asserted against it.&rdquo;</div>
<div>&nbsp;</div>
<div>Until the Fourth Circuit chimes in on this issue, plaintiffs and defendants alike will continue to litigate whether Twiqbal applies to affirmative defenses. <strong>Until then, defendants (especially those appearing in a Virginia federal court) can use Judge Cacheris&rsquo; opinion as authority in support of their position.</strong>&nbsp;</div>
<div>&nbsp;</div>]]></description>
         <link>http://www.virginiabusinesslawupdate.com/2011/01/articles/litigation/virginia-litigation/virginia-federal-court-twiqbal-standard-doesnt-apply-to-affirmative-defenses/</link>
         <guid isPermaLink="false">http://www.virginiabusinesslawupdate.com/2011/01/articles/litigation/virginia-litigation/virginia-federal-court-twiqbal-standard-doesnt-apply-to-affirmative-defenses/</guid>
         <category domain="http://www.virginiabusinesslawupdate.com/tags">Alexandria federal court</category><category domain="http://www.virginiabusinesslawupdate.com/tags">Twiqbal</category><category domain="http://www.virginiabusinesslawupdate.com/articles/litigation">Virginia Litigation</category><category domain="http://www.virginiabusinesslawupdate.com/tags">affirmative defense</category><category domain="http://www.virginiabusinesslawupdate.com/tags">defendant</category><category domain="http://www.virginiabusinesslawupdate.com/tags">federal rules</category><category domain="http://www.virginiabusinesslawupdate.com/tags">pleading'</category><category domain="http://www.virginiabusinesslawupdate.com/tags">s</category>
         <pubDate>Wed, 26 Jan 2011 12:45:38 -0500</pubDate>
         <dc:creator>H. Scott Johnson, Jr.</dc:creator>
      
      </item>
      
   </channel>
</rss>

