• Joseph Potvin @joseph_potvin ·

    To keep the rule.xa logic gate structure always to be seen as a bilattice, we have to specify Input Condition rows and Output Assertion rows. It's fine to represent only the Input Condition section for discussion of that, so we ensure it's labelled as such.

    Edited by Joseph Potvin
  • it is not clear why the result has "x" : 31, instead of "x" : 33.

    Typo.

  • That's to say, in the "Context" section, the rule table should be labelled "Input Conditions".

    These are just discussions. I'd do that for something that we'd publish on the development site.

  • This conversation has been significantly rewritten based partly on the comments as well as other conversations. Best to ignore the preceding comments.

  • Joseph Potvin @joseph_potvin ·

    I am trying to imagine being a rule author using RM to write sentences that resolve to:

    "x" : "[4d4673b6-3f5d-499b-a87e-468bd0b2c268]" 01 10 01

    "x" : "==a" 10 00 01

    What would the first sentence look like?

    Edited by Joseph Potvin
  • Joseph Potvin @joseph_potvin ·

    My preference is to let the rule author refer to some variable "x" and immediately indicate where that information would come from. Analogous to an iframe, but for a sentence of a rule: the external data is pulled into the sentence by RuleTaker.

    Edited by Joseph Potvin
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment