headers
Adrian Paschke | 2 Jun 23:20
Picon
Favicon

[rules-dev] RuleML-2008: Deadline Extension

[ our apologies should you receive this message more than one time ]

=====================================================================
Due to a number of requests we have to decided to extend
the submission deadline by 2 weeks.

         NEW deadline for paper/demo submission: June 16
=====================================================================

            2008 International RuleML Symposium
       on Rule Interchange and Applications (RuleML-2008)

          October 30-31, 2008, Orlando, Florida
               http://2008.ruleml.org

--------------------------------------------------------------------
RuleML-2008 Highlights:

- Keynote speakers:
  * Michael Kifer (State University of New York at Stony Brook, USA),
    on "Rule Interchange Format: Not Just Syntax".
    Joint keynote between RuleML-2008 and RR2008.
  * David Luckham (Stanford University, USA) on complex event processing.
  * Paul Haley (Haley Ltd) on business rules.
  * Benjamin Grosof (Vulcan Inc, USA) on the SILK KRR system of the HALO
    project.
  (Details at: http://2008.ruleml.org/keynote.php )
- Joint Lunch Panel with the Business Rules Forum about "Rules on the Web"
- RuleML-2008 Challenge with prestigious prices
  (Details at: http://2008.ruleml.org/challenge.php )
(Continue reading)

Permalink | Reply | 2 comments |
headers
stuntman-mike | 4 Jun 10:15
Picon

[rules-dev] Leaps Match Algorithm discontinuation

Hello,

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.

Regards, E.L.
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066

_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
Permalink | Reply | 1 comment |
headers
Mark Proctor | 4 Jun 14:38

Re: [rules-dev] Leaps Match Algorithm discontinuation

stuntman-mike <at> web.de wrote:
> Hello,
>
> 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?
>   
The developer who was working on it lost interest. With no one to 
maintain it, we discontinued it. While manners performaned well, it had 
performance issues for waltz.
> 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.
>   
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 in advance.
>
> Regards, E.L.
> _____________________________________________________________________
> Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
> http://smartsurfer.web.de/?mc=100071&distributionid=000000000066
(Continue reading)

Permalink | Reply | 0 comments |
headers
stuntman-mike | 5 Jun 10:50
Picon

Re: [rules-dev] Leaps Match Algorithm discontinuation

mproctor <at> codehaus.org wrote:
> 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!

Regards, E.L.

______________________________________________________________
Jeden Monat 1 hochkarätiger maxdome-Blockbuster GRATIS!
Exklusiv für alle WEB.DE Nutzer. http://www.blockbuster.web.de

_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
Permalink | Reply | 501 comments |
headers
Mark Proctor | 5 Jun 14:32

Re: [rules-dev] Leaps Match Algorithm discontinuation

stuntman-mike <at> web.de wrote:
mproctor <at> codehaus.org wrote:
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.
Just use google scholar search. KBSC also have a page of links to useful papers:
http://kbsc.com/aibooks.html
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.
Yes it seems all the interesting research was done in the 90s and then it just stops. This is partly due to the commercialisation of production systems and partly due to academia only being interested in prolog engines. While production engines have the performance, which business are interested in, academia go for prolog which they can do complete proofs in, so their research is focused there.
Thank you very much! Regards, E.L. ______________________________________________________________ Jeden Monat 1 hochkarätiger maxdome-Blockbuster GRATIS! Exklusiv für alle WEB.DE Nutzer. http://www.blockbuster.web.de _______________________________________________ rules-dev mailing list rules-dev <at> lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev 

_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
Permalink | Reply | 501 comments |
headers
Mark Proctor | 6 Jun 04:39

[rules-dev] Dom element for ExtensibleXmlReader

Krisv,

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:
http://jira.jboss.com/jira/browse/JBRULES-1634

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.

Mark
_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
Permalink | Reply | 0 comments |
headers
Mark Proctor | 6 Jun 16:30

[rules-dev] Possible OSWorkflow Merger

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.

Mark
_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
Permalink | Reply | 0 comments |
headers
Michael Neale | 10 Jun 14:26
Picon
Gravatar

[rules-dev] simple templates

Hi Matt.
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.

Thoughts?

Alternative is a more DSL like approach where the text goes through a
proper parser (like you have been working on).

Michael.
_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
Permalink | Reply | 0 comments |
headers
mkisker | 10 Jun 15:01

[rules-dev] Mike Kisker is out of the office.

I will be out of the office starting 06/07/2008 and will not return until 06/12/2008.

I will respond to your message when I return.

_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
Permalink | Reply | 0 comments |
headers
Mark Proctor | 13 Jun 16:54

[rules-dev] sub project names

I'm in the process of splitting drools up into sub projects and looking 
for feed on names. Each sub project will have it's own manual.

Drools the Business Logic integration Platform
-----------------------------------------------

Drools Expert
This is the expert system rule engine, as you expect from Drools 4.0 
now, Ruleflow has moved to the Flow project

Drools Flow
This is becoming a full blown workflow and process engine and includes 
the ruleflow work for rule engine integration

Drools Fusion
Temporal Reason system providing CEP capabilities. The syntax is an 
orthogonal extension to the DRL. While it could possible live as a 
chapter in the "Drools Expert" manual we expect there will be enough 
information on adapters and integration and general theory to justify 
its own sub project.

Drools Guvnor
This is the Guvovernance system for Drools and all it's sub projects. 
It's still primarily a BRMS, but we are trying to expand it to provide a 
governance platform for processes and cep too, which will be a long term 
effort post 5.0

Mark

_______________________________________________
rules-dev mailing list
rules-dev <at> lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
Permalink | Reply | 1 comment |

Gmane