You can ask Erin, I've been railing at this for ... what? ... let's see I graduated law school in 2004, I took my first Trademarks class in ... 2002 or so? ... 16 years?
As you might expect from a lawyer that spends a lot of time thinking about how law applies to the food and beverage business, I am obsessed (obsessed!) with Geographic Indications, the TRIPS word for Appellation d'Origine Controlle (FR), Protected Designation of Origin (EU), Denominazione di origine controllata (IT), Certification Marks (US), etc.
Historically, the US has looked to take advantage of European intellectual property by "borrowing" their designations of origin for things that bear little passing resemblance to "cheese," let alone "parmesan" or "asiago" or "feta."
The chicken is now coming to roost, so to speak, with the current trade war. It turns out that when you slap huge tariffs on your trading partners, they don't like that and they look elsewhere. When they look elsewhere, the others ask that you play by their rules. If their rules are better (e.g., aren't huge tariffs), then you play the game. So, when our bumbling fool of a head of state imposed tariffs on Mexico and pulled out of the Trans Pacific Partnership, the partners to those looked to get their goods elsewhere - namely Europe. And Europe came in and say, we'd be happy to send you all the Asiago cheese you can handle, but you have to agree to play by our Asiago rules - so, no Asiago from anywhere other than Italy.
In response, and I can only imagine cartoonishly hopping mad, Wisconsin cheesemaker Sartori renamed their "asiago" cheese "Sartiago" so that Mexico wouldn't stop importing it.
In an event that I assume Sen. Tammy Baldwin has no recollection of, I actually spoke to her about Geographic Indications and how we, Wisconsin, were missing the boat. [ed note: the short version of this story is that we were both being interviewed for a documentary about beer]. And, she responded with something like this. I think her position, the typical American position, and definitely the official "Wisconsin Food Producers" position is that anyone should be allowed to call their hard white salty cheese "parmesan" because "What else would you call it?" Well...maybe Asiago?
Look, this full discussion is much longer. I actually get most of the way into the full rant in a podcast that I did with Edible Alpha about trademarks in food [ed note: that was part 2, you can find part 1 here.
But, the short of the argument is this: if "terroir" in food means anything - and I think the whole premise of the sustainability, locavore, slow food, whatever-you-want-to-call-it movement is fundamentally based on it meaning something - then, we [ed note: the "royal we" not literally you, the reader, and me, Jeff, the author, but yes, us too] need to protect Designations of Origin as meaning something. And that means, that when someone in a particular place creates something that you like and they call it something to show their pride in their place that you - manufacturer in the middle-of-nowhere foreign country - can't create something that vaguely resembles that thing and call your thing the same thing. Because that's misleading the public, it's deceptive trade practice, it's counterfeiting, it's infringement.
The State Journal article mentions that "The U.S. has been battling the EU over the geographic naming restriction during trade negotiations dating back to the Obama administration." This is wrong. This "battle" dates back to arguably, the Paris Convention in 1883 and certainly to TRIPS in 1995, but even back to the adoption of the American Viticultural Areas in 1981 and a first attempt at such a thing back in the 1930s.
Law, technology, beer, policy, and a few other things thrown in for good measure.
Tuesday, July 24, 2018
Friday, July 13, 2018
Design Thinking and Lawyers
I am going to start by saying that I am not trained in "Design Thinking" or any of its sub or related fields. I'm not going to spend a lot of time giving backstory on Design Thinking. For that, go check out the Stanford d.school and/or the work of Margaret Hagen at Stanford's Legal Design Lab. So, with the "what this isn't" out of the way...
I believe that one of the most underrated skills of a lawyer is problem solving. Clients don't often think of lawyers as "problem solvers." We are more often thought of as "technicians" or, in other words, people who act at the instruction of the client.
Indeed, many clients dread lawyers because we aren't seen as problem solvers at all, but problem causers. Lawyers have a reputation for saying "no, you can't do that because laws x, y, and z say it's illegal." As a result, clients are reluctant to come to lawyers in the first place. I'm not saying I'm immune to this problem [hands over ears "lalalalalalalalala"], but I am saying that lawyers can and should be better.
Moreover, We can have a relatively long discussion about why lawyers-as-technician is a dead business model, but the short of it is that no-longer-that-advanced-technology will soon be doing the "technician" piece of being a lawyer. Advances in technology such as artificial intelligence, smart contracting, blockchain, not to mention industry pressures from rapidly increasing innovation cycles will put pressure on lawyers to modularize, standardize, and mechanize the drafting of contracts and other transactional documents.
There will be (already is) increased pressure on lawyers to be problem solvers. To work with clients to understand facts (products and businesses processes), the analyze "the law" (regulatory, case law, whatever), and to work with clients to align appropriately. Once this framework is in place, our robot overlords will take it from there and draft the contracts that define the way forward.
Thus, lawyers have a need for an arsenal of tools to engage in problem solving. Law school, the analysis of fact and conclusion of law, is one such tool. The business world has many such tools - Design Thinking, Lean Startup, Six Sigma, just to name three. As business lawyers we will need to be conversant in these business tools, not just our legal tools.
I believe that one of the most underrated skills of a lawyer is problem solving. Clients don't often think of lawyers as "problem solvers." We are more often thought of as "technicians" or, in other words, people who act at the instruction of the client.
Indeed, many clients dread lawyers because we aren't seen as problem solvers at all, but problem causers. Lawyers have a reputation for saying "no, you can't do that because laws x, y, and z say it's illegal." As a result, clients are reluctant to come to lawyers in the first place. I'm not saying I'm immune to this problem [hands over ears "lalalalalalalalala"], but I am saying that lawyers can and should be better.
Moreover, We can have a relatively long discussion about why lawyers-as-technician is a dead business model, but the short of it is that no-longer-that-advanced-technology will soon be doing the "technician" piece of being a lawyer. Advances in technology such as artificial intelligence, smart contracting, blockchain, not to mention industry pressures from rapidly increasing innovation cycles will put pressure on lawyers to modularize, standardize, and mechanize the drafting of contracts and other transactional documents.
There will be (already is) increased pressure on lawyers to be problem solvers. To work with clients to understand facts (products and businesses processes), the analyze "the law" (regulatory, case law, whatever), and to work with clients to align appropriately. Once this framework is in place, our robot overlords will take it from there and draft the contracts that define the way forward.
Thus, lawyers have a need for an arsenal of tools to engage in problem solving. Law school, the analysis of fact and conclusion of law, is one such tool. The business world has many such tools - Design Thinking, Lean Startup, Six Sigma, just to name three. As business lawyers we will need to be conversant in these business tools, not just our legal tools.
Subscribe to:
Posts (Atom)