Sure. I am working on this alone for now, so a reasonable delay is not an issue.
Tonino On 2024/03/04 15:26:01 Alex Porcelli wrote: > Toni, > > Although you mentioned that it's quite isolated, I feel more > comfortable if we could delay to introduce it to the codebase after > the 10.0.0 release - in the meantime maybe use a feature branch > directly in the Apache repository. > > On Mon, Mar 4, 2024 at 10:15 AM Toni Rikkola <[email protected]> wrote: > > > > Future goals can include having YaRD next to SonataFlow. Allowing easy > > access to Decision Tables and other Decision logic that is not easy to > > implement with a flow structure and of course the other way around. > > > > However there are also other targets. One method is to use the YaRD files > > as scorecards. Based on the inputs the end result gives a % of success. > > > > YaRD can also be used to aggregate several REST calls into a one more > > preferable format. > > > > Toni > > > > On 2024/03/04 14:27:07 Yeser Amer wrote: > > > Hi Tonino! > > > > > > Thanks for sharing a brief description of YaRD here. > > > I agree with you that having the editor in kie-tools (apache) and the > > > engine in another area (kie?) is not ideal. > > > > > > Can I ask where the code is currently located? > > > Since you said the feature is "experimental", can I ask what the plans > > > are for YaRD? > > > I think clarifying this point can help us make the best decision. > > > > > > > > > On 2024/03/04 13:53:07 Alex Porcelli wrote: > > > > Toni, > > > > > > > > As in previous discussion related to the new Drools parser, my concern > > > > is how much this might affect the 10.0.0 release. > > > > > > > > I personally am not a big fan of YAML, in a recent demo I got in > > > > trouble because of 2 spaces :D - but I understand that this might look > > > > appealing to k8s audience :) > > > > > > > > On Mon, Mar 4, 2024 at 8:23 AM Toni Rikkola <[email protected]> wrote: > > > > > > > > > > Hello, > > > > > > > > > > I am proposing we add YaRD into the kie-drools repository. YaRD is > > > > > used > > > > > to describe Decisions, Rules and Declarative logic in the YAML format. > > > > > At the current state it supports Decision Tables and Literal > > > > > Expressions. > > > > > > > > > > Example of a Decision Table is in attached file > > > > > "yard-dtable-example.txt". ( In .txt for easier viewing. ) > > > > > A more complex example is in attached "costs.txt". > > > > > > > > > > The YAML structure and the used scripting language is not set in stone > > > > > and the feature at the moment is experimental. > > > > > > > > > > Under the YAML cover it runs Drools, in more detail the Drools Rule > > > > > Units DSL. > > > > > > > > > > Due to the move to Apache we are in a weird situation where we already > > > > > have an editor for YaRD in kie-tools without a backend. The existing > > > > > editor has a simple autocomplete with support for Validation that > > > > > finds > > > > > redundancy and subsumption from the Decision Tables. To follow the > > > > > Apache community rules and to show visibility I am now asking for > > > > > approval to add the backend in. > > > > > > > > > > Thank you > > > > > Toni Rikkola > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [email protected] > > > > > For additional commands, e-mail: [email protected] > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [email protected] > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
