21 posts categorized "Property Rights"

How long should it take Facebook to give users control over their personalities?

Reference is hereby made to the post here of Saturday last, Facebook's own healthcare.gov-like debacle.

The issue before us is, how long should it take Facebook to build a control that notifes a user that her name and/or likeness has been used to endorse a product or service, and to allow that user to kill the use of her personality rights in that ad?

8480754834_888d738c9b_zTo paraphrase the Facebook spokesperson quoted in the NYTimes article prompting Saturday's post, "these things take time."

I reached out to five coders I know and highly respect, got answers from four of them, and will attribute quotes to two of them, with permission:

Dan Carleton told me that building this feature is not as complicated as, say, fixing healthcare.gov:

"So what they are talking about is adding a system where you can be notified if you appear in one of these ads, and they’re adding a preference that you can opt out of appearing in these ads, right? So they already have a generalized system for sending different kinds of notifications to users, they already have a generalized system for tracking privacy settings and opt-in and opt-out, right? So those two major components are already there. So this is just a new type of notification they need to send people that appear in one of these ads, and a new bit they need to be able to flip per person as to whether or not they want to be in one of these ads, and then they just have to propagate the value of that bit down into the ad-serving platform. It just doesn’t seem that hard. It’s mostly a matter of priority. As a feature, in terms of surface area, in terms of how big a team you would need to accomplish it, in terms of just the integration issues you have to work through, it doesn’t seem like the team would have to be that large. Maybe four people working on it for a month and a half?"

Jason Thane told me that the problem is not really a technical one:

"A company like Facebook likely has many tiers of test and measurement for any new features that end up deployed as part of their product. So, though such a feature may be simple to build from a technical perspective, the challenge probably lies in crafting the messaging and positioning within the product such that the feature won't produce the kind of resentment several of their other privacy-related features have in recent memory. That's a taller order than any specific technical hurdle."

A third friend told me he couldn't comment, given something he is working on right now for a different company.

A fourth friend told me my knowledge of what actually happens, on the ground, on Facebook, is out of date:

"I took a look around Facebook and I can't find any examples of names or likenesses being used in onsite advertising anymore. I don't see it as an option in the advertising setup anymore either. I remember this summer when I was running . . . ads you would see social information about who was playing, liking the application but I'm not seeing it anymore."

Photo: zombieite / Flickr.

Spying vs. stealing

Imagine Facebook had to pay you for using any information about you.

Instead of balancing "personal privacy" against some super-secret corporate imperative to profile you for the purposes of manipulating you, instead of that, your individual interests, and Facebook corporate interests, were perfectly aligned.

MV5BMTk4OTE2NjU1MF5BMl5BanBnXkFtZTcwMzQ5MDQ1Ng@@._V1_SY317_CR46,0,214,317_You and Facebook were partners in the monetization of your information, your personality.

In short, your information was your intellectual property.

In the privacy paradigm, Facebook may or may not get the "balance" - between your interests and its commercial imperatives - exactly right, but Facebook alone controls all exclusive intellectual property rights.

In the personal-information-as-intellectual-property paradigm, Facebook must account to you for how your information is processed and exploited. No "balancing act" required; simple commercial reporting obligations ensure accountability.

If we thought about our information this way, and if our commercial relationships with large web services were built to meet such expectations, it would be harder for companies like Facebook, Google, Apple, etc., to cooperate with government requests for all the data that runs through the corporate servers.

"That data does not belong to us," they could say. Depending on their contract with customers, they might also say, "It is, however, available for a premium fee."

Some people might be willing to sell their information to the government in exchange for good and valuable consideration - say, a federal income tax credit. For some, maybe patriotism would be sufficient consideration.

Trademark beef

What foods are they serving at the US Patent and Trademark Office cafeteria?

From a Brian Rogers retweet of a tweet from Erik Pelton comes a link to this more-than-usually entertaining official USPTO Communication in connection with a federal trademark registration application.

Chicken and kale

The central issue presented: is the applicant's word mark, EAT MORE KALE, confusingly similar to the existing mark, EAT MORE CHIKIN.

In finding that the marks are confusingly similar, the PTO's examiner discusses how a word chosen in opposition to another can be calculated to invoke an association:

