<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>HHR New Media, Entertainment and Technology Group &#187; Dan Schnapp and Wayne Josel</title>
	<atom:link href="http://digitalhhr.com/author/dan-and-wayne/feed/" rel="self" type="application/rss+xml" />
	<link>http://digitalhhr.com</link>
	<description>An online community</description>
	<lastBuildDate>Fri, 03 Feb 2012 19:52:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
		<item>
		<title>Did Facebook look before it leaped with its Usernames program?</title>
		<link>http://digitalhhr.com/2009/08/did-facebook-look-before-it-leaped-with-its-usernames-program/</link>
		<comments>http://digitalhhr.com/2009/08/did-facebook-look-before-it-leaped-with-its-usernames-program/#comments</comments>
		<pubDate>Tue, 04 Aug 2009 19:20:09 +0000</pubDate>
		<dc:creator>Dan Schnapp and Wayne Josel</dc:creator>
				<category><![CDATA[Intellectual Property]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[Litigation]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Infringement]]></category>
		<category><![CDATA[Usernames]]></category>

		<guid isPermaLink="false">http://digitalhhr.com/?p=1274</guid>
		<description><![CDATA[Since Facebook launched its Facebook Usernames initiative in mid-June, over 6 million unique individuals have registered usernames for their personal profiles, and over 15,000 usernames have been registered for Facebook Pages as well, which are commonly used by businesses and other organizations.  In many ways, the program looks like a proprietary domain name registration system.  [...]]]></description>
			<content:encoded><![CDATA[<p>Since Facebook launched its Facebook Usernames initiative in mid-June, over 6 million unique individuals have registered usernames for their personal profiles, and over 15,000 usernames have been registered for Facebook Pages as well, which are commonly used by businesses and other organizations.  In many ways, the program looks like a proprietary domain name registration system.  However, when we read that <a title="Facebook user names leave their cyber mark - SF Gate" href="http://www.sfgate.com/cgi-bin/article.cgi?f=/c/a/2009/06/16/BU5Q187SL0.DTL" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.sfgate.com/cgi-bin/article.cgi?f=/c/a/2009/06/16/BU5Q187SL0.DTL&amp;referer=');">Facebook is claiming ownership over every username</a>, an assertion attributed to a company spokesman, we realized that Facebook is not acting like a domain name registrar.  We also wondered about the legal basis of such a claim.</p>
<p><span id="more-1274"></span>The program enables individuals and companies to register a Facebook URL with an address format of www.facebook.com/[username].  Applicant for usernames are generally allowed to choose them freely, without need to prove any connection or ownership to the name itself.  This wide-open nature raises potential concerns for intellectual property rights holders, particularly trademark owners, worried about unauthorized use of their trademarks in connection with the service. </p>
<p>Facebook has sought to maintain as much of control over the usernames as possible, including the right to<a title="Facebook - Usernames: General Information" href="http://www.facebook.com/help.php?page=897" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.facebook.com/help.php?page=897&amp;referer=');"> remove or reclaim a username at any time</a> for any reason.  This strong proactive stance is probably partially motivated by a desire to preempt and prevent widespread buying or selling of usernames, and the cyber-squatting practices that follow.  (Such concerns are not unfounded; Facebook usernames are already up for sale on <a title="Assetize: Buy and sell Twitter, Gmail and other online accounts" href="http://www.assetize.com/" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.assetize.com/?referer=');">Assetize</a>, an online website specializing in the buying and selling of online accounts.)</p>
<p>But back to the ownership issue&#8211;Can Facebook actually &#8220;own&#8221; a username that contains a registered and widely used trademark owned by someone else?  And if Facebook &#8220;owns&#8221; the username, what happens when a trademark owner seeks to register the username containing its mark?  Is &#8220;ownership&#8221; (<em>i.e</em>., title) to the username conveyed?  Or does Facebook license the username?  Take for example the username &#8220;facebook.com/burgerking&#8221;.  As of the date of this posting, Burger King <a title="Facebook.com/burgerking" href="http://www.facebook.com/burgerking" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.facebook.com/burgerking?referer=');">has not yet registered the username</a>, but if it does choose to register it, is it accurate to say that Facebook is transferring ownership over the username to Burger King?  Or is it licensing it?  Either way, how can Facebook transfer to Burger King something Burger King already owns?</p>
<p>Also, Facebook claims that when a Facebook account is cancelled, that account&#8217;s username <a href="http://www.facebook.com/help.php?page=897" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.facebook.com/help.php?page=897&amp;referer=');">will not become available to anyone else</a>.  If Burger King registers for the user name, and then cancels it, can Facebook prevent Burger King from re-registering the user name if it later changes its mind?  In the end it is not clear or likely that Facebook can legitimately assert power over trademark holders when it comes to the use of their trademarks in the Usernames program. </p>
<p>Facebook&#8217;s <a title="Facebook - Statement of Rights and Responsibilities" href="http://www.facebook.com/terms.php?ref=pf" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.facebook.com/terms.php?ref=pf&amp;referer=');">terms of service</a> do not help to clarify the matter.  They make no mention of the Usernames program.  On the other hand, Facebook&#8217;s &#8220;<a title="Facebook - Help Center" href="http://www.facebook.com/help.php?ref=pf" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.facebook.com/help.php?ref=pf&amp;referer=');">Help Center</a>&#8221; does have a section devoted to answering common questions about the program.  When the program was launched, the Help Center materials contained a few scant paragraphs of information.  Since that time, it has become <a title="Facebook - Usernames" href="http://www.facebook.com/help.php?topic=username" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.facebook.com/help.php?topic=username&amp;referer=');">much more developed</a>, but that initial lack of clarity exemplifies the legal ambiguity with which the initiative got off the ground.  The uncertainties surrounding the Usernames program may be of particular concern for businesses in light of their increasing reliance on Facebook as an avenue through which to connect with customers (and concerns about businesses&#8217; dependence on Facebook <span style="text-decoration: underline;">are not new</span>).</p>
<p>We will eventually see if Facebook&#8217;s experience with the Usernames program proves a cautionary tale as to the pitfalls of rolling out new programs without fully anticipating the potential legal issues.  As the Username feature develops and more companies become aware of it, Facebook may see both disputes and angry markholders multiply. </p>
<p>This may turn into yet another cyber-battleground over trademarks.  Numerous trademark infringement claims have been brought against Google in connection with its search ad business.  The claims are based on Google&#8217;s sale of trademarked keywords through its AdWords program.  In large part, the plaintiffs have asserted that such sales constitute trademark infringement because consumers could be confused by links to competitors&#8217; ads that pop up alongside a search for the plaintiff&#8217;s marks.  While Google suffered a litigation setback in April when <a title="Trademark Protection in Cyberspace Rescued - Law.com" href="http://www.law.com/jsp/legaltechnology/pubArticleLT.jsp?id=1202429833898" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.law.com/jsp/legaltechnology/pubArticleLT.jsp?id=1202429833898&amp;referer=');">the Second Circuit reversed a dismissal of a suit brought by Rescuecom Corp.</a>, two separate <a title="Google Rebounds in AdWords Lawsuits - law.com" href="http://www.law.com/jsp/article.jsp?id=1202432752160&amp;Google_Rebounds_in_AdWords_Lawsuits&amp;hbxlogin=1" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.law.com/jsp/article.jsp?id=1202432752160_amp_Google_Rebounds_in_AdWords_Lawsuits_amp_hbxlogin=1&amp;referer=');">actions against Google, one by Daniel Jurin and the other by Ascentive LLC, were both recently dismissed</a>.</p>
<p>We will continue to monitor these matters and keep an eye out for developments.  In the meantime, our group would be happy to discuss any specific questions you might have about the impact of Facebook&#8217;s Usernames program on your trademark portfolio and help you develop strategies to protect your intellectual property rights.</p>
<p>*  We would like to thank Yoshinori Sasao, a summer associate at the Firm, who assisted in preparing this article.</p>
]]></content:encoded>
			<wfw:commentRss>http://digitalhhr.com/2009/08/did-facebook-look-before-it-leaped-with-its-usernames-program/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Licensing Rights in Jointly-Owned Copyrights-You Can’t Always Get What You Want</title>
		<link>http://digitalhhr.com/2009/07/licensing-rights-in-jointly-owned-copyrights-you-can%e2%80%99t-always-get-what-you-want/</link>
		<comments>http://digitalhhr.com/2009/07/licensing-rights-in-jointly-owned-copyrights-you-can%e2%80%99t-always-get-what-you-want/#comments</comments>
		<pubDate>Tue, 21 Jul 2009 20:35:52 +0000</pubDate>
		<dc:creator>Dan Schnapp and Wayne Josel</dc:creator>
				<category><![CDATA[Intellectual Property]]></category>
		<category><![CDATA[Litigation]]></category>
		<category><![CDATA[copyright]]></category>
		<category><![CDATA[joint ownership]]></category>
		<category><![CDATA[licensing]]></category>

		<guid isPermaLink="false">http://digitalhhr.com/?p=1266</guid>
		<description><![CDATA[Joint ownership of copyrights is a tricky issue in any transaction.  It is one confronted regularly in digital media deals where rights in the underlying content are often owned by more than one person and licenses are granted retroactively.  Recent decisions in the Second and Ninth Circuit Court of Appeals have caused tremendous concern about [...]]]></description>
			<content:encoded><![CDATA[<p>Joint ownership of copyrights is a tricky issue in any transaction.  It is one confronted regularly in digital media deals where rights in the underlying content are often owned by more than one person and licenses are granted retroactively.  Recent decisions in the Second and Ninth Circuit Court of Appeals have caused tremendous concern about the eroding rights of copyright co-owners.  In <a title="Davis v. Blige, et al., Second Circuit Court of Appeals" href="http://digitalhhr.com/wp-content/uploads/2009/07/davis-v-blige-2nd-cir.pdf" target="_blank"><em>Davis v. Blige</em>, the Second Circuit held that copyright co-owners cannot unilaterally issue retroactive licenses</a>.  And in <a title="Sybersound Records, Inc. v. UAV Corp., et al, Ninth Circuit Court of Appeals" href="http://digitalhhr.com/wp-content/uploads/2009/07/sybersound-v-uav-corp-9th-cir.pdf" target="_blank"><em>Sybersound v. UAV Corp.,</em> , the Ninth Circuit held that a copyright co-owner cannot grant an exclusive license without the consent of all the other co-owners</a>.  The combined effect of these decisions has been described as the &#8220;<a title="The Death of Divisibility - The Patry Copyright Blog" href="http://williampatry.blogspot.com/2008/02/death-of-divisibility.html" target="_blank" onclick="pageTracker._trackPageview('/outgoing/williampatry.blogspot.com/2008/02/death-of-divisibility.html?referer=');">death of divisibility</a>&#8221; in copyright law.  These decisions threaten to pose considerable difficulties for anyone looking to acquire rights in a copyright that is owned by more than one individual.    <span id="more-1266"></span></p>
<p>The question of <a title="Comment, Unilateral Settlements and Retroactive Transfers: A Problem of Copyright Co-Ownership, James K. Rothstein, U. Penn. Law Rev." href="http://www.pennumbra.com/issues/pdfs/157-3/Rothstein.pdf" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.pennumbra.com/issues/pdfs/157-3/Rothstein.pdf?referer=');">retroactive licensing has been considered in a number of district court cases</a>, however, <em>Davis</em>was the first time the issue had been considered by an appellate court.  The case centered around two songs written by Mary J. Blige, Bruce Miller and others, all of whom were defendants in the case.  The plaintiff, Sharice Davis, claimed that Blige&#8217;s songs infringed her copyright in two songs she co-authored with Bruce Chambliss, the step-father of Blige and father of Miller.  Miller however, claimed that Chambliss, who was not a party to the case, wrote the disputed compositions on his own and orally agreed to give all rights in the music to Miller.  However, the crux of the case turned on a written agreement between Miller and Chambliss, created two days before Chambliss&#8217; first deposition.  The agreement purported to retroactively transfer all rights in Chambliss&#8217; works to Miller from the date of their composition.  This would make Miller a co-owner in the two disputed compositions and validate the licenses he gave to Blige to use the works.  If the Court of Appeals had upheld the agreement, as the District Court did, Davis would have lost all of her claims for past infringement against the other defendants. </p>
<p>The Second Circuit overturned the District Court decision, holding that a co-author cannot immunize a third party for past infringements by retroactively issuing a license for the infringed work.  To support its decision, the Court of Appeals used the property theory of joint tenancy as a model for the rights of copyright co-owners.  Each copyright co-owner had independent rights to use and license the work, subject only to a duty to account to the other co-owners for any profits that are made.  A co-owner can only convey as much as he possesses and cannot, therefore, transfer or assign the rights of other co-owners.  The court held that a retroactive transfer would effectively allow a co-owner to assign away another co-owner&#8217;s right to sue for accrued infringements.  While Chambliss could release Miller and the others from liability from him for past infringements, he could not transfer or assign any rights Davis had against the defendants for accrued causes of action. </p>
<p>By holding that licenses can only be issued prospectively, the court drew a line between a co-owners right to sue for past and future infringements.  A copyright co-owner can unilaterally issue a non-exclusive license which prevents a co-owner from suing the licensee for any future use.  However, a co-owner cannot issue a retroactive license that would prevent a co-owner from suing for infringements that have already occurred.  This holding, the court believed, provides certainty for co-owners dealing with infringement actions and discourages infringement by ensuring that retroactive licenses aren&#8217;t used to lower the cost of infringement.   </p>
<p>In <em>Sybersound</em>, the Ninth Circuit dealt with the question of a co-owner&#8217;s right to license their copyright from a different perspective.  Where <em>Davis</em> dealt whether a co-owner could unilaterally issue a retroactive license in order to cure past infringements, the question in <em>Sybersound </em>was whether a co-owner can unilaterally grant an exclusive license that gives the licensee co-ownership in the copyright. </p>
<p>Sybersound had brought claims of infringement against five of its competitors in the karaoke industry for allegedly infringing Sybersound&#8217;s copyrights in nine songs.  Sybersound had acquired its rights in these songs by way of agreement with TVT, a co-owner the copyrights along with other publishing companies.  The agreement stated that TVT was making Sybersound the &#8220;exclusive assignee of TVT&#8217;s copyrighted karaoke use interest and of TVT&#8217;s right to sue,&#8221; purportedly making Sybersound a co-owner in the copyright.  The Ninth Circuit held that the agreement was invalid because TVT could not exclusively assign what it did not exclusively possess.  TVT was only a co-owner of the copyright, and therefore, &#8220;as a co-owner of the copyright, TVT could not grant an exclusive right interest.&#8221;  For Sybersonic to acquire an exclusive license, each of the co-owners of the copyright would have to agree to the transfer.  Since TVT could only unilaterally grant a non-exclusive license, Sybersonic did not have standing to sue and the infringement claims were dismissed.    </p>
<p>It had <a title="Comment, Unilateral Settlements and Retroactive Transfers: A Problem of Copyright Co-Ownership, James K. Rothstein, U. Penn. Law Rev." href="http://www.pennumbra.com/issues/pdfs/157-3/Rothstein.pdf." target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.pennumbra.com/issues/pdfs/157-3/Rothstein.pdf.?referer=');">been a common practice in the media industry</a> to obtain licenses after the fact.  However, after <em>Davis, </em>that practice has become much more uncertain.  The <em>Sybersound</em> decision might have a dampening effect on similar transactions as it seemingly makes it impossible for a copyright co-owner to grant an exclusive license of his proportional share in a copyright without the consent of his fellow co-owners.   </p>
<p>Left undiscussed in these decisions was the issue of the representations made by the co-owner of the copyrights in the underlying license agreements.  One can assume that the licensees sought and obtained a representation that the licensors had the authority to grant the underlying rights and that use by the licensee of the copyrighted works would not infringe or violate any third party&#8217;s rights.  Obviously these rulings have rendered those representations false, exposing the co-owners to potential claims under the license agreements, including claims for indemnification.</p>
<p>In confronting the commercial landscape created by these rulings, it is critical for licensees to carefully consider the rights they are obtaining in copyrighted works with multiple owners, particularly when rights are being granted on a retroactive or exclusive basis, to ensure that they will be able to exploit the rights as intended.  For copyright co-owners, it is important that any representations they make be tailored to reflect their limitations on the rights they can grant so that they are not promising more than they can deliver.</p>
<p>Our New Media, Entertainment and Technology practice group has extensive experience assisting our clients in understanding and analyzing the impact of new developments in the law on the design, development, implementation and operation of their respective business initiatives across all new media platforms, and we will continue to stay apprised of and routinely report on further developments in the treatment of co-ownership by the courts in this regard.     </p>
<p>* We would like to thank Kate O&#8217;Donnell, a Summer Associate at the Firm, for her assistance in preparing this article.</p>
]]></content:encoded>
			<wfw:commentRss>http://digitalhhr.com/2009/07/licensing-rights-in-jointly-owned-copyrights-you-can%e2%80%99t-always-get-what-you-want/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Deadline for Safe Harbor Certification under Anti-Child Pornography Regs Fast Approaching</title>
		<link>http://digitalhhr.com/2009/06/deadline-for-safe-harbor-certification-under-anti-child-pornography-regs-fast-approaching/</link>
		<comments>http://digitalhhr.com/2009/06/deadline-for-safe-harbor-certification-under-anti-child-pornography-regs-fast-approaching/#comments</comments>
		<pubDate>Tue, 09 Jun 2009 17:14:56 +0000</pubDate>
		<dc:creator>Dan Schnapp and Wayne Josel</dc:creator>
				<category><![CDATA[E-alert]]></category>
		<category><![CDATA[Regulations]]></category>
		<category><![CDATA[certification]]></category>
		<category><![CDATA[Child Protection and Obscenity Enforcement Act]]></category>
		<category><![CDATA[online child safety]]></category>
		<category><![CDATA[safe harbor]]></category>

		<guid isPermaLink="false">http://digitalhhr.com/?p=1001</guid>
		<description><![CDATA[For years, the adult entertainment industry has been required to maintain records verifying the age of all performers.  However earlier this year, new regulations implementing § 2257 and § 2257(A) of the Child Protection and Obscenity Enforcement Act went into effect which impose similar record keeping requirements on many mainstream media companies.  However, the regulations [...]]]></description>
			<content:encoded><![CDATA[<p>For years, the adult entertainment industry has been required to maintain records verifying the age of all performers.  However earlier this year, new regulations implementing <a title="18 USC 2257, Record Keeping Requirements" href="http://www.law.cornell.edu/uscode/18/usc_sec_18_00002257----000-.html" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.law.cornell.edu/uscode/18/usc_sec_18_00002257----000-.html?referer=');">§ 2257</a> and <a title="18 USC 2257A, Record keeping requirements for simulated sexual conduct" href="http://www.law.cornell.edu/uscode/html/uscode18/usc_sec_18_00002257---A000-.html" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.law.cornell.edu/uscode/html/uscode18/usc_sec_18_00002257---A000-.html?referer=');">§ 2257(A)</a> of the <a title="Child Protection and Obscenity Enforcement Act, 18 USD 2251 et seq." href="http://www.law.cornell.edu/uscode/18/usc_sup_01_18_10_I_20_110.html" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.law.cornell.edu/uscode/18/usc_sup_01_18_10_I_20_110.html?referer=');">Child Protection and Obscenity Enforcement Act</a> went into effect which impose similar record keeping requirements on many mainstream media companies.  However, the regulations contain a &#8220;safe harbor&#8221; to help minimize the effect of the regulations by enabling mainstream media companies to file a certification with the Attorney General&#8217;s Office.  The deadline for this important certification is June 16<sup>th</sup>, 2009. <span id="more-1001"></span></p>
<p>The new DOJ regulations implement the expanded age-verification requirements enacted in the Adam Walsh Act.  Now <a title="How &quot;Swingers&quot; Might Save Hollywood from a Federal Pornography Statute - The Yale Law Journal" href="http://yalelawjournal.org/content/view/672/14/" target="_blank" onclick="pageTracker._trackPageview('/outgoing/yalelawjournal.org/content/view/672/14/?referer=');">primary and secondary producers of depictions of &#8220;simulated sexually explicit conduct&#8221; and &#8220;lascivious exhibition&#8221; must also comply</a> with age-verification record keeping requirements. The regulations define a <a title="28 CFR Sec. 75.1(c)(1) (2009)" href="http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&amp;sid=2301ae63f41142b590daafcfd91da40d&amp;rgn=div5&amp;view=text&amp;node=28:2.0.1.1.30&amp;idno=28#28:2.0.1.1.30.0.17.1" target="_blank" onclick="pageTracker._trackPageview('/outgoing/ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr_amp_sid=2301ae63f41142b590daafcfd91da40d_amp_rgn=div5_amp_view=text_amp_node=28_2.0.1.1.30_amp_idno=28_28_2.0.1.1.30.0.17.1&amp;referer=');">primary producer</a> as the individual who records the depiction of the sexually explicit conduct, whether it&#8217;s by videotape, photography, or a digitally manipulated image.  Primary producers also include anyone who digitizes an image of sexually explicit conduct.  A secondary producer includes anyone who &#8220;produces, assembles, manufactures, publishes, duplicates, reproduces, or reissues a book, magazine, periodical, videotape, or digitally or computer-manipulated image, picture, or other matter&#8221; that is intended for commercial distribution.  This definition also encompasses anyone who includes sexually explicit depictions on a computer site or service or otherwise manages the sexually explicit content on a computer site or service.  The breadth of the initial definition of secondary producer raised <a title="Media Coalition, Inc. comments to proposed regulations" href="http://www.mediacoalition.org/govt_regulation.php" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.mediacoalition.org/govt_regulation.php?referer=');">protest from the media industry</a> and it was later amended to exclude those who <a title="28 CFR Sec. 75.1(c)(4)(vi) (2009)" href="http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&amp;sid=2301ae63f41142b590daafcfd91da40d&amp;rgn=div5&amp;view=text&amp;node=28:2.0.1.1.30&amp;idno=28#28:2.0.1.1.30.0.17.1" target="_blank" onclick="pageTracker._trackPageview('/outgoing/ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr_amp_sid=2301ae63f41142b590daafcfd91da40d_amp_rgn=div5_amp_view=text_amp_node=28_2.0.1.1.30_amp_idno=28_28_2.0.1.1.30.0.17.1&amp;referer=');">merely distribute sexually explicit conduct, without altering or editing the content</a>. Simulated sexually explicit conduct includes conduct that would cause a reasonable viewer to believe that the performers were actually engaged in sexually explicit conduct.  However, the depiction must amount to more than the mere suggestion of sexually explicit conduct.  While lascivious exhibition is not defined within the regulations, the <a title="Obscenity Prosecution Task Force Section 2257 Compliance Guide - US Department of Justice" href="http://www.usdoj.gov/criminal/optf/links/2257-compliance-guide.html" target="_blank" onclick="pageTracker._trackPageview('/outgoing/www.usdoj.gov/criminal/optf/links/2257-compliance-guide.html?referer=');">DOJ website</a> describes a few components of a lascivious depiction: &#8220;(1) the focal point is on the subject&#8217;s genitalia or pubic area, (2) the setting of the visual depiction is sexually suggestive . . . (3) the visual depiction suggests sexual coyness or a willingness to engage in sexual activity; or (4) the visual depiction is intended to elicit a sexual response in the viewer.&#8221;  Under this description, producers who show only fleeting nudity might still be subject to the age-verification recording procedures. </p>
<p>The new regulations require the primary producer to examine a government issued photo ID of every performer before the production of the sexually explicit depiction.  The producer must then make a record of the performer&#8217;s name, aliases, date of birth, the date of the production of the sexually explicit image, and make a photocopy of the identification.  These records must be maintained in accordance with specific requirements and the visual depiction must be labeled with the location of the record.  A secondary producer of sexually explicit content must obtain all age-verification records from the primary producer, but does not have to independently verify the age of the performers.</p>
<p>While these requirements might have proven burdensome for mainstream media, the DOJ regulations contain an <a title="28 CFR Sec. 75.9 (2009)" href="http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&amp;sid=2301ae63f41142b590daafcfd91da40d&amp;rgn=div5&amp;view=text&amp;node=28:2.0.1.1.30&amp;idno=28#28:2.0.1.1.30.0.17.9" target="_blank" onclick="pageTracker._trackPageview('/outgoing/ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr_amp_sid=2301ae63f41142b590daafcfd91da40d_amp_rgn=div5_amp_view=text_amp_node=28_2.0.1.1.30_amp_idno=28_28_2.0.1.1.30.0.17.9&amp;referer=');">important safe harbor</a> which offsets some of this burden:  Specifically, the record keeping provisions do not apply to a producer of simulated sexual conduct or lascivious images if the images are intended for commercial distribution as part of a commercial enterprise and they meet one of two requirements: (1) if the visual depiction is not &#8220;produced, marketed, or made available in circumstances such that an ordinary person would conclude that the matter contains a visual depiction that is child pornography&#8221; or (2) the depiction is subject to regulation by the FCC in its regulation of the broadcast of obscene, indecent, or profane programming. </p>
<p>Producers seeking eligibility for the exemption must send a letter of certification to the Attorney General. The certification letter must state the statutory basis for eligibility, and, in the <a title="28 CFR 75.9(c)(2) (2009)" href="http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&amp;sid=2301ae63f41142b590daafcfd91da40d&amp;rgn=div5&amp;view=text&amp;node=28:2.0.1.1.30&amp;idno=28#28:2.0.1.1.30.0.17.9" target="_blank" onclick="pageTracker._trackPageview('/outgoing/ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr_amp_sid=2301ae63f41142b590daafcfd91da40d_amp_rgn=div5_amp_view=text_amp_node=28_2.0.1.1.30_amp_idno=28_28_2.0.1.1.30.0.17.9&amp;referer=');">required language</a>, state that the producer, in the regular course of business, collects and maintains identifying information for all performers. The letter must be signed by an executive officer of the entity or, if the entity does not have executive officers, by a senior manager who oversees the entity&#8217;s activities.  There are specific requirements <a title="28 CFR Sec. 75.9(c)(3) (2009)" href="http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&amp;sid=2301ae63f41142b590daafcfd91da40d&amp;rgn=div5&amp;view=text&amp;node=28:2.0.1.1.30&amp;idno=28#28:2.0.1.1.30.0.17.9" target="_blank" onclick="pageTracker._trackPageview('/outgoing/ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr_amp_sid=2301ae63f41142b590daafcfd91da40d_amp_rgn=div5_amp_view=text_amp_node=28_2.0.1.1.30_amp_idno=28_28_2.0.1.1.30.0.17.9&amp;referer=');">for foreign entities seeking certification</a>, or entities which have used foreign performers. </p>
<p>The deadline for submitting the certification is June 16, 2009.  For all production that begins after June 16, 2009, the certification is due within 60 days of the start of the production.   After the initial certification, there is no need to recertify unless there are any material changes to the information provided in the certification.  In that case, a subsequent certification must be filed within 60 days of the material change. </p>
<p>Our New Media, Entertainment and Technology practice group has been closely monitoring these regulations and would be happy to answer any questions regarding the impact of the same on your content production, broadcast and distribution initiatives or assist you in filing your own certification letters. </p>
<p><em>We would like to thank Kate O&#8217;Donnell, a summer associate with the Firm, for her assistance in the preparation of this alert.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://digitalhhr.com/2009/06/deadline-for-safe-harbor-certification-under-anti-child-pornography-regs-fast-approaching/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Protecting Mobile Content Providers Against Improper Billing Practices of Third Parties</title>
		<link>http://digitalhhr.com/2008/01/pending-class-action-points-to-potential-pitfalls-for-mobile-digital-content-providers/</link>
		<comments>http://digitalhhr.com/2008/01/pending-class-action-points-to-potential-pitfalls-for-mobile-digital-content-providers/#comments</comments>
		<pubDate>Tue, 15 Jan 2008 16:22:31 +0000</pubDate>
		<dc:creator>Dan Schnapp and Wayne Josel</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[E-alert]]></category>
		<category><![CDATA[Mobile]]></category>

		<guid isPermaLink="false">http://digitalhhr.webair.com/?p=140</guid>
		<description><![CDATA[  Pending Class Action Points to Potential Pitfalls
 
While not directly involving mobile digital content provides, a class action lawsuit pending in Federal court in Massachusetts has brought into focus a practice that such providers must be aware of and protect themselves against. At issue in Knox and Esparza v. m-Qube, Inc. is &#8220;cramming&#8221; pursuant to [...]]]></description>
			<content:encoded><![CDATA[<p><strong><img class="alignnone" src="http://digitalhhr.com/wp-content/uploads/2008/09/pdficon_large.gif" alt="" width="32" height="32" />  <a href="http://digitalhhr.com/wp-content/uploads/2008/10/ealert-pending-class-action-points_jan2008doc.pdf">Pending Class Action Points to Potential Pitfalls</a></strong></p>
<p> </p>
<p>While not directly involving mobile digital content provides, a class action lawsuit pending in Federal court in Massachusetts has brought into focus a practice that such providers must be aware of and protect themselves against. At issue in <em>Knox and Esparza v. m-Qube, Inc</em>. is &#8220;cramming&#8221; pursuant to which a cellular subscriber is automatically billed for mobile content services that were not purchased.</p>
<p><span id="more-140"></span>The plaintiffs in <em>Knox</em> allege that m-Qube, a third-party provider of billing services for wireless carriers, unlawfully billed for services that the plaintiffs did not order. Specifically, the plaintiffs allege that m-Qube continued to bill for services that had been purchased by prior subscribers using their mobile phone numbers, which were &#8220;recycled&#8221; or &#8220;refurbished&#8221; after the prior subscriber terminated his or her cellular contract. The parties have briefed a motion to dismiss, on which oral argument is scheduled to be heard at the end of the month.</p>
<p>Curiously, while the complaint alleges wrongdoing on the part of the content mobile digital providers themselves (in particular, negligently failing to determine when authorization was provided for billing for the mobile content), no content providers were named as defendants. Notwithstanding that fact, the allegations of the case do provide critical guidance to mobile digital content providers when entering into agreements with wireless carriers.</p>
<p>Typically, wireless carriers and/or their third-party billing vendor(s) assume primary responsibility for obtaining authorization from subscribers to bill such subscribers for the content purchased, whether on a subscription, per-view or per-download basis, as well as for managing the billing and collections. The content provider is paid a portion of the revenue remitted by the subscriber and collected by the carrier and/or third-party vendor for the content purchased.</p>
<p>But what happens when, as in <em>Knox</em>, the subscriber claims he or she did not request the content and/or authorize being billed for it? Could the content provider be held liable under those circumstances, where it has received the economic benefit of such unauthorized transaction?</p>
<p>The law currently is unclear on this subject. However, mobile digital content providers may mitigate their risk under these circumstances by ensuring that their content license agreements with wireless carrier and mobile content aggregator partners clearly provide that the carrier or aggregator, as applicable, will indemnify the content provider for any claims that may arise as a result of such billing practices and that such partners&#8217; independently procure and maintain sufficient insurance coverage for losses incurred in connection with any such claims .</p>
<p>While an argument could be made that the indemnification provisions of many content license agreements can be broadly construed to cover such a situation (<em>e.g.</em> where the carrier must indemnify the content provider for claims arising as a result of the carrier&#8217;s wireless service generally), a better practice would be to expressly cover claims related to billing and other potential disputes that may arise between the subscriber and the carrier and/or its agents.</p>
]]></content:encoded>
			<wfw:commentRss>http://digitalhhr.com/2008/01/pending-class-action-points-to-potential-pitfalls-for-mobile-digital-content-providers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

