DMNFTF — Stick with own definition of terms in all cases

Since DMN is a standard (and in particular claims to be a business standard), then it must stick with its own definition of terms in all cases. Otherwise, in what sense is it a standard (especially a business standard)?

In defining “decision” DMN had two fundamental choices (from Merriam-Webster Unabridged dictionary):

1. a : the act of deciding; specifically : the act of settling or terminating (as a contest or controversy) by giving judgment

1. b : a determination arrived at after consideration : SETTLEMENT, CONCLUSION

DMN explicitly chose the first meaning. I strongly prefer the second, but then I’m a big fan of all things declarative. So in BRS TableSpeak an outcome by definition is a decision.

Since DMN explicitly chose the first meaning, however, an outcome (conclusion) is by definition not a decision. A decision is an act, never the result of the act.

If DMN somehow allows ‘overloading’ of the term “decision” – the central term in the standard – all bets are off. For example I have read elsewhere that the 'output' of a decision can be treated as a decision in DMN.

A term that you can use any way you want when it happens to suit you is a term that has not been standardized at all.

This comment appears to have been made against an earlier draft.
After review of the current beta draft, the task force believes the definition of decision as an act of choosing among possible options is the correct definition, and is consistent with the current text. This captures the notion of applying decision logic in the making of a decision.