Argument map

From Infogalactic: the planetary knowledge core
(Redirected from Argument mapping)
Jump to: navigation, search
An argument map

In informal logic and philosophy, an argument map or argument diagram is a visual representation of the structure of an argument. An argument map typically includes the key components of the argument, traditionally called the conclusion and the premises, also called contention and reasons.[1] Argument maps can also show co-premises, objections, counterarguments, rebuttals, and lemmas. There are different styles of argument map but they are often functionally equivalent and represent an argument's individual claims and the relationships between them.

Argument maps are commonly used in the context of teaching and applying critical thinking.[2] The purpose of mapping is to uncover the logical structure of arguments, identify unstated assumptions, evaluate the support an argument offers for a conclusion, and aid understanding of debates. Argument maps are often designed to support deliberation of issues, ideas and arguments in wicked problems.[3]

An argument map is not to be confused with a concept map or a mind map, which are less strict in relating claims.

Key features of an argument map

A number of different kinds of argument map have been proposed but the most common, which Chris Reed and Glenn Rowe called the standard diagram,[4] consists of a tree structure with each of the reasons leading to the conclusion. There is no consensus as to whether the conclusion should be at the top of the tree with the reasons leading up to it or whether it should be at the bottom with the reasons leading down to it.[4] Another variation diagrams an argument from left to right.[5]

According to Doug Walton and colleagues, an argument map has two basic components: "One component is a set of circled numbers arrayed as points. Each number represents a proposition (premise or conclusion) in the argument being diagrammed. The other component is a set of lines or arrows joining the points. Each line (arrow) represents an inference. The whole network of points and lines represents a kind of overview of the reasoning in the given argument..."[6] With the introduction of software for producing argument maps, it has become common for argument maps to consist of boxes containing the actual propositions rather than numbers referencing those propositions.

There is disagreement on the terminology to be used when describing argument maps,[7] but the standard diagram contains the following structures:

Dependent premises or co-premises, where at least one of the joined premises requires another premise before it can give support to the conclusion: An argument with this structure has been called a linked argument.[8]

Statements 1 and 2 are dependent premises or co-premises

Independent premises, where the premise can support the conclusion on its own: Although independent premises may jointly make the conclusion more convincing, this is to be distinguished from situations where a premise gives no support unless it is joined to another premise. Where several premises or groups of premises lead to a final conclusion the argument might be described as convergent. This is distinguished from a divergent argument where a single premise might be used to support two separate conclusions.[9]

Statements 2, 3, 4 are independent premises

Intermediate conclusions or sub-conclusions, where a claim is supported by another claim that is used in turn to support some further claim, i.e. the final conclusion or another intermediate conclusion: In the following diagram, statement 4 is an intermediate conclusion in that it is a conclusion in relation to statement 5 but is a premise in relation to the final conclusion, i.e. statement 1. An argument with this structure is sometimes called a complex argument. If there is a single chain of claims containing at least one intermediate conclusion, the argument is sometimes described as a serial argument or a chain argument.[10]

Statement 4 is an intermediate conclusion or sub-conclusion

Each of these structures can be represented by the equivalent "box and line" approach to argument maps. In the following diagram, the conclusion is shown at the top, and the boxes linked to it represent supporting reasons, which comprise one or more premises. The reason, 1A, comprising two premises 1A-a and 1A-b, support the conclusion:

A box and line diagram

Argument maps can also represent counterarguments. In the following diagram, the objection 1A weakens the conclusion, while the reason 2A supports premise 1A-b of the objection:

A sample argument using objections

Representing an argument as an argument map

A written text can be transformed into an argument map by following a sequence of steps. Monroe Beardsley's 1950 book Practical Logic recommended the following procedure:[11]

  1. Separate statements by brackets and number them.
  2. Put circles around the logical indicators.
  3. Supply, in parenthesis, any logical indicators that are left out.
  4. Set out the statements in a diagram in which arrows show the relationships between statements.
A diagram of the example from Beardsley's Practical Logic

Beardsley gave the first example of a text being analysed in this way:

Though ① [people who talk about the "social significance" of the arts don’t like to admit it], ② [music and painting are bound to suffer when they are turned into mere vehicles for propaganda]. For ③ [propaganda appeals to the crudest and most vulgar feelings]: (for) ④ [look at the academic monstrosities produced by the official Nazi painters]. What is more important, ⑤ [art must be an end in itself for the artist], because ⑥ [the artist can do the best work only in an atmosphere of complete freedom].

