LogFAQs > #954553172

LurkerFAQs, Active DB, DB1, DB2, DB3, DB4, DB5, DB6, DB7, Database 8 ( 02.18.2021-09-28-2021 ), DB9, DB10, DB11, DB12, Clear
Topic List
Page List: 1
TopicControversial Opinion #4: Automation
darkknight109
06/02/21 5:32:58 AM
#251:


LinkPizza posted...
For the context clues, you don't have to scroll back a dozen post. As I said if you would read what I typed it was that the clues are usually in the next sentence or two.
Except that's not the case or I wouldn't be calling you out on it.

If your posts are poorly constructed, don't expect me to do your work for you.

LinkPizza posted...
And my context clues aren't ambiguous to the point of worthlessness.
They 100% are, dude.

LinkPizza posted...
As for copywriting, I'm just telling you what the law said. Something about being able to protect the creative expression associated with a recipe.
"Something about"? Meaning you don't know.

Here, allow me to educate you on the subject: recipes are not copywritable. Period. This is not debatable at all.

From here: https://www.copyright.gov/circs/circ33.pdf

"Recipes
A recipe is a statement of the ingredients and procedure required for making a dish of food. A mere listing of ingredients or contents, or a simple set of directions, is uncopyrightable. As a result, the Office cannot register recipes consisting of a set of ingredients and a process for preparing a dish. In contrast, a recipe that creatively explains or depicts how or why to perform a particular activity may be copyrightable. A registration for a recipe may cover the written description or explanation of a process that appears in the work, as well as any photographs or illustrations that are owned by the applicant. However, the registration will not cover the list of ingredients that appear in each recipe, the underlying process for making the dish, or the resulting dish itself. The registration will also not cover the activities described in the work that are procedures, processes, or methods of operation, which are not subject to copyright protection.

Examples: Jules Kinder submits an application to register a cookbook, Pie in the Sky. In the Author Created field of the application, Kinder asserts a claim in text, photographs, and compilation of ingredients. Each recipe contains a list of ingredients, instructions for making a pie, and a photograph of the finished product. The claim in a compilation of ingredients will not be accepted because there is no copyrightable authorship in a mere listing of ingredients. Since this claim is not acceptable, the Office may communicate with Jules Kinder to limit the extent of the registration to the text and photographs only. Paulina Neumann submits an application to register a recipe for caesar salad dressing. In the Author Created field, Neumann asserts a claim in text. The work consists of a list of eleven ingredients with the following instructions: (1) puree anchovies, garlic, Dijon, egg yolks; (2) drizzle oil in gradually to emulsify; (3) add lemon, parmesan cheese, salt, pepper, Worcestershire and tabasco sauce. The Office will refuse registration for this work, because the list of ingredients is uncopyrightable, and the instructional text contains an insufficient amount of creative authorship."

Emphasis mine.

In essence, while you could copyright a cookbook or how a recipe is presented, the recipe itself is not subject to copyright and anyone can use it without permission or paying royalties.

LinkPizza posted...
And the problem I see is that robots will be able to steal those recipes.
You can't have something "stolen" from you if it doesn't belong to you in the first place.

Again, recipes are not copywritable. If they were, you wouldn't be able to cook a hamburger for yourself unless you paid McDonalds for the right to do so.

LinkPizza posted...
I mean, how would you being able to make the restaurant food at home not cost the restaurant money? If you had a robot that could make you the exact same food just like the restaurant does at home for less money, why would you go to pay more at the restaurant for things other than things like parties and get-togethers.
You wouldn't. As a result, restaurants would have to change their business model, as most businesses facing changing technology do. Expect to see them shift to more of a lounge-style get together area rather than somewhere whose main selling point is food.

LinkPizza posted...
So, I 100% expect industry reps to step in.
And do what? They have no legal power and any lobbying they do will be opposed by the (much larger and more well-equipped) big tech lobby.

Moreover, you can't outlaw an idea. The robots are merely working off of publicly available information. There is no meaningful way to ban that technological process, nor would anyone outside the food industry want to.

LinkPizza posted...
As for the Chef's teaching them, just because they can't copyright the recipe in the normal way doesn't mean they are forced to tell anybody the recipe or how to cook it. So, again, Many chefs may not actually teach the robots how to do anything. Which I'm totally fine with...
Yet you already conceded that the robots are fully capable of working out the dish on their own, whether or not the chef wants to cooperate.

If you're a chef and you have the option between selling your recipe to an interested robot manufacturer for potentially millions of dollars or simply letting them work it out on their own and eventually wind up with nothing, you'd be an idiot not to take the former.

---
Kill 1 man: You are a murderer. Kill 10 men: You are a monster.
Kill 100 men: You are a hero. Kill 10,000 men, you are a conqueror!
... Copied to Clipboard!
Topic List
Page List: 1