Argument map

From Wikipedia, the free encyclopedia
A schematic argument map showing a contention (or conclusion), supporting arguments and objections, and an inference objection

An argument map or argument diagram is a visual representation of the structure of an argument. An argument map typically includes all 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, two other kinds of node–link diagram which have different constraints on nodes and links.[4]

Key features[edit]

A number of different kinds of argument maps have been proposed but the most common, which Chris Reed and Glenn Rowe called the standard diagram,[5] 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.[5] Another variation diagrams an argument from left to right.[6]

According to Douglas N. 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..."[7] 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,[8] 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.[9]

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.[10]

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.[11]

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 contention is shown at the top, and the boxes linked to it represent supporting reasons, which comprise one or more premises. The green arrow indicates that the two reasons support the contention:

A box and line diagram

Argument maps can also represent counterarguments. In the following diagram, the two objections weaken the contention, while the reasons support the premise of the objection:

A sample argument using objections

Representing an argument as an argument map[edit]

Diagramming written text[edit]

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:[12]

  1. Separate statements by brackets and number them.
  2. Put circles around the logical indicators.
  3. Supply, in parentheses, 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:[13]

  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.

Diagramming as thinking[edit]

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.[14] The use of such argument analysis for thinking through issues has been called "reflective argumentation".[15]

An argument map, unlike a decision tree, does not tell how to make a decision, but the process of choosing a coherent position (or reflective equilibrium) based on the structure of an argument map can be represented as a decision tree.[16]

History[edit]

The philosophical origins and tradition of argument mapping[edit]

From Whately's Elements of Logic p467, 1852 edition

In the Elements of Logic, published in 1826 and issued in many subsequent editions,[17] 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,[18] based in part on the ideas of 19th century philosopher Henry Sidgwick who used lines to indicate relations between terms.[19]

Anglophone argument diagramming in the 20th century[edit]

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.[12] 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,[20] identified several elements to an argument which have been generalized. The Toulmin diagram is widely used in educational critical teaching.[21][22] 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".[23] Toulmin introduced the concept of warrant which "can be considered as representing the reasons behind the inference, the backing that authorizes the link".[24]

Beardsley's approach was refined by Stephen N. Thomas, whose 1973 book Practical Reasoning In Natural Language[25] introduced the term linked to describe arguments where the premises necessarily worked together to support the conclusion.[26] However, the actual distinction between dependent and independent premises had been made prior to this.[26] 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.[27] Whereas Beardsley had said "At first, write out the statements...after a little practice, refer to the statements by number alone"[28] 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.[29] This also enabled the diagramming of "balance of consideration" arguments.[30]

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

Development of computer-supported argument visualization[edit]

The argument map tree schema of Kialo with an example path through it: all Con-argument boxes and some Pros were emptied to illustrate an example path.[32]
A partial argument tree with claims and impact votes for arguments illustrates one form of collective determination of argument weights that is based on equal-weight user voting.[33] There is research into how to efficiently calculate the winning arguments or arguments' weights and the overall conclusions in digital argument map systems.[34]

Human–computer interaction pioneer Douglas Engelbart, in a famous 1962 technical report on intelligence augmentation, envisioned in detail something like argument-mapping software as an integral part of future intelligence-augmenting computer interfaces:[35]

You usually think of an argument as a serial sequence of steps of reason, beginning with known facts, assumptions, etc., and progressing toward a conclusion. Well, we do have to think through these steps serially, and we usually do list the steps serially when we write them out because that is pretty much the way our papers and books have to present them—they are pretty limiting in the symbol structuring they enable us to use. ... To help us get better comprehension of the structure of an argument, we can also call forth a schematic or graphical display. Once the antecedent-consequent links have been established, the computer can automatically construct such a display for us.

— Douglas Engelbart, "Augmenting human intellect: a conceptual framework" (1962)

In the middle to late 1980s, hypertext software applications that supported argument visualization were developed, including NoteCards and gIBIS; the latter generated an on-screen graphical hypertextual map of an issue-based information system, a model of argumentation developed by Werner Kunz and Horst Rittel in the 1970s.[36] In the 1990s, Tim van Gelder and colleagues developed a series of software applications that permitted an argument map's premises to be fully stated and edited in the diagram, rather than in a legend.[37] Van Gelder's first program, Reason!Able, was superseded by two subsequent programs, bCisive and Rationale.[38]

