Creating statement and argument nodes
This section describes how the Argdown parser decides which statements and arguments are represented as nodes in the generated argument map and how you can change this behaviour.
In general, all arguments with at least one relation are added as nodes to the argument map. But you can also be more selective. For example, you might want to create a map with arguments from a certain section or with a certain tag.
The default rules that decide which statements will get their own node are more complicated. The Argdown parser tries to keep the number of statement nodes as low as possible to support visualizing complex debates with many arguments in comparartively compact maps. For example, this allows you to "hide" unimportant premises in your arguments and only introduce the premises you really care about as nodes in your map.
Choose your own style
In this respect Argdown distinguishes itself from many argument mapping tools that represent arguments only as "inference nodes" that link different premises together. Such tools force you to represent every statement as a node in your map. This becomes quickly overwhelming and unmanagable in complex debates (at least if you reconstruct every argument's premise-conclusion-structure in detail).
In contrast, Argdown lets you choose what you want to emphasize in your map. You can even choose to only add the central thesis of the debate to your map and otherwise only visualize arguments. This is a good choice for complex debates. On the other hand, for small debates, you might prefer the "oldschool" style of argument mapping that represents each statement as its own node in the map. By using the all-mode it is easy to do so.
The selection process is divided up into two phases:
Selection round: In the selection round, it is checked in which relations these preselected elements stand to other preselected elements. This is the round in which the
excludeDisconnected setting and the
statementSelectionMode are applied. It is also the round in which you can choose to include "extra" statements from the preselection with the
includeStatements setting or the
Let us start with the latter, as this is the round that is excluding arguments and statements by default, even if you do not change any settings.
In contrast, the preselection round will only exclude statements or arguments, if you explicitely tell it to do so by using the selection settings or the
isInMap data flag.
excludeDisconnected selection setting
By default only statements and arguments are represented by nodes in the argument map that are considered to be connected to another node in the map. A statement counts as connected, if its equivalence class is.
An equivalence class is considered to be connected if at least one of the following conditions applies:
- It is used in a preselected argument's premise-conclusion-structure as premise or conclusion.
- It has at least one relation to a preselected element.
An argument is considered to be connected if at least one of the following conditions applies:
- The argument itself is directly related to another preselected element.
- A premise is supported/attacked by another preselected element.
- The main conclusion is supporting/attacking another preselected element.
- An inference is undercut by a preselected element.
- Support by equivalence: a premise is equivalent with a main conclusion or the main conclusion is equivalent with a premise of another preselected argument.
The exclusion of disconnected statements from the map allows you to comment on your reconstruction by adding meta-statements in the Argdown text without 'polluting' your argument map with them. If you want to disable this feature you can use the
excludeDisconnected: false selection setting:
Click on the map button in the top right to see these three sad arguments appearing in the map.
The Argdown parser supports several different general methods to exlude equivalence classes from the selection. You can change the method used by choosing a
statementSelectionMode in the selection settings. This section describes the different modes currently supported.
Managing complexity in your map
In contrast to arguments, not all preselected and connected equivalence classes will appear as statement nodes in the map. While you can easily change this behaviour, it is quite important to keep the number of statement nodes in your map as low as possible.
If you include all statements of a a complex debate as nodes in your map, it will become overcrowded and readers will have difficulty to stay orientated. Choosing which statements you visualize as nodes in your map is a crucial method of managing complexity.
In three special cases, any of the modes described further below will not exclude equivalence classes:
Equivalence classes that will be selected as nodes by all modes
The third case may need an explanation: Relations of such equivalence classes can not be represented by edges of argument nodes, so it is important to represent them with statement nodes or they will be lost. In most cases you will want to include them in your map.
Now let's take a look at what the different modes are doing:
Includes each equivalence class that is connected to a preselected element (argument or statement).
Excludes any equivalence class that is used in an argument (as premise or conclusion).
with-title mode (default mode)
Excludes any equivalence class that is anonymous (has no title).
Excludes any equivalence class that has no relations.
Excludes any equivalence class that has less than two relations.
Excludes any equivalence class that is not used as top-level block element. See the introduction of the syntax documentation for the definition of a top-level block element.
Selecting nodes by tag
You can use the
selectedTags selection setting to preselect only those arguments and statements for further selection which are tagged with any of the chosen hashtags.
Only t1, a and c are selected. You can choose to also include statements or arguments without any tags by using the
Now argument f is included in the map, even though it is not tagged as well. You may have noticed that not all arguments with the #pro tag were selected. Argument e is missing from the map.
The reason is once again that disconnected nodes are excluded from the map. Argument e's only connection is to d, but d is neither tagged with the #pro tag nor is it without any tags (it is tagged with the #con tag). As a result, it is excluded from the map. This leaves e disconnected. So it is excluded as well.
Selecting nodes by section
You can use the
selectedSections selection setting to preselect only those arguments and statements for further selection, that are members of chosen sections. See the section on creating groups to learn more about sections.
You can choose to also include statements or arguments without any section by using the
Note, that argument b is excluded, even though it is used outside of any section. This is because b is defined first in section H2 and sections are by default assigned by their first definition. For more about how sections are assigned see creating groups.
Selecting nodes by title
You can use the
excludeArguments selection settings to include or exclude elements by title.
Note that argument b, which would normally appear in the map together with t3, is now also excluded, because its only connection was to t3. Because t3 is excluded b is now disconnected and falls victim to the
excludeDisconnected default policy.
Why is there not also an
includeArguments setting? It is not needed because by default all connected arguments are added as nodes to the map. In contrast, only connected statements selected by the statementSelectionMode are added by default to the map. The
includeStatements setting includes additional statements to the map that were not added by the statementSelectionMode.
Selecting nodes with the
isInMap data flag
You can also pick single arguments or statements for the map by using the
isInMap data flag directly in the Argdown code:
The downside of this method is that you add map-specific data to elements in your Argdown document, thereby making it more difficult for others to change the selection and to generate a different map from the same document. This "tight coupling" of data and visualization is not recommended. If you want to pick single elements you should use the
excludeArguments selection settings instead. See the previous section for further details.
If you still prefer to use the
isInMap data flag or if you want to override the flags of other authors, you can use the
ignoreIsInMap selection setting. If set to true, all
isInMap data flags in your document will be ignored: