"Decision" node type needs a sub-component type (like "positions")

A decision may have many aspects which in some cases would be better explained using sub-components much like positions are sometimes explainied using the "component" node type. Each component may have its own list of tasks.

RELATED ARTICLESExplain
DebateGraph Community
Development Ideas
Improving existing features?
Idea types and relationships?
"Decision" node type needs a sub-component type (like "positions")
Argument structuring could be improved
Clarify the use of argument groups
Moves may create type inconsistencies
Part arguments were a useful measure against cluttered views
Graph of this discussion
Enter the title of your article


Enter a short (max 500 characters) summation of your article
Enter the main body of your article
Lock
+Comments (1)
+Citations (0)
+About
Enter comment

Select article text to quote
welcome text

First name   Last name 

Email

Skip