Beardsley said that the conclusion in this example is statement ②. Statement ④ needs to be rewritten as a declarative sentence, e.g. "Academic monstrosities [were] produced by the official Nazi painters." Statement ① points out that the conclusion isn't accepted by everyone, but statement ① is omitted from the diagram because it doesn't support the conclusion. Beardsley said that the logical relation between statement ③ and statement ④ is unclear, but he proposed to diagram statement ④ as supporting statement ③.

A box and line diagram of Beardsley's example, produced using Harrell's procedure

More recently, philosophy professor Maralee Harrell recommended the following procedure:[12]

  1. Identify all the claims being made by the author.
  2. Rewrite them as independent statements, eliminating non-essential words.
  3. Identify which statements are premises, sub-conclusions, and the main conclusion.
  4. Provide missing, implied conclusions and implied premises. (This is optional depending on the purpose of the argument map.)
  5. Put the statements into boxes and draw a line between any boxes that are linked.
  6. Indicate support from premise(s) to (sub)conclusion with arrows.

Argument maps are useful not only for representing and analyzing existing writings, but also for thinking through issues as part of a problem-structuring process or writing process, which has been called "reflective argumentation".[13]

History

The philosophical origins and tradition of argument mapping

From Whately's Elements of Logic p467, 1852 edition

In the Elements of Logic, which was published in 1826 and issued in many subsequent editions,[14] Archbishop Richard Whately gave probably the first form of an argument map, introducing it with the suggestion that "many students probably will find it a very clear and convenient mode of exhibiting the logical analysis of the course of argument, to draw it out in the form of a Tree, or Logical Division".

However, the technique did not become widely used, possibly because for complex arguments, it involved much writing and rewriting of the premises.

Wigmore evidence chart, from 1905

Legal philosopher and theorist John Henry Wigmore produced maps of legal arguments using numbered premises in the early 20th century,[15] based in part on the ideas of 19th century philosopher Henry Sidgwick who used lines to indicate relations between terms.[16]

Anglophone argument diagramming in the 20th century

Dealing with the failure of formal reduction of informal argumentation, English speaking argumentation theory developed diagrammatic approaches to informal reasoning over a period of fifty years.

Monroe Beardsley proposed a form of argument diagram in 1950.[11] His method of marking up an argument and representing its components with linked numbers became a standard and is still widely used. He also introduced terminology that is still current describing convergent, divergent and serial arguments.

A Toulmin argument diagram, redrawn from his 1959 Uses of Argument
A generalised Toulmin diagram

Stephen Toulmin, in his groundbreaking and influential 1958 book The Uses of Argument,[17] identified several elements to an argument which have been generalized. The Toulmin diagram is widely used in educational critical teaching.[18][19] Whilst Toulmin eventually had a significant impact on the development of informal logic he had little initial impact and the Beardsley approach to diagramming arguments along with its later developments became the standard approach in this field. Toulmin introduced something that was missing from Beardsley's approach. In Beardsley, "arrows link reasons and conclusions (but) no support is given to the implication itself between them. There is no theory, in other words, of inference distinguished from logical deduction, the passage is always deemed not controversial and not subject to support and evaluation".[20] Toulmin introduced the concept of warrant which "can be considered as representing the reasons behind the inference, the backing that authorizes the link".[21]

Beardsley's approach was refined by Stephen N. Thomas, whose 1973 book Practical Reasoning In Natural Language[22] introduced the term linked to describe arguments where the premises necessarily worked together to support the conclusion.[23] However, the actual distinction between dependent and independent premises had been made prior to this.[23] The introduction of the linked structure made it possible for argument maps to represent missing or "hidden" premises. In addition, Thomas suggested showing reasons both for and against a conclusion with the reasons against being represented by dotted arrows. Thomas introduced the term argument diagram and defined basic reasons as those that were not supported by any others in the argument and the final conclusion as that which was not used to support any further conclusion.

Scriven's argument diagram. The explicit premise 1 is conjoined with additional unstated premises a and b to imply 2.

