ESP Wiki is looking for moderators and active contributors!

Difference between revisions of "Formulating arguments"

m (Reverted edits by 217.151.225.37 (talk) to last revision by Ciaran)
(formatting and remove navbox)
 
Line 1: Line 1:
{{navbox}}
 
 
When writing letters or discussing patent policy, it's important to plan what message you want to get across.
 
When writing letters or discussing patent policy, it's important to plan what message you want to get across.
  
Line 41: Line 40:
  
 
{{footer}}
 
{{footer}}
[[Category:Scribbles]]
+
[[Category: Campaigning]]
[[Category:Campaigning]]
+
[[Category: Scribbles]]

Latest revision as of 14:50, 16 October 2014

When writing letters or discussing patent policy, it's important to plan what message you want to get across.

Don't implicitly shrink the issue

Software patents cause many different problems. If you want to discuss one of those problems, remember to highlight that this is just one of many problems.

For example:

  • The patent system's timelines don't work for software, but if they were improved, software still shouldn't be patented.
  • Many software patents are of woeful quality, but if quality was improved, the remaining ones would still be bad.
  • Software patents harm the software market, BUT the software market is not the only concern.
  • Same for SMEs.
  • Same for standards.
  • Same for innovation.

Try to formulate your arguments as:

  • Software patents are not necessary for X, in fact they harm X, but moreover they harm Y.

Related pages on ESP Wiki

Arguments