Throughout the 1990s and 2000s, many other software applications were developed for argument visualization. By 2013, more than 60 such software systems existed.[39] In a 2010 survey of computer-supported argumentation, Oliver Scheuer and colleagues noted that one of the differences between these software systems is whether collaboration is supported.[40] In their survey, single-user argumentation systems included Convince Me, iLogos, LARGO, Athena, Araucaria, and Carneades; small group argumentation systems included Digalo, QuestMap, Compendium, Belvedere, and AcademicTalk; community argumentation systems included Debategraph and Collaboratorium.[40] Free and open source structured argumentation systems include Argdown[41] and Argüman.[42]

As of 2020, the commercial website Kialo is the most widely adopted argumentation-based deliberation system with an argument-map interface.[43] On Kialo, users can vote on the overall debate topic as well as on individual claims to express their perspectives or conclusions, with the rationale (i.e. the main causal arguments) why they voted on the veracity of the thesis as they did not being captured if these reasons are not located as claims beneath the argument and have also been rated by the same users.[clarification needed][44] This represents Kialo's algorithm of collective determination of argument weights and theses' veracities,[clarification needed][45] which has a plurality component in that the user can also switch between the perspectives of specific users and some groups of users (e.g. supporters and opponents of a thesis).[46] In the context of historical-political education, researcher Oliver Held identified at least five key components of historical judgment that can be implemented easily in Kialo: perspectivity, levels of relevance, interdependence, multi-causality and assessments.[47]

Applications[edit]

Argument maps have been applied in many areas, but foremost in educational, academic and business settings, including design rationale.[48] Argument maps are also used in forensic science,[49] law, and artificial intelligence.[50] 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.[51]

Difficulties with the philosophical tradition[edit]

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.[21] There appears to be little statistical effect after such classes. Argument mapping, however, has a measurable effect according to many studies.[52] For example, instruction in argument mapping has been shown to improve the critical thinking skills of business students.[53]

Evidence that argument mapping improves critical thinking ability[edit]

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.[54] The tests used in the reviewed studies were standard critical-thinking tests.

Limitations[edit]

When used with students in school, argument maps have limitations. They can "end up looking overly complex" and can increase cognitive load beyond what is optimal for learning the course content.[55] Creating maps requires extensive coaching and feedback from an experienced argument mapper.[55] Depending on the learning objectives, the time spent coaching students to create good maps may be better spent learning the course content instead of learning to diagram.[55] When the goal is to prompt students to consider other perspectives and counterarguments, the goal may be more easily accomplished with other methods such as discussion, rubrics, and a simple argument framework or simple graphic organizer such as a vee diagram.[55] To maximize the strengths of argument mapping and minimize its limitations in the classroom requires considering at what point in a learning progression the potential benefits of argument mapping would outweigh its potential disadvantages.[55]

A 2022 security studies blog post said that "Kialo's simplicity does pose some weaknesses and limitations, and in general current [computer-supported argument visualization] systems cannot reliably automate analysis or synthesis of arguments in the same way that statistical packages can automate analysis of data".[56]

Standards[edit]

Argument Interchange Format[edit]

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.[57] 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.[58]

Legal Knowledge Interchange Format[edit]

The Legal Knowledge Interchange Format (LKIF)[59] was developed in the European ESTRELLA project[60] and 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.

Argdown[edit]

Argdown is a Markdown-inspired lightweight markup language for complex argumentation.[41] It is intended for exchanging arguments and argument reconstructions in a universally accessible and highly human-readable way. The Argdown syntax is accompanied by tools that facilitate coding and transform Argdown documents into argument maps.[61]

See also[edit]

