Yeah, I remember the exchanges from a long time ago about "else" in DRL. IIRC, Mark wasn't keen on the idea.<br><br>Anyway, provided my "reversals" make sense it's almost complete in the guided dtable; it only uses SimpleFieldConstraints so doesn't have the complexity of compound constraints :)<br>
<br><br><div class="gmail_quote">On 31 March 2011 22:20, Michael Neale <span dir="ltr"><<a href="mailto:michael.neale@gmail.com">michael.neale@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Otherwise has been dragging on since 2006. There are many skeletons in that cave. <div><br></div><div>I will believe it when I see it !<div><div></div><div class="h5"><br><br><div class="gmail_quote">On Fri, Apr 1, 2011 at 7:25 AM, Michael Anstis <span dir="ltr"><<a href="mailto:michael.anstis@gmail.com" target="_blank">michael.anstis@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">I bet Edson can't wait to refactor the parser for that ;)<div><div></div><div><br><br><div class="gmail_quote">
On 31 March 2011 21:11, Mark Proctor <span dir="ltr"><<a href="mailto:mproctor@codehaus.org" target="_blank">mproctor@codehaus.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff">
on a related note I do plan to add OTHERWISE support at a DRL level,
just no time to do it right now. Once it's supported at a DRL level,
you won't need to as much work on figuring out the inverse options
etc.<br>
<br>
Mark<div><div></div><div><br>
On <a href="tel:31%2F03%2F2011%2020" target="_blank">31/03/2011 20</a>:25, Michael Anstis wrote:
</div></div><blockquote type="cite"><div><div></div><div>Hi,<br>
<br>
I'm adding support for "otherwise" to (for the time being) the
guided decision table in Guvnor.<br>
<br>
The idea being if you set a cell to represent "otherwise" the
generated rule is the opposite of the accumulation of the other
cells; perhaps best explained with an example:-<br>
<br>
<div style="margin-left: 40px;"><span style="font-family: courier new,monospace;">Person( name == )</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">Mark</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">Kris</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">Geoffrey</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"><otherwise></span><br style="font-family: courier new,monospace;">
</div>
<br>
This would generate:-<br>
<br>
<span style="font-family: courier new,monospace;">Person(name not
in ("Mark", "Kris", "Geoffrey")</span><br style="font-family: courier new,monospace;">
<br>
Equals is the simple example, this is my thoughts for the other
operators we might like to support:-<br>
<ul>
<li>!= becomes "in (<list of the other cells' values)"</li>
<li>< becomes ">= the maximum value of the other cells'
values</li>
</ul>
<br>
<div style="margin-left: 40px;">For example:-<br>
<br>
<span style="font-family: courier new,monospace;">Person ( age
< )</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">10</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">20</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">30</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"><otherwise></span><br style="font-family: courier new,monospace;">
<br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">Person ( age
>= 30 )</span></div>
<br>
<ul>
<li><= becomes "> the maximum value of the other cells'
values</li>
<li>> becomes "<= the minimum value of the other cells'
values</li>
<li>>= becomes "< the minimum value of the other cells'
values</li>
<li>"in" becomes "not in (<a list of all values contained in
all the other cells' lists of values>)"</li>
</ul>
<div style="margin-left: 40px;">For example:-<br>
</div>
<br>
<div style="margin-left: 40px;">
<span style="font-family: courier new,monospace;">Person ( name
in )</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">Jim, Jack</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">Lisa, Jane,
Paul</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"><otherwise></span><br style="font-family: courier new,monospace;">
<br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">Person ( name
not in ("Jim", "Jack", "Lisa", "Jane", "Paul" ) )</span><br>
<br>
</div>
<ul>
<li>I'm not sure there is a simple solution for "matches" and
"soundslike" but welcome advice, although a possibility might
be to create a compound field constraint:-<br>
</li>
</ul>
<div style="margin-left: 40px;">
<span style="font-family: courier new,monospace;">Person ( name
soundslike )</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">Fred</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">Phil</span><br style="font-family: courier new,monospace;">
<br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">not Person (
name soundslike "Fred" || soundslike "Phil" )</span><br style="font-family: courier new,monospace;">
</div>
<br>
<br>
Would this be considered the most suitable approach?<br>
<br>
Inputs and thoughts welcome.<br>
<br>
Thanks,<br>
<br>
Mike <br>
<br>
</div></div><pre><fieldset></fieldset>
_______________________________________________
rules-dev mailing list
<a href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a>
</pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
<br></blockquote></div><br>
</div></div><br>_______________________________________________<br>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
<br></blockquote></div><br><br clear="all"><br></div></div>-- <br>Michael D Neale<br>home: <a href="http://www.michaelneale.net" target="_blank">www.michaelneale.net</a><br>blog: <a href="http://michaelneale.blogspot.com" target="_blank">michaelneale.blogspot.com</a><br>
</div>
</blockquote></div><br>