"Applicant . . .discusses the differences between the terms KALE and CHICKEN. The trademark attorney [examining this application] concedes that these terms are different and that they have specific definitions. But the similarities between the marks are more important than the differences. Both parties’ marks have a similar concept – encouraging those that encounter the marks to eat more of something. The marks urge action in the same way, only as to different substances and both of them are commonly consumed types of food. Given the nature of the goods and services, it is the attorney’s position that this is sufficient to find them similar. He has to be mindful of the fact that consumer confusion has been held likely even for marks that do not physically sound or look alike but that convey the same idea, stimulate the same mental reaction, or may have the same overall meaning. Proctor & Gamble Co. v. Conway, 419 F.2d 1332, 1336, 164 USPQ 301, 304 (C.C.P.A. 1970) (holding MISTER STAIN likely to be confused with MR. CLEAN on competing cleaning products); see Ralston Purina Co. v. Old Ranchers Canning Co., 199 USPQ 125 (TTAB 1978) (holding TUNA O’ THE FARM for canned chicken likely to be confused with CHICKEN OF THE SEA for canned tuna); Downtowner Corp. v. Uptowner Inns, Inc., 178 USPQ 105 (TTAB 1973) (holding UPTOWNER for motor inn and restaurant services likely to be confused with DOWNTOWNER for the same services)."

Humor aside, I find the PTO examiner's reasoning to be pretty good and the communication to be professional.

Diptych from photos by normanack (chicken) and by Tuscanycious (kale), both on Flickr.

Macy's exclusivity with Martha Stewart

We had such a good time last month parsing a license assignment clause, I thought we'd enjoy having a look at the exclusivity provisions in the contract between Macy's and Martha Stewart Living Omnimedia.

Lisbon black collectionMacy's has sued Martha Stewart's company, claiming that the latter's recently announced deal with JCPenney violates an exclusive contract with Macy's. Reportedly, the judge in the case has sent the parties off to mediate for a month.

I found what looks like the most current version of Macy's complaint, along with a copy of the main contract between Macy's and Martha Stewart Living Omnimedia.

It wasn't hard to find these documents - I went straight to the new York State Supreme Court website and use the native search functions it provides - but I have to say, the news stories I've seen don't make it easy for the layperson to access primary documents. That reflects poorly on professional journalism.

Redacted page from complaintIf you're a journalist and you're writing about a high-profile lawsuit or a key provision in an essential contract in dispute, why not link to the complaint and to the contract? One of the glories of our open judicial system is that disputes are adjudicated in public, and so the complaints, answers, briefs and exhibits that get filed with a court are (subject to redactions when confidentiality is warranted) open to the public. When courts take the trouble to make documents available online, there really is no reason for a journalist writing about the case to not link to the source documents.

Anyway, it's going to take a post or two (or more) to unpack the contractual genesis of Macy's complaint. Maybe because the "intellectual-property" at issue is pretty nebulous - little more than the Martha Stewart name and some personality rights - the defined terms deployed go off in different directions, and it's not yet clear to me that they meet back at one consistent center. Then again, maybe they do; but it will take some work to find the center.

Here's an example of what I mean: the contract uses a defined term, "Exclusive Products," styled in the conjunctive, and in a manner that may almost seem calculated to obviate connotations of exclusivity. Here's that defined term:

"'Exclusive Products' shall mean those products in the Exclusive Product Categories that are branded under the Trademark, manufactured by Licensee, and marketed and sold by Licensee or, under the conditions set forth herein, through an MSLO DTC Channel."

There are two or three other defined terms to unpack here, for sure, but I hope you see my point. Reading this defined term in isolation suggests that products don't become "exclusive" unless and until Macy's manufactures, markets and sells them.

More to come. Maybe this post will beget a miniseries.

Redacted pages (one pictured) in the Macy's complaint remind me of the Martha Stewart Collection Dinnerware, Lisbone Black Collection.

A right answer in the Cascadia Cup trademark registration kerfuffle

It's okay to talk about sports on Counselor @ Law because this story is really about intellectual property.

Check that. The story is about where intellectual property meets cultural property.

Some background: Seattle, Vancouver and Portland have soccer clubs that, of late, play in the professional league known as MLS.

But before any of Seattle, Vancouver and Portland joined MLS, the three were in other leagues, and over years a rivalry developed.

Cascadia cup

Fans put a name to the rivalry and to the trophy awarded to the yearly champion: the Cascadia Cup.

(Side note: "Cascadia" has connotations difficult for people who don't live along the Vancouver/Seattle/Portland corridor to understand. It is a transnational (maybe even a secessionist) concept. These subversive connotations are fitting for the soccer rivalry insofar as they suggest that loyalty to the sport runs deeper than national identity.)

Comes now the MLS, looking to capitalize on the goodwill associated with regional rivalries among member MLS teams. According to this story from the AP:

"The MLS has . . . applied to trademark other rivalries, including the Rocky Mountain Cup, the Brimstone Cup between the Chicago Fire and FC Dallas, and the California Clasico between the San Jose Earthquakes and the L.A. Galaxy."

The MLS wants to treat "Cascadia Cup" as MLS IP as well, but a consortium of Seattle, Vancouver and Portland soccer fan clubs have organized to assert their own, prior rights in the trademark. See this assessment of the clash from Michael Atkins, who also links to the trademark applications at issue.

On the most recent Nos Audietis podcast, former soccer player and current TV soccer commentator Alexi Lalas seemed to suggest that the fan group should defer to the beneficence of the league. Here's what he said in answer to a question about whether it would be realistic for the MLS to newly brand the regional rivalry and ignore the Cascadia Cup mark:

"Oh yeah, it is certainly realistic.

"I see first and foremost them [the league and the fan group] getting together, them talking. I think from a CCC [Cascadia Cup Council, the fan group] perspective, they should first let MLS explain themselves much better, and let them give them detailed, point by point by point, 'this is how we are going to make your Cup better, and this is why the ownership, or being the custodians, of this Cup, is going to help it become better and become even something greater than you ever imagined. And this is why having it greater than you ever imagined is going to be good for you, and maybe even,' appealing to their sense of greater good, 'and why it is going to be good for this league and this sport that you, at least on the surface, purport that you believe in.' I think that's first and foremost hat has to happen.

"With regards to the other possibility, where they just napalm the whole thing and say 'okay fine, it's still yours, go ahead, enjoy it, do what you want to do, but there will be no mention of it, there will be no recognition of it from a league nor from a team standpoint going forward; and if it's this clandestine type of out back, alley way, post-game presentation to a player who will remain anonymous, then so be it.'

"I hope it doesn't get to that, because what will mean is that they [the MLS] will create their own version of it, and it will be diluted, and it will lack any authenticity or credibility, and it will serve to further distance the very people that are going to drive, as I said, the very fuel that is hopefully going to ignite this to something bigger and better. That would be disappointing to me, not just from a Cascadia Cup perspective, but from a soccer perspective. Because if there is one thing I think we can all agree on, it's that in order for this game to continue to go forward, there has to be communication, there has to be cooperation, and to be quite honest, that's how we've gotten so far in such a relatively short period of time. And if it starts splintering off, that can lead to big, big problems."

I think Lalas is too quick to concede that a typical, advertising sponsorship path is the right way to exploit this particular mark. But I do think he's right that the parties should focus on what they want the Cascadia Cup to mean in the coming years.

The framework for the solution is this: MLS should acknowledge the prior rights of the supporters group in the Cascadia Cup mark, assign its Candian registration to the supporters group, and decline to oppose the application that the supporters group has made in the US; in exchange, the supporters should give MLS a multi-year license to use the Cascadia Cup mark according to branding guidelines that are mutually acceptable.

The negotiations should be about the branding guidelines for the Cascadia Cup mark.

Zynga's Employee Invention Assignment and Confidentiality Agreement with Alan Patmore

I've just started looking at documents filed in the Superior Court of California, County of San Francisco, in connection with a suit brought by the game maker Zynga. Zynga filed the suit initially against its former employee, Alan Patmore, and has since amended its complaint to name Patmore's new employer, another game company, Kixeye, as well.

Alan PatmorePatmore is a big deal in the game industry. In an entry that appears to pre-date Zynga's lawsuit, Wikipedia credits Patmore for delivering many succesful games, including one from 2002 based on The Lord of the Rings, which, Wikipedia says, sold 1.8 million copies. "Patmore," Wikipedia states, "is a much sought-after authority within the industry on topics including project management, creative development, and industry trends and practices."

Keep the phrases "project management" and "industry trends and practices" top of mind, because the coutcome of the fight among Zynga, Patmore and Kixeye may well turn on the extent to which distinctions can be drawn between Zynga-specific trade secrets, on the one hand, and general game industry expertise, on the other.

Though we're not going to unpack the various allegations, counter-allegations and defenses in the lawsuit, not today.

Instead, we'll begin our look into the case by reviewing an Employee Invention Assignment and Confidentiality Agreement between Zynga and Patmore, which was appended as an exhibit to Zynga's initial complaint.

Because Zynga is based in California and because Patmore lives in California and worked for Zynga in that state, we know Patmore's agreement with Zynga is not going to include any express post-termination non-compete covenant. To the extent that Zynga wants to impede what Patmore might accomplish for Kixeye, it is going to have to allege and show behavior on the part of Patmore that is unfair, illegal, or in breach of a contractual covenant (other than a non-compete).

Is there anything unusual in that Employee Invention Assignment and Confidentiality Agreement that might tend to give Zynga's claims broader scope?

No and yes.

By and large, the Zynga Employee Invention Assignment and Confidentiality Agreement is standard and what you would expect to see in use by an angel or VC-backed startup or emerging technology company. The Agreement requires the employee:

  • to acknowledge that his work for the company is work for hire,
  • that he assign company inventions to the company,
  • that he schedule out prior inventions he means to retain,
  • that he waive moral rights, and
  • that he keep the company's proprietary information confidential.

The Agreement also contains a one-year, post-termination covenant to not solicit Zynga employees or consultants.

All of the foregoing is normal. But there are two nuances in the Zynga Employee Invention Assignment and Confidentiality Agreement, pieces of bespoke drafting, that could be important, from Zynga's perspective, in expanding the scope of what may be fairly regarded as trade secrets for purposes of this case.

The first bit of custom drafting is in the definition of Proprietary Information. Here's an excerpt of what the Agreement says are examples of the kinds of information that ought to be regarded as proprietary to Zynga:

"Proprietary Information may include information I learn about or develop in connection with my employment with the Company, such as: . . . (ii) techniques and methods for developing, coding, or improving online social games; (iii) techniques and methods to create 'virality;'  (iv) measurement techniques, and specific functionality that increases monetization and both measures and increases retention metrics; . . . (xi) the particular needs and preferences of the Company's suppliers, platform providers and business partners, and the Company's approaches and strategies for satisfying those needs and preferences . . . ."

Arguably, much of what is described in these examples could fall under the rubric of general industry knowledge or experience gained through work for a succession of employers. By including these items in a "laundry list" of what should be regarded as proprietary, Zynga is doing what it can to shift the balance somewhat, and expand, by virtue of agreement of the parties, the scope of what should be regarded as protected. On the other hand, and as you would expect, the Agreement has a standard carve-out to the definition of Proprietary Information, eliminating from the scope of what is protected such information as is generally known, was previously known, or is independently developed. This carve out will temper the expansive effect of the "laundry list."

And here's the second bit of custom drafting, an entire section of the Agreement that is clearly calculated to secure an employee's acknowledgment of an expansive view of what should be regarded as trade secret:

"14. Non-Solicitation of Suppliers/Customers. During and after the termination of my employment with the Company, I will not directly or indirectly solicit or otherwise take away customers or suppliers of the Company if, in so doing, I access, use or disclose any trade secrets or proprietary or confidential information of the Company. I acknowledge and agree that the names and addresses of the Company's customers and suppliers, and all other confidential information related to them, including their buying and selling habits and special needs, whether created or obtained by, or disclosed to me during my employment, constitute trade secrets or proprietary or confidential information of the Company." 

The title of the section leads you to believe you'll find an express, post-termination restrictive covenant, though the actual drafting is circular. The net intent appears, again, to get the employee's buy-in to an expansive view of the kinds of information that should be regarded as proprietary to Zynga.

To be continued.

Photo credit: VideogameVisionary.com, Alan Patmore in 2008, as posted on Flickr.

Feedback's ownership loop

Interesting feedback from @joshblake on App.net yesterday about App.net's written Developer Terms.

Go here to see the actual thread in which Blake framed the problem and the discussion that ensued. Here's how you might express the issue in the form of a question: how can App.net, with a straight face, ask independent developers for feedback, while at the same time insisting that App.net own any such feedback?

FeedbackAny service provider with ambitions to become a platform will of course relish feedback, especially when that user is an accomplished outside developer who understands how the service works, technically, and who puts effort and imagination into fusing new applications onto the service.

That service provider will naturally covet the unrestricted ability to make use of feedback.

App.net took a wrong turn by publishing an overreaching covenant about developer feedback. Here's what it says, or said, in a version dated September 26, 2012:


We love feedback. Please let us know what you think of the API, these Developer Terms and, in general, App.net. When you provide us with any feedback, comments or suggestions about the API, these Developer Terms and, in general, App.net, you irrevocably assign to us all of your right, title and interest in and to your feedback, comments and suggestions.

Blake opened an issue on GitHub for further discussion.

The right approach here is probably a license, rather than an assignment, from the developer.

Here's a suggested draft of a substitute feedback provision, using license language and already carrying the benefit of Blake's feedback:


We love feedback. Please let us know what you think of the API, these Developer Terms and, in general, App.net. When you provide us with any feedback, comments or suggestions (collectively, "Feedback") about the API, these Developer Terms and, in general, App.net, you grant to us, under any right, title or interest you may have in and to such Feedback, a non-exclusive, royalty-free, worldwide, transferable, sub-licensable, irrevocable, perpetual license to use that Feedback or to incorporate it into the API, these Developer Terms, or any of App.net's products or services.

Image: Sune Petersen / Flickr.

Related Posts with Thumbnails