The Oregon Supreme Court recently reversed the Oregon Court of Appeals in Neumann v. Liles, a defamation lawsuit involving a negative review of a wedding venue. The plaintiff, an operator of the venue, was the target of a review on google.com calling her, among other things, "two faced, crooked, and . . . rude." She sued the author of the review, who had been a guest at a wedding hosted at plaintiff's venue. The Oregon Court of Appeals found that the trial court improperly granted the defendant's special motion to strike under Oregon's anti-SLAPP statute, finding that the review contained potentially defamatory statements regarding the plaintiff's honesty and business ethics.
In reversing the Oregon Court of Appeals, the Oregon Supreme Court announced a framework, adopted from the Ninth Circuit, for analyzing whether a defamatory statement is entitled to First Amendment protection. The first question is whether the statement involves a matter of public concern. If it does, then the dispositive question is whether a reasonable factfinder could conclude that the statement implies an assertion of objective fact. To answer that question, the following three-part inquiry must be applied: (1) whether the general tenor of the entire publication negates the impression that the defendant was asserting an objective fact; (2) whether the defendant used figurative or hyperbolic language that negates that impression; and (3) whether the statement in question is susceptible of being proved true or false.
Considering the content of the review as a whole, the Oregon Supreme Court held that a reasonable factfinder could not conclude that the defendant's review implied an assertion of objective fact; rather, the review expressed an opinion on matters of public concern that is protected under the First Amendment. On that basis, the Supreme Court concluded that the trial court properly dismissed the defamation lawsuit.
Earlier this month, Judge Edward M. Chen of the Northern District of California granted class action status to the plaintiffs in the on-going litigation against the popular ride-sharing app, Uber Technologies, Inc. The lawsuit was originally brought on behalf of three Uber drivers who claimed that Uber misclassified them as contract workers and improperly denied them employment-related benefits. The court's recent ruling expanded the lawsuit from three individual drivers to all Uber drivers in California, with the exception of those who executed a waiver of class action rights.
In opposition to the plaintiffs' motion for class certification, Uber argued that the drivers' employment classification cannot be adjudicated on a class-wide basis. Uber maintains that its right of control over its drivers, as well as the day-to-day reality of its relationship with them, are not sufficiently uniform across the proposed class. The court found that there was an inherent tension in Uber's argument -- on one hand, Uber claims that it has properly classified every single driver as an independent contractor, but on the other, Uber claims that each driver has a unique relationship with Uber such that the Court cannot make a class-wide determination of its drivers' proper job classification.
This high-profile decision highlights the increased scrutiny that is being placed on "sharing economy" companies that classify their workers as independent contractors rather than employees.
The decade-old Zubulake v. UBS case set off a seismic shift in electronic discovery that many lawyers and litigants still don't fully comprehend. One lesson many have learned the hard way is that the electronic discovery rules and practices that have been developed post-Zubulake must be a regular part of every organization's document management plans.
Zubulake was a standard employment discrimination lawsuit in the U.S. District Court for the Southern District of New York that is now seen as a turning point in electronic discovery. This article provides an excellent summary of Zubulake and its impact.
Increasingly, courts are disinclined to tolerate a party's failure to work cooperatively to minimize the cost of eDiscovery, as this plaintiff painfully discovered.
Give just a moment to consider your organization’s electronic document protocols. Processes should be in place long before any subpoena or request for records arrives. When your organization is hit with a lawsuit, what is the plan for preserving, requesting, organizing and producing documents?
The Litigation Technology Team at Ater Wynne manages electronic documents and eDiscovery for clients in litigation of all sizes, from small document collections with just one or two file types to large, complex sets involving terabytes of data, millions of documents, and dozens of file types. We utilize protocols and best practices developed in-house and multiple eDiscovery software platforms, keeping document management practices up-to-date and satisfying the courts' requirements.
In matters of eDiscovery, an ounce of prevention is better than a pound of cure. For more information about Ater Wynne’s Litigation Technology Team, contact Kara Lindsay, Chief Litigation Technology Specialist at email@example.com.
The Ninth Circuit Court of Appeals last week handed a trademark victory to Pom Wonderful, reversing a district court decision denying its request for an injunction against competitor Pur Beverages.
Pom Wonderful, maker of the popular POM pomegranate juice drinks, requested a preliminary injunction to bar the defendant from using the word “pŏm” for its pomegranate flavored energy drinks, as seen below.
The district court denied the request, stating that Pom Wonderful did not establish a likelihood of confusion between the marks.
On review, the Ninth Circuit focused on the Sleekcraft factors for likelihood of confusion. Regarding the physical similarities of the marks, the Ninth Circuit found far more in common between the marks than not. “Balancing the marks’ many visual similarities, perfect aural similarity, and perfect semantic similarity more heavily than the marks’ visual dissimilarities – as we must – the similarity factor weighs heavily in Pom Wonderful’s favor.” Furthermore, when considering this factor, strong marks are given greater weight than weak marks. As such, the district court clearly erred by giving more weight to the marks’ differences than their similarities.
The district court also erred in its “brick-and-mortar” trade channels analysis. “Because Pom Wonderful and Pur sell highly similar products in supermarkets located across the country, the marketing channel convergence factor weighs in Pom Wonderful’s favor. The district court clearly erred in . . . requiring Pom Wonderful to prove that its beverages were sold in the very same brick-and-mortar stores as Pur’s ‘pŏm’ beverage.” Though a perfect overlap of retailer locations increases likelihood of consumer confusion, its absence does not undermine the convergence of the marketing channels.
Finally, the district court mistakenly weighed the remaining factors – actual confusion, defendant’s intent, and product expansion –against Pom Wonderful. The absence of any evidence supporting these factors is to be considered merely neutral in a likelihood of confusion analysis.
In weighing the totality of the factors, the Ninth Circuit review revealed that five of the Sleekcraft factors weighed in favor of Pom Wonderful, none weighed in favor of Pur Beverages, and three factors were neutral. Since the district court’s errors created a ripple effect, influencing its decision regarding the remaining preliminary injunction requirements, the Ninth Circuit reversed and remanded.
The Oregon Supreme Court held last week that the attorney-client privilege applies to communications between a law firm's lawyers and the firm's in-house counsel. In Crimson Trace Corp. v. Davis Wright Tremaine LLP, plaintiff sued its lawyers for malpractice, and sought discovery of communications between the defendant lawyers and a group of firm lawyers designated as in-house counsel. Those internal communications had occurred when a potential conflict of interest arose between the client and its lawyers.
The trial court held that the communications were discoverable and were not subject to the attorney-client privilege, adopting a "fiduciary exception" to Oregon Evidence Code 503, which sets out the scope of the privilege. According to the fiduciary exception, a law firm's fiduciary obligations to its clients prevent it from invoking the privilege to protect its lawyers' communications with in-house counsel. Justice Landau, writing for the Supreme Court, concluded that the fiduciary exception is not supported by the plain language of Rule 503, and that the internal law firm communications in that case were protected by the privilege.
The Oregon Court of Appeals recently held that a business owner can pursue a defamation claim against an individual who posted a negative on-line review. In Neumann v. Liles, plaintiff, who operates a wedding venue, was the target of a review on google.com calling her, among other things, "two faced, crooked, and . . . rude." She sued the author of the review, who had been a guest at a wedding hosted at plaintiff's venue.
The on-line critic in response filed a "special motion to strike" under Oregon's SLAPP statute. SLAPP stands for "strategic lawsuit against public participation," and the anti-SLAPP statute creates a procedure for dismissing at an early stage an unfounded lawsuit designed to quash speech or activism on issues of public interest. While the statute protects certain speech-related activities, it does not shield defendants who engage in defamatory speech.
According to the Court of Appeals, the trial court should not have granted the anti-SLAPP motion to strike the complaint because plaintiff had offered sufficient evidence that the review was in fact defamatory. While defendant claimed that the review represented his opinion and was merely "figurative, rhetorical, or hyperbolic," the Court of Appeals concluded that most of the post was "nonrhetorical and factual" and contained specific, potentially defamatory, statements about plaintiff's honesty and business ethics. Accordingly, the trial court should have allowed the case to proceed to trial.
Last week the Oregon Court of Appeals weighed in on an issue being litigated around the country by homeowners who have defaulted on their mortgages: whether a nonjudicial foreclosure can occur where there has been no recorded assignment to the party seeking to foreclose. In Niday v. GMAC Mortgage, LLC, the defaulting homeowner filed suit to stop a foreclosure, claiming that the holder of the promissory note was not the original lender, and that the assignment of the note had not been recorded with the county.
At issue was the Mortgage Electronic Registration System, Inc. -- known as MERS -- which lenders have used for nearly 20 years to track electronically the transfer of beneficial interests in loan obligations. Lenders using the MERS system do not record the sale or assignment of a beneficial interest because MERS remains in place as the "beneficiary" of a trust deed notwithstanding the sale or assignment.
The Court of Appeals, interpreting Oregon's 1959 law allowing foreclosure by a private, advertised trustee's sale rather than through a court-ordered foreclosure, held that a nonjudicial foreclosure cannot occur if an assignment of the beneficial interest was not recorded. The Court rejected the argument by MERS that, even though it was not the lender or a successor to the lender, foreclosure was proper because it had been designated as beneficiary of the trust deed when the homeowner took out the loan.
There was evidence in Niday that the lender assigned its interest in the trust deed without recording the assignment, and the Court of Appeals ordered a trial on whether the predicates to nonjudicial foreclosure had been satisfied.
The day after the Court of Appeals issued the opinion in Niday, the Oregon Supreme Court accepted a certified question from the U.S. District Court in a case also addressing nonjudicial foreclosures of mortgages tracked by MERS.
The Oregon Supreme Court last month held that an LLC that leased office space to a physician could not be held liable on an apparent agency theory for physical injuries suffered by the physician's patient.
In Eads v. Borman, the injured patient contended that the landlord, Willamette Spine Center, LLC, through signage on the building and other representations, created the appearance that the building housed a group medical entity of which the physician was an agent. Plaintiff claimed that that the LLC thereby created an apparent agency relationship with the physician.
The Supreme Court noted that an agency relationship can arise from the appearance of consent by one person to allow another to act on its behalf. And a principal can be vicariously liable for the negligence of an agent who is not an employee, but only if the principal actually or apparently had a right of control over the agent's injury-causing actions.
The Court then surveyed other states' treatment of apparent agency in the context of medical malpractice. The Court agreed with those authorities that a hospital or other entity can be held vicariously liable for a physician's negligence on an apparent authority theory if the entity held itself out as a direct provider of medical care, and if plaintiff relied on those representations by looking to the entity, rather than the physician, as the provider of care.
In this case, the Court concluded that there was insufficient evidence that the landlord LLC held itself out as a provider of medical services that it delivered through agents such as its tenant, plaintiff's physician. Further, there was insufficient evidence that plaintiff relied on any representation by the LLC to believe that the LLC was itself a medical provider. On that basis, the Court found no apparent agency relationship and affirmed summary judgment for the LLC.
The federal Computer Fraud and Abuse Act, 18 USC sec. 1030, imposes criminal liability for unauthorized access to a computer, or for exceeding authorized access. An en banc panel of the Ninth Circuit last month narrowly interpreted the CFAA, holding that it does not apply to violations of private computer use policies. The opinion sets up a conflict with other federal circuit courts that may end up being resolved by the US Supreme Court.
In US v. Nosal, the defendant was convicted of aiding and abetting a violation of the CFAA after he convinced employees of an executive search firm to give him confidential client information from the firm's database. While the employees were authorized to access the information, their employer's policy prohibited disclosing confidential information to persons outside the company. The validity of the conviction turned on the meaning of the phrases "without authorization" and "exceeds authorized access" in the CFAA.
The anti-discrimination provisions of the Fair Housing Act don't apply to a Roommate.com, the Ninth Circuit Court of Appeals ruled last month in Fair Housing Council v. Roommate.com, LLC.
Roommate.com operates a web site that helps roommates find each other. When users sign up they create a profile stating their sex, sexual orientation, and whether children will be living with them. Users may also complete an "Additional Comments" section. Users are asked to list their preferences for roommate characteristics, including sex, sexual orientation, and familial status. Based on the profiles and preferences the web site provides potential matches. The site also allows users to search based on roommate characteristics.
Plaintiff sued Roommate.com alleging that the questions about users' characteristics, and matching and steering based on those characteristics, violate the federal Fair Housing Act, which prohibits discrimination in the sale or rental of dwellings.
Judge Kozinski, writing for the Ninth Circuit, found no violation, based on the fact that roommates necessarily share a single "dwelling": "It makes practical sense to interpret 'dwelling' as an independent living unit and stop the FHA at the front door." According to the court, the selection of a roommate is more akin to a private relationship -- in which the government won't meddle -- than to a landlord-tenant relationship that's protected against discrimination.