Menu
News
All News
Dungeons & Dragons
Level Up: Advanced 5th Edition
Pathfinder
Starfinder
Warhammer
2d20 System
Year Zero Engine
Industry News
Reviews
Dragon Reflections
White Dwarf Reflections
Columns
Weekly Digests
Weekly News Digest
Freebies, Sales & Bundles
RPG Print News
RPG Crowdfunding News
Game Content
ENterplanetary DimENsions
Mythological Figures
Opinion
Worlds of Design
Peregrine's Nest
RPG Evolution
Other Columns
From the Freelancing Frontline
Monster ENcyclopedia
WotC/TSR Alumni Look Back
4 Hours w/RSD (Ryan Dancey)
The Road to 3E (Jonathan Tweet)
Greenwood's Realms (Ed Greenwood)
Drawmij's TSR (Jim Ward)
Community
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Resources
Wiki
Pages
Latest activity
Media
New media
New comments
Search media
Downloads
Latest reviews
Search resources
EN Publishing
Store
EN5ider
Adventures in ZEITGEIST
Awfully Cheerful Engine
What's OLD is NEW
Judge Dredd & The Worlds Of 2000AD
War of the Burning Sky
Level Up: Advanced 5E
Events & Releases
Upcoming Events
Private Events
Featured Events
Socials!
EN Publishing
Twitter
BlueSky
Facebook
Instagram
EN World
BlueSky
YouTube
Facebook
Twitter
Twitch
Podcast
Features
Top 5 RPGs Compiled Charts 2004-Present
Adventure Game Industry Market Research Summary (RPGs) V1.0
Ryan Dancey: Acquiring TSR
Q&A With Gary Gygax
D&D Rules FAQs
TSR, WotC, & Paizo: A Comparative History
D&D Pronunciation Guide
Million Dollar TTRPG Kickstarters
Tabletop RPG Podcast Hall of Fame
Eric Noah's Unofficial D&D 3rd Edition News
D&D in the Mainstream
D&D & RPG History
About Morrus
Log in
Register
What's new
Search
Search
Search titles only
By:
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
Community
General Tabletop Discussion
Publishing Business & Licensing
Boilerplate Language: Worrying about the OGL (Part 4)
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Snarf Zagyg" data-source="post: 8914195" data-attributes="member: 7023840"><p>Look, I assume you actually read the first post? </p><p></p><p>Here-</p><p></p><p><u><em>Boilerplate</em></u><em> is the standardized language that you will see in contract after contract; it's the stock provisions that you will see in most (or all) contracts of a certain type. Even if they might not apply, you will see a lot of <u>boilerplate</u>.</em></p><p><em></em></p><p><em>...</em></p><p><em></em></p><p><em>To give you an idea of how this would operate in practice, you will often see contracts that have "boilerplate" provisions. Most contracts of most types have a choice of law provision, a severance clause, a merger clause, and so on. Different law firms and companies might vary the language a little, but you will almost always see this in most types of contacts (is the contractual provision labeled controlling law, choice of law, or governing law etc.).</em></p><p></p><p>That's it. Boilerplate does not mean good. It does not mean bad. It just refers to standardized common contractual provisions that do not vary greatly in contracts, and are often copied verbatim from contract to contract. That's it. </p><p></p><p>This means a few things (which was also covered in the prior column on why attorneys write a certain way)- as I wrote, the prevalence of <em>boilerplate language</em> means that it will often appear, even when it isn't applicable. For example, the "class action waiver" language will almost always include a reference to "collective actions" even though it is inapplicable outside of employment contexts, simply because the language gets re-used. </p><p></p><p>But it's also important to think about <em>why</em> something became a particular provision, and what it means. Boilerplate does not arise by accident; I just explained to you why severance clauses are used. There are similar reasons for all the clauses, from merger to choice of law to, yes, even class action waivers. </p><p></p><p>So instead of saying standard contractual language is corrosive, you actually need to be able to come to the table and explain why that is the case. And it is frustrating for attorneys when they see people say things like your objection to the <em>standard disclaimer of warranties and liability</em>. They are offering up IP, and they are (for a license that can be used in all sorts of jurisdictions will all sorts of rules) just saying that they are providing the material "as is."</p><p></p><p>It's bizarre. Again, there's a lot of issues going on, but it helps to concentrate on real issues, and not make fake ones up.</p></blockquote><p></p>
[QUOTE="Snarf Zagyg, post: 8914195, member: 7023840"] Look, I assume you actually read the first post? Here- [U][I]Boilerplate[/I][/U][I] is the standardized language that you will see in contract after contract; it's the stock provisions that you will see in most (or all) contracts of a certain type. Even if they might not apply, you will see a lot of [U]boilerplate[/U]. ... To give you an idea of how this would operate in practice, you will often see contracts that have "boilerplate" provisions. Most contracts of most types have a choice of law provision, a severance clause, a merger clause, and so on. Different law firms and companies might vary the language a little, but you will almost always see this in most types of contacts (is the contractual provision labeled controlling law, choice of law, or governing law etc.).[/I] That's it. Boilerplate does not mean good. It does not mean bad. It just refers to standardized common contractual provisions that do not vary greatly in contracts, and are often copied verbatim from contract to contract. That's it. This means a few things (which was also covered in the prior column on why attorneys write a certain way)- as I wrote, the prevalence of [I]boilerplate language[/I] means that it will often appear, even when it isn't applicable. For example, the "class action waiver" language will almost always include a reference to "collective actions" even though it is inapplicable outside of employment contexts, simply because the language gets re-used. But it's also important to think about [I]why[/I] something became a particular provision, and what it means. Boilerplate does not arise by accident; I just explained to you why severance clauses are used. There are similar reasons for all the clauses, from merger to choice of law to, yes, even class action waivers. So instead of saying standard contractual language is corrosive, you actually need to be able to come to the table and explain why that is the case. And it is frustrating for attorneys when they see people say things like your objection to the [I]standard disclaimer of warranties and liability[/I]. They are offering up IP, and they are (for a license that can be used in all sorts of jurisdictions will all sorts of rules) just saying that they are providing the material "as is." It's bizarre. Again, there's a lot of issues going on, but it helps to concentrate on real issues, and not make fake ones up. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
Publishing Business & Licensing
Boilerplate Language: Worrying about the OGL (Part 4)
Top