Michael Scriven further developed the Beardsley-Thomas approach in his 1976 book Reasoning.[24] Whereas Beardsley had said "At first, write out the statements...after a little practice, refer to the statements by number alone"[25] Scriven advocated clarifying the meaning of the statements, listing them and then using a tree diagram with numbers to display the structure. Missing premises (unstated assumptions) were to be included and indicated with an alphabetical letter instead of a number to mark them off from the explicit statements. Scriven introduced counterarguments in his diagrams, which Toulmin had defined as rebuttal.[26] This also enabled the diagramming of "balance of consideration" arguments.[27]

In the 1990s, Tim van Gelder and colleagues developed a series of computer software applications that permitted the premises to be fully stated and edited in the diagram, rather than in a legend.[28] Van Gelder's first program, Reason!Able, was superseded by two subsequent programs, bCisive and Rationale.[29]

Throughout the 1990s and 2000s, many other software applications were developed for argument visualization. By 2013, more than 60 such software systems existed.[30] One of the differences between these software systems is whether collaboration is supported.[31] Single-user argumentation systems include Convince Me, iLogos, LARGO, Athena, Araucaria, and Carneades; small group argumentation systems include Digalo, QuestMap, Compendium, Belvedere, and AcademicTalk; community argumentation systems include Debategraph and Collaboratorium.[31] For more software examples, see: § External links.

In 1998 a series of large-scale argument maps released by Robert E. Horn stimulated widespread interest in argument mapping.[32]

Applications

Argument maps have been applied in many areas, but foremost in educational, academic and business settings, including design rationale.[33] Argument maps are also used in forensic science,[34] law, and artificial intelligence.[35] It has also been proposed that argument mapping has a great potential to improve how we understand and execute democracy, in reference to the ongoing evolution of e-democracy.[36]

Difficulties with the philosophical tradition

It has traditionally been hard to separate teaching critical thinking from the philosophical tradition of teaching logic and method, and most critical thinking textbooks have been written by philosophers. Informal logic textbooks are replete with philosophical examples, but it is unclear whether the approach in such textbooks transfers to non-philosophy students.[18] There appears to be little statistical effect after such classes. Argument mapping, however, has a measurable effect according to many studies.[37] For example, instruction in argument mapping has been shown to improve the critical thinking skills of business students.[38]

Evidence that argument mapping improves critical thinking ability

There is empirical evidence that the skills developed in argument-mapping-based critical thinking courses substantially transfer to critical thinking done without argument maps. Alvarez's meta-analysis found that such critical thinking courses produced gains of around 0.70 SD, about twice as much as standard critical-thinking courses.[39] The tests used in the reviewed studies were standard critical-thinking tests.

How argument mapping helps with critical thinking

The use of argument mapping has occurred within a number of disciplines, such as philosophy, management reporting, military and intelligence analysis, and public debates.[33]

Logical structure: Argument maps display an argument's logical structure more clearly than does the standard linear way of presenting arguments.

Critical thinking concepts: In learning to argument map, students master such key critical thinking concepts as "reason", "objection", "premise", "conclusion", "inference", "rebuttal", "unstated assumption", "co-premise", "strength of evidence", "logical structure", "independent evidence", etc. Mastering such concepts is not just a matter of memorizing their definitions or even being able to apply them correctly; it is also understanding why the distinctions these words mark are important and using that understanding to guide one's reasoning.

Visualization: Humans are highly visual and argument mapping may provide students with a basic set of visual schemas with which to understand argument structures.

More careful reading and listening: Learning to argument map teaches people to read and listen more carefully, and highlights for them the key questions "What is the logical structure of this argument?" and "How does this sentence fit into the larger structure?" In-depth cognitive processing is thus more likely.

More careful writing and speaking: Argument mapping helps people to state their reasoning and evidence more precisely, because the reasoning and evidence must fit explicitly into the map's logical structure.

Literal and intended meaning: Often, many statements in an argument do not precisely assert what the author meant. Learning to argument map enhances the complex skill of distinguishing literal from intended meaning.

Externalization: Writing something down and reviewing what one has written often helps reveal gaps and clarify one's thinking. Because the logical structure of argument maps is clearer than that of linear prose, the benefits of mapping will exceed those or ordinary writing.

Anticipating replies: Important to critical thinking is anticipating objections and considering the plausibility of different rebuttals. Mapping develops this anticipation skill, and so improves analysis.

Standards

Argument Interchange Format

The Argument Interchange Format, AIF, is an international effort to develop a representational mechanism for exchanging argument resources between research groups, tools, and domains using a semantically rich language. AIF-RDF, is the extended ontology represented in the Resource Description Framework Schema (RDFS) semantic language. Though AIF is still something of a moving target, it is settling down.[40]

See the AIF original draft description (2006) and the full AIF-RDF ontology specifications in RDFS format.

Legal Knowledge Interchange Format

The Legal Knowledge Interchange Format (LKIF), developed in the European ESTRELLA project, is an XML schema for rules and arguments, designed with the goal of becoming a standard for representing and interchanging policy, legislation and cases, including their justificatory arguments, in the legal domain. LKIF builds on and uses the Web Ontology Language (OWL) for representing concepts and includes a reusable basic ontology of legal concepts.

See also

Notes

  1. Freeman 1991, pp. 49–90
  2. For example: Davies 2012; Facione 2013, p. 86; Fisher 2004; Kelley 2014, p. 73; Kunsch, Schnarr & van Tyle 2014; Walton 2013, p. 10
  3. For example: Culmsee & Awati 2013; Hoffmann & Borenstein 2013; Metcalfe & Sastrowardoyo 2013; Ricky Ohl, "Computer supported argument visualisation: modelling in consultative democracy around wicked problems", in Okada, Buckingham Shum & Sherborne 2014, pp. 361–380
  4. 4.0 4.1 Reed & Rowe 2007, p. 64
  5. For example: Walton 2013, pp. 18–20
  6. Reed, Walton & Macagno 2007, p. 2
  7. Freeman 1991, pp. 49–90; Reed & Rowe 2007
  8. Harrell 2010, p. 19
  9. Freeman 1991, pp. 91–110; Harrell 2010, p. 20
  10. Beardsley 1950, pp. 18–19; Reed, Walton & Macagno 2007, pp. 3–8; Harrell 2010, pp. 19–21
  11. 11.0 11.1 Beardsley 1950
  12. Harrell 2010, p. 28
  13. For example: Hoffmann & Borenstein 2013; Hoffmann 2015
  14. Whately 1834 (first published 1826)
  15. Wigmore 1913
  16. Goodwin 2000
  17. Toulmin 2003 (first published 1958)
  18. 18.0 18.1 Simon, Erduran & Osborne 2006
  19. Böttcher & Meisert 2011; Macagno & Konstantinidou 2013
  20. Reed, Walton & Macagno 2007, p. 8
  21. Reed, Walton & Macagno 2007, p. 9
  22. Thomas 1997 (first published 1973)
  23. 23.0 23.1 Snoeck Henkemans 2000, p. 453
  24. Scriven 1976
  25. Beardsley 1950, p. 21
  26. Reed, Walton & Macagno 2007, p. 10–11
  27. van Eemeren et al. 1996, p. 175
  28. van Gelder 2007
  29. Berg et al. 2009
  30. Walton 2013, p. 11
  31. 31.0 31.1 Scheuer et al. 2010
  32. Holmes 1999; Horn 1998 and Robert E. Horn, "Infrastructure for navigating interdisciplinary debates: critical decisions for representing argumentation", in Kirschner, Buckingham Shum & Carr 2003, pp. 165–184
  33. 33.0 33.1 Kirschner, Buckingham Shum & Carr 2003; Okada, Buckingham Shum & Sherborne 2014
  34. For example: Bex 2011
  35. For example: Verheij 2005; Reed, Walton & Macagno 2007; Walton 2013
  36. Hilbert 2009
  37. Twardy 2004; Álvarez Ortiz 2007; Harrell 2008; Yanna Rider and Neil Thomason, "Cognitive and pedagogical benefits of argument mapping: LAMP guides the way to better thinking", in Okada, Buckingham Shum & Sherborne 2014, pp. 113–134; Dwyer 2011; Davies 2012
  38. Carrington et al. 2011; Kunsch, Schnarr & van Tyle 2014
  39. Álvarez Ortiz 2007, pp. 69–70 et seq
  40. Bex et al. 2013

References

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

Further reading

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

External links

Argument mapping software

Online, collaborative software