Issue54

Title restrict derived variables to binary domains
Priority wish Status chatting
Superseder Nosy List jendrik, malte
Assigned To Keywords translator
Optional summary
Part of the axiom meta-issue issue924.

Created on 2009-12-03.17:47:47 by malte, last changed by malte.

Summary
Part of the axiom meta-issue issue924.
Messages
msg11148 (view) Author: malte Date: 2023-07-21.14:22:36
Updated the title of the issue: we now commit to restricting derived variables to binary (true/false) domains. This needs to be enforced at the code level and documented, and we should point out somewhere (in the code is perhaps enough) that this differs from the AIJ translator paper.

To simplify things, I think we should then also make clear which of the two domain values stands for "false" and which one stands for "true". (This matters for negation-by-failure semantics.)
msg3355 (view) Author: malte Date: 2014-08-27.15:10:00
See issue458.
msg152 (view) Author: malte Date: 2009-12-03.17:47:47
The AIJ translator paper associates layers with axiom *rules*, not with axiom
*variables*. This is more general because it allows for non-binary derived
variables. (In our implementation's version, non-binary derived variables would
either be trivial, i.e. certain values could never be achieved, or they'd
violate the layering property in the AIJ translator paper.)

For people who directly generate FDR tasks rather than go through our
translator, we should either support the more general case, or at least properly
document the restriction of derived variables to the binary case.
History
Date User Action Args
2023-07-21 14:22:36maltesettitle: axiom support differs from what is described in the AIJ translator paper -> restrict derived variables to binary domains
messages: + msg11148
summary: Part of the axiom meta-issue issue924.
2014-10-04 19:50:17maltesetkeyword: + translator
2014-08-27 15:10:00maltesetmessages: + msg3355
2009-12-03 17:47:47maltecreate