Notes[edit]

  1. ^ Freeman 1991, pp. 49–90
  2. ^ For example: Davies 2012; Facione 2016, pp. 88–112; Fisher 2004; Kelley 2014, p. 73; Kunsch, Schnarr & van Tyle 2014; Walton 2013, p. 10; van Gelder 2015
  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. ^ For example: Davies 2010; Hunter 2008; Okada, Buckingham Shum & Sherborne 2014, pp. vii–x, 4
  5. ^ a b Reed & Rowe 2007, p. 64
  6. ^ For example: Walton 2013, pp. 18–20
  7. ^ Reed, Walton & Macagno 2007, p. 2
  8. ^ Freeman 1991, pp. 49–90; Reed & Rowe 2007
  9. ^ Harrell 2010, p. 19
  10. ^ Freeman 1991, pp. 91–110; Harrell 2010, p. 20
  11. ^ Beardsley 1950, pp. 18–19; Reed, Walton & Macagno 2007, pp. 3–8; Harrell 2010, pp. 19–21
  12. ^ a b Beardsley 1950
  13. ^ Harrell 2010, p. 28
  14. ^ This is related to the distinction between "knowledge telling" and "knowledge transforming" in composition studies: see, for example, Chryssafidou 2014, pp. 38–39, 413
  15. ^ For example: Hoffmann & Borenstein 2013; Hoffmann 2016; Hoffmann 2018
  16. ^ See section 4.2, "Argument maps as reasoning tools", in Brun & Betz 2016
  17. ^ Whately 1834 (first published 1826)
  18. ^ Wigmore 1913
  19. ^ Goodwin 2000
  20. ^ Toulmin 2003 (first published 1958)
  21. ^ a b Simon, Erduran & Osborne 2006
  22. ^ Böttcher & Meisert 2011; Macagno & Konstantinidou 2013
  23. ^ Reed, Walton & Macagno 2007, p. 8
  24. ^ Reed, Walton & Macagno 2007, p. 9
  25. ^ Thomas 1997 (first published 1973)
  26. ^ a b Snoeck Henkemans 2000, p. 453
  27. ^ Scriven 1976
  28. ^ Beardsley 1950, p. 21
  29. ^ Reed, Walton & Macagno 2007, pp. 10–11
  30. ^ van Eemeren et al. 1996, p. 175
  31. ^ Holmes 1999; Horn 1998; Robert E. Horn, "Infrastructure for navigating interdisciplinary debates: critical decisions for representing argumentation", in Kirschner, Buckingham Shum & Carr 2003, pp. 165–184
  32. ^ Bolton et al. 2020
  33. ^ Durmus, Ladhak & Cardie 2019
  34. ^ Young 2021
  35. ^ Engelbart 1962; For an account of Engelbart's place in the history of computer-supported argument visualization, see, e.g., Simon Buckingham Shum, "The roots of computer supported argument visualization", in Kirschner, Buckingham Shum & Carr 2003, pp. 3–24
  36. ^ Conklin & Begeman 1988, on gIBIS; Halasz 1988, on NoteCards; Kirschner, Buckingham Shum & Carr 2003, pp. 14–15, on the place of both in the history of computer-supported argument visualization
  37. ^ van Gelder 2007
  38. ^ Berg et al. 2009
  39. ^ Walton 2013, p. 11
  40. ^ a b Scheuer et al. 2010
  41. ^ a b See Voigt 2014. The Argdown website is argdown.org. Argdown is currently developed as an open source project: "christianvoigt/argdown: a simple syntax for complex argumentation". GitHub.com. Retrieved 2019-10-30.
  42. ^ Pührer 2017
  43. ^ De Liddo & Strube 2021
  44. ^ Carroll, Sun & Beck 2019
  45. ^ Durmus, Ladhak & Cardie 2019
  46. ^ Beck, Neupane & Carroll 2019
  47. ^ Held 2022
  48. ^ Kirschner, Buckingham Shum & Carr 2003; Okada, Buckingham Shum & Sherborne 2014
  49. ^ For example: Bex 2011
  50. ^ For example: Verheij 2005; Reed, Walton & Macagno 2007; Walton 2013
  51. ^ Hilbert 2009
  52. ^ 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
  53. ^ Carrington et al. 2011; Kunsch, Schnarr & van Tyle 2014
  54. ^ Álvarez Ortiz 2007, pp. 69–70 et seq
  55. ^ a b c d e Nussbaum 2012, pp. 125, 133
  56. ^ Durland 2022
  57. ^ See the AIF original draft description (2006) and the full AIF-RDF ontology specifications in RDFS format.
  58. ^ Bex et al. 2013
  59. ^ Boer, Winkels & Vitali 2008
  60. ^ "Estrella project website". estrellaproject.org. Archived from the original on 2016-02-12. Retrieved 2016-02-24.
  61. ^ Argdown tools include a web browser sandbox editor, an extension for Visual Studio Code, and a command-line tool; see "Getting started". argdown.org. Retrieved 2019-10-30.

References[edit]

Further reading[edit]