| Huh, I haven't thought of using them as an input format, a form that matches the typical structure of a discussion. Thanks! > I think they expect you to draft the argument map, then go back over it and iteratively reduce it by manually normalizing duplicate sub-arguments into one canonical sub-argument in one place + references to it in other places. That can work with this application/language. It doesn't work with Kialo, unfortunately, where you had different people contributing different nodes of the tree and AFAIR maybe, sometimes, someone then going over the tree and cleaning it up. > Then, once you have captured that structure, (...) massage (refactor!) the discussion (...) into one that lets you more efficiently get at the truth. One thing I tried to say is that I believe an argument tree isn't a right end format here, both because it's about arguments (vs. facts and their relationships), and because it's a tree. I think the end format must be a directed graph, very likely containing cycles (mutually supporting arguments). Why I don't like arguments in the final format? Because they're kind of like an applied function. They hide the parameters. You can decompose an individual argument into pieces of facts and their relationships; an argument takes those, and assigns hidden weights to them - you care about some facts and relationships more than others, and this is usually implicit in the argument (and a source of confusion when doing this multiplayer, a-la Kialo). I think it'll be more productive to decompose the arguments and deduplicate the resulting graph, and then work at the facts-and-relationships level. The benefits are that all components are now much easier to objectively verify, and whatever conclusion you then read out of this graph could be validated easier. Note I just think that it'll work better, I haven't really tried it. I have on my TODO list somewhere to take a particular nontrivial topic, like e.g. "animal suffering"[0], and try to decompose it this way to see whether this format will actually work in practice. -- [0] - It's a topic on which I have no formed opinion at this point, only bunch of inconsistent feelings and heuristics, so I shouldn't have too many preconceptions and biases here. It also seems hard enough to teach me something about myself. |
Can you clarify what you mean with cycles? As written it sounds like you think sound arguments contain circular reasoning...
I can see a branching opening and closing in a unidirected graph being the result of a sound argument^, but since you cannot move freely in both directions I don't know if it would count as a cycle.
^ The argument being: some process has a positive an negative effect (one thing happens, another thing never happens), the positive and negative effects are observed in nature, supporting the conclusion that the process in fact is the cause of the two effects.