Was thinking about whole-rule templates, wanted to run some ideas.
Would we assume that templates like this would generally only be used
with tooling? ie not so much with plain text editors?
If so, then why not use some well formed document for a template:
<template>Some text <field type='int' id='f1'/> here </template>
To use, the data is simply the same, but with a value filled in the
"field" tag. This is easy to parse, and easy to build GUI for.
We can then use MVEL templating to render the values from the "field"
tags into an actual rule.
Alternative is a more DSL like approach where the text goes through a
proper parser (like you have been working on).
I just wanted to give the Drools community a heads-up that the
OSWorkflow community might be merging with us - not confirmed yet, but
their project lead is keen. Our unified process work has matured and we
are now very close to having a migration path for OSWorkflow users, who
are keen to migrate to an actively maintained project. We've spoken to
Diego Naya Lazo, the project lead and author of the OSWorkflow Book
http://www.infoq.com/articles/naya-lazo-osworkflow, and he is liasing
with his community to see if they are happy to move forward with this.
The Drools process stuff also needs a name, as sub project - remember we
have total unification and integration between the rules and process
(see blog http://blog.athico.com/search/label/Rule%20Flow). So we can
either go down generic routes - Drools Flow, Drools Rules, Drools
Events. Or have something a bit more fun Drools Meastro, Drools X,
Drools Fusion - X is there sa I don't have a fun name for the rule part.
The idea is we will split the manual up into separate books that will
start from the understanding of a person from that discipline, before
jumping deep into how the techs are integrated.
This is huge news and puts us firmly onto the path of a unified
modelling environment, and hopefully an end to the days of having to
choose and purchase separate and poorly integrated products for rules,
processes and complex event processing.
I have removed the Configuration interface and implementation and
implemented everything to use DOM and Element. I've updated all the
tests and it seems to be working:
I have not yet updated the Semantic Modules to allow DOM handler, I'll
do that tomorrow along with attempting to do a JAXB one. But hopefully
what I've done already is enough for you to do the OSWorkflow mapping.
> There are things you can do. remove the agenda, but make sure all node
> memories are iterated in lifo order - thus propagations will happen in
> approximate lifo, but fire straight away. Make sure the network building
> orders according to salience. You can then do an adapter algorithm that
> chooses to store or not store partial matches, based on demands of the
> problem. It isn't hard to write a network that can lazily pull all the
> joins from parent nodes (ala leaps) if there are no partial matches -
> thus creating a hybrid algorithm.
Thank you very much for your fast reply, it helps a lot!
If it causes not too much trouble and you find time for this, I would like to ask you if you have more information (weblinks, reports, etc.) on these algorithms or their implementations and commercial use.
It's quite hard to find recent reports (or reports at all), it seems all the theoretical work has been done long ago and further development only happens in commercial products.
Thank you very much!
Jeden Monat 1 hochkarätiger maxdome-Blockbuster GRATIS!
Exklusiv für alle WEB.DE Nutzer. http://www.blockbuster.web.de
I noticed that the Leaps algorithm implementation is not existent any more in version 4.x.
I would like to know the reason for discontinuing Leaps support.
Were there performance or implementation problems?
Background: I'm working on my Master's Thesis about pattern matching algorithms for rule based multiagent systems.
Main motivation is to find an efficient algorithm that needs less space than Rete.
Because Leaps claims to be far more efficient than Rete it is very interessting for me why you kept Rete and discarded Leaps.
Thank you in advance.
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!