<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.java.drools.devel">
    <title>gmane.comp.java.drools.devel</title>
    <link>http://blog.gmane.org/gmane.comp.java.drools.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5716"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5715"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5714"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5713"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5712"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5711"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5710"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5709"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5708"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5707"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5706"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5705"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5704"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5703"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5702"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5701"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5700"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5699"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5698"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.java.drools.devel/5697"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5716">
    <title>Re: [rules-dev] 2 very useful github tips</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5716</link>
    <description>&lt;pre&gt;Very handy, tnx for sharing

--
View this message in context: http://drools.46999.n3.nabble.com/2-very-useful-github-tips-tp4013589p4013649.html
Sent from the Drools: Developer (committer) mailing list mailing list archive at Nabble.com.
_______________________________________________
rules-dev mailing list
rules-dev&amp;lt; at &amp;gt;lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev

&lt;/pre&gt;</description>
    <dc:creator>ge0ffrey</dc:creator>
    <dc:date>2012-05-24T14:34:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5715">
    <title>Re: [rules-dev] 2 very useful github tips</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5715</link>
    <description>&lt;pre&gt;You've changed my life :) The cool thing is it works faster than most of
the IDEs out there

On Thu, May 24, 2012 at 10:56 AM, Mario Fusco &amp;lt;mario.fusco&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:



&lt;/pre&gt;</description>
    <dc:creator>Mauricio Salatino</dc:creator>
    <dc:date>2012-05-24T13:58:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5714">
    <title>Re: [rules-dev] 2 very useful github tips</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5714</link>
    <description>&lt;pre&gt;Thanks Edson,

very useful findings (especially the 2nd one for me).

Mario

On Thu, May 24, 2012 at 3:54 PM, Edson Tirelli &amp;lt;ed.tirelli&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:

_______________________________________________
rules-dev mailing list
rules-dev&amp;lt; at &amp;gt;lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
&lt;/pre&gt;</description>
    <dc:creator>Mario Fusco</dc:creator>
    <dc:date>2012-05-24T13:56:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5713">
    <title>[rules-dev] 2 very useful github tips</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5713</link>
    <description>&lt;pre&gt;   Was watching a presentation yesterday from Zack Holman (&amp;lt; at &amp;gt;holman) and he
presented 2 very useful tricks on github:

* on any page in a repository, press "t" on your keyboard and start typing
the name of a file and it will find the file for you. Same as ctrl+t/ctrl+r
on Eclipse. I use this all the time. Press "?" for a list of all keyboard
shortcuts.

* on a diff/commit page, add "?w=1" at the end of the URL to make the diff
ignore whitespaces. Very useful for those commits where people are using a
different code format.

   Edson

&lt;/pre&gt;</description>
    <dc:creator>Edson Tirelli</dc:creator>
    <dc:date>2012-05-24T13:54:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5712">
    <title>[rules-dev] Functional Programming in Drools</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5712</link>
    <description>&lt;pre&gt;Hi all,

similarly to what Edson did with his Event Sequencing specs, I modified and
enriched my draft proposal about Functional Programming in Drools:

https://community.jboss.org/wiki/FunctionalProgrammingInDrools

and opened a JIRA ticket to gather all the comments and suggestions related
to it:

https://issues.jboss.org/browse/JBRULES-3516

I just started working on the development of the features listed in that
document and at the moment I only have a first working implementation of
what described in the "Higher-Order functions" section.

Thanks for your feedbacks,
Mario
_______________________________________________
rules-dev mailing list
rules-dev&amp;lt; at &amp;gt;lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
&lt;/pre&gt;</description>
    <dc:creator>Mario Fusco</dc:creator>
    <dc:date>2012-05-23T07:32:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5711">
    <title>[rules-dev] Event Abstraction,Event Sequencing and Pattern repetition</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5711</link>
    <description>&lt;pre&gt;   All,

   For the next Drools release we intend to add support to event
abstraction, event sequencing, pattern repetition and related features. A
draft proposal can be found in the following link:

https://community.jboss.org/wiki/EventSequencing

   I opened a JIRA to centralize feedback for future reference:

https://issues.jboss.org/browse/JBRULES-3514

   Feedback is welcome on the above ticket. I would like to minimize e-mail
feedback as that ends up lost in time.

   Individual features will be implemented in sub-tickets of the above
master ticket.

   I am starting to refine the draft and will start the design asap, so the
sooner you send me feedback, the more likely it will be included in the
final release.

   Thanks,
      Edson

&lt;/pre&gt;</description>
    <dc:creator>Edson Tirelli</dc:creator>
    <dc:date>2012-05-22T19:43:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5710">
    <title>[rules-dev] 6th International Rule Challenge organized by RuleML 2012 in Montpellier, France, August 27-29, 2012</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5710</link>
    <description>&lt;pre&gt;Dear Drools developers,

The 6th International Rule Challenge organized by RuleML 2012 in 
Montpellier, France, August 27-29, 2012  is an opportunity to submit 
rule-based applications illustrating Drools performance with respect of 
challenging tasks. In addition, you are welcome to submit applications 
illustrating best practices  on Drools implementations as well as 
contributions emphasizing challenging use cases.

Participants can take advantage of many events taking place in 
Montpellier, including the main RuleML2012 Symposium and also various 
ECAI2012 events. However, the Rule Challenge is also open for remote 
presentations.

Would you be interested please consider the below important dates and 
submission guidelines:

Dates:
Paper submission: June 15, 2012
Notification of acceptance/rejection: July 15, 2012
Camera-ready copy due: July 31, 2012

Submission:
1. An open-source or commercial demo (or an URL of the application)
2. A demo paper, using LNCS format, describing research, implementation, 
and technical details of your submission.

Links:
http://2012.ruleml.org/rulechallenge
http://2012.ruleml.org/keynotes
http://www2.lirmm.fr/ecai2012/

Sincerely,
Adrian Giurca
PC-chair of RuleML2012
_______________________________________________
rules-dev mailing list
rules-dev&amp;lt; at &amp;gt;lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
&lt;/pre&gt;</description>
    <dc:creator>Adrian Giurca</dc:creator>
    <dc:date>2012-05-22T07:35:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5709">
    <title>[rules-dev] 2nd CFP - 6th Int. Workshop on Event-Driven Business Process Management (edBPM12)</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5709</link>
    <description>&lt;pre&gt;[ our apologies should you receive this message more than one time ]

6th Int. Workshop on Event-Driven Business Process Management (edBPM12)

collocated with BPM 2012

Tallinn, Estonia, 3-7 September 2012

http://icep-edbpm12.fzi.de/

++++ SUBMISSION DEADLINE - JUNE 1st +++++


Workshop Themes
--------------------------

Authors are invited to submit novel contributions in the prior described
problem domain.

    * Event-driven BPM: Concepts
          o Role of event processing in BPM
          o Business Events: types and representation
          o Event stream processing in business processes
          o Data- and event-driven business processes
          o Evaluation/ROI of event-driven BPM
          o Event-driven SOA
          o EDA and BPM
          o Real/time awareness in BPM
          o Context in BPM
    * Design-time CEP and BPM
          o Modelling languages, notations and methods for event-driven BPM
          o Event Patterns: Definition / Creation / Representation /
Learning
          o BPMN and event processing
          o Modelling unknown/similar events in business processes
          o Modelling events in human-oriented tasks
          o Semantics/Ontologies for event-driven BPM
          o Publish/subscription mechanism and process modelling
    * Run-time CEP and BPM
          o Event pattern detection
          o BPEL and event processing
          o Reasoning about unknown/similar events
          o Distributed event processing
          o Dynamic workflows
          o Ad-hoc workflows
    * Applications/Use cases for event-driven BPM
          o Event-driven monitoring/BAM
          o Event-driven SLA monitoring
          o Domains: Logistics, Automotive, .
          o Event processing and Internet of Services


Important Dates
--------------------------

Deadline paper submissions: 1 June 2012

Notification of acceptance: 2 July 2012

Camera-ready papers: 30 July 2012

Workshops: 3 September 2012

Submission
--------------------------

The following types of submission are solicited:

- Long paper submissions, describing substantial contributions of novel
ongoing work. Long papers should be at most 12 pages long.

- Short paper submissions, describing work in progress. These papers should
be at most 6 pages long.

- Use case submission, describing results from an edBPM use case. These
papers should be at most 4 pages long.

Papers should be submitted in the new LNBIP format
(http://www.springer.com/computer/lncs?SGWID=0-164-6-791344-0). Papers have
to present original research contributions not concurrently submitted
elsewhere. The title page must contain a short abstract, a classification of
the topics covered, preferably using the list of topics above, and an
indication of the submission category (Long Paper/ Short Paper). Accepted
paper will be published in the joint workshops proceeding (Springer).

For submission, please visit
http://www.easychair.org/conferences/?conf=edbpm12.


Organizing Committee
--------------------------

Nenad Stojanovic
FZI - Research Center for Information Technologies at the University of
Karlsruhe, Germany.
nstojano (at) fzi dot de

Opher Etzion
IBM Research Lab in Haifa
OPHER (at) il dot ibm dot com

Adrian Paschke
Corporate Semantic Web, Free University Berlin, Germany and RuleML Inc.,
Canada
paschke (at) inf dot fu-berlin dot de

Christian Janiesch
Karlsruhe Institute of Technology (KIT)
Christian.Janiesch (at) kit dot edu

&lt;/pre&gt;</description>
    <dc:creator>Adrian Paschke</dc:creator>
    <dc:date>2012-05-21T08:25:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5708">
    <title>Re: [rules-dev] Drools 5.4.0.Final released</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5708</link>
    <description>&lt;pre&gt;Hi Mark,

I got excited about the possibilities so I tried to port Drools over about
6 months ago and got hung up for all of the reasons you have mentioned....

I would like to point out (as I experiment w/the AlphaPad Android 4 Tablet
-&amp;gt; wholesale from China) that the 'new' up and coming Android tablets
really 'do' have plenty of processing power and capacity to handle the Rete
Algorithm.

I have ported Prolog to the Android platform (B&amp;amp;N Color Nook) and as long
as it's loaded 'properly' it runs  plenty fast.

I also suspect that the corporate market would have some hidden (but quite
profitable) uses for Drools on the Android Tablet Platform, as I think the
flood of Cheap high quality Tablets that I think China will flood the US
market with, is inevitable. I live in the Netherlands (X-Pat from Chicago),
so we get to see some of these trends before they hit the mainland.

Just food for thought, and congrats on a great product! :-)

-matt

****************

On Mon, May 14, 2012 at 10:24 PM, Mark Proctor &amp;lt;mproctor&amp;lt; at &amp;gt;codehaus.org&amp;gt;wrote:



&lt;/pre&gt;</description>
    <dc:creator>Matthew Versaggi</dc:creator>
    <dc:date>2012-05-16T08:14:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5707">
    <title>Re: [rules-dev] can't put the formula in Guvnor 5.4</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5707</link>
    <description>&lt;pre&gt;Thanks Mark...I post my question to rules-users&amp;lt; at &amp;gt;lists.jboss.org ....

thanks again...














On Tue, May 15, 2012 at 4:27 PM, Mark Proctor &amp;lt;mproctor&amp;lt; at &amp;gt;codehaus.org&amp;gt; wrote:



&lt;/pre&gt;</description>
    <dc:creator>zeeshan khan</dc:creator>
    <dc:date>2012-05-15T11:21:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5706">
    <title>Re: [rules-dev] can't put the formula in Guvnor 5.4</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5706</link>
    <description>&lt;pre&gt;This is a channel for those developing drools itself, the lists page 
clearly specifies for you to join the USER mailing list
http://www.jboss.org/drools/lists

That book is many years old, guvnor has changed a lot since then, there 
is no updated version for that book title. I suggest you look at the 
documentation that comes with the release you are using.

Please ask any further questions on the USER mailing list.

On 15/05/2012 11:52, zeeshan khan wrote:

_______________________________________________
rules-dev mailing list
rules-dev&amp;lt; at &amp;gt;lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
&lt;/pre&gt;</description>
    <dc:creator>Mark Proctor</dc:creator>
    <dc:date>2012-05-15T10:57:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5705">
    <title>[rules-dev] can't put the formula in Guvnor 5.4</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5705</link>
    <description>&lt;pre&gt;Hi Team !

           Since yesterday only I started learning Drools with the help of
Google and *JBOSS DROOLS BUSINESS RULES pdf file*. I faced many problems to
understand the concept but now its going smooth. But the problem is
the *version
of PDF file of the book* and the *Govener version*. *Its quite different*.
 I request you all to please provide me the latest version of PDF as I am
unable to find on net. The problem I am facing is to put the formula as
given in the screen shot in the book.
           I am unable to put the *formula* as described in JBOSS DROOLS
BUSINESS RULES pdf file on page no. 102.....the formula is *salesValue-10
as the box is not capable of taking cahracters. *It is taking only integer.

Thanks in Advance for all the help and material !!!!
_______________________________________________
rules-dev mailing list
rules-dev&amp;lt; at &amp;gt;lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
&lt;/pre&gt;</description>
    <dc:creator>zeeshan khan</dc:creator>
    <dc:date>2012-05-15T10:52:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5704">
    <title>[rules-dev] IRC Server Change - from Codehaus to Freenode</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5704</link>
    <description>&lt;pre&gt;Drools, jBpm and Guvnor are moving from codehaus irc servers to 
freenode. You can now find us on the following channels on 
irc://chat.freenode.net &amp;lt;http://chat.freenode.net&amp;gt;
#drools &amp;lt;https://plus.google.com/s/%23drools&amp;gt;
#droolsdev &amp;lt;https://plus.google.com/s/%23droolsdev&amp;gt;
#jbpm &amp;lt;https://plus.google.com/s/%23jbpm&amp;gt;
#jbpmdev &amp;lt;https://plus.google.com/s/%23jbpmdev&amp;gt;
#guvnor &amp;lt;https://plus.google.com/s/%23guvnor&amp;gt;
#guvnordev &amp;lt;https://plus.google.com/s/%23guvnordev&amp;gt;

freenode also maintains a web interface:
http://webchat.freenode.net/
_______________________________________________
rules-dev mailing list
rules-dev&amp;lt; at &amp;gt;lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
&lt;/pre&gt;</description>
    <dc:creator>Mark Proctor</dc:creator>
    <dc:date>2012-05-15T10:49:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5703">
    <title>Re: [rules-dev] Drools 5.4.0.Final released</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5703</link>
    <description>&lt;pre&gt;currently drools relies on runtime code generation, and our architecture 
is built around that. I think it may run already if you use pure MVEL 
with 5.4 - or atleast a few tweaks and it shoud run. 1) probably stop 
the JIT kicking in to ASM bytecode statements. 2) I think I remember 
some classloader problem, android needs parent classloader. The other 
option is we pre-generate all our generated bytecode and put it in a jar 
so it can be resolved when needed.

I've not prioritised it, because our Rete algorithm can be too eager for 
mobile enviornments. However I almost have lazy rete working, that 
merges the benefits of Rete and Leaps; the resulting algorithm is ideal 
for mobile enviornments. Once I get that working, I'll be more keen to 
accelerate our mobile efforts.

Mark
On 14/05/2012 21:02, Matthew Versaggi wrote:

_______________________________________________
rules-dev mailing list
rules-dev&amp;lt; at &amp;gt;lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
&lt;/pre&gt;</description>
    <dc:creator>Mark Proctor</dc:creator>
    <dc:date>2012-05-14T20:24:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5702">
    <title>Re: [rules-dev] Drools 5.4.0.Final released</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5702</link>
    <description>&lt;pre&gt;Hi Gents!

Great News!

Is there any talk about porting Drools to Android 4 by chance?

Inquiring Minds want to know .... :-)

-matt

************************************

On Mon, May 14, 2012 at 9:28 PM, Mark Proctor &amp;lt;mproctor&amp;lt; at &amp;gt;codehaus.org&amp;gt; wrote:



&lt;/pre&gt;</description>
    <dc:creator>Matthew Versaggi</dc:creator>
    <dc:date>2012-05-14T20:02:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5701">
    <title>[rules-dev] Drools 5.4.0.Final released</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5701</link>
    <description>&lt;pre&gt;http://blog.athico.com/2012/05/drools-540final-released.html
----link contents pasted below---

We are happy to announce the release of Drools (Expert, Fusion, Planner, 
Guvnor) *5.4.0.Final*. jBPM 5.3.0 announcement will follow shortly and 
the link will be added when it does.

Documentation, Release Notes and Downloads are detailed below:

  * Download the zips from the bottom of the drools download page
    &amp;lt;http://www.jboss.org/drools/downloads&amp;gt;.
      o To try out the examples, just unzip one and run a
        runExamples.sh/.bat script.
      o See the JBoss Maven repository for a list of all released
        artifacts
        &amp;lt;https://repository.jboss.org/nexus/index.html#nexus-search;gav%7Eorg.drools*%7E%7E5.4.0.Final%7E%7E&amp;gt;.
          + It will be synced to Maven Central
            &amp;lt;http://search.maven.org/#search%7Cga%7Final%7Corg.drools&amp;gt;
            automatically in a couple of hours.
  * *Read the new and noteworthy changes here.
    &amp;lt;http://docs.jboss.org/drools/release/5.4.0.Final/droolsjbpm-introduction-docs/html/releaseNotesSimple.html&amp;gt;*

Try it out and give us some feed-back (user list 
&amp;lt;http://www.jboss.org/drools/lists&amp;gt;, issue tracker 
&amp;lt;https://issues.jboss.org/browse/JBRULES&amp;gt;).

Some new online videos, make sure you change youtube setting to 720:

*Build Pong in 13 Minutes*
http://www.youtube.com/watch?v=Omj4PR3v-nI

*Build a Graphical Adventure in 20 Minutes:*
http://www.youtube.com/watch?v=4CvjKqUOEzM 
&amp;lt;http://www.youtube.com/watch?v=4CvjKqUOEzM%20&amp;gt;

*Guided Decision Tables*
http://vimeo.com/35472874

*Importing Excel Decision Tables*
http://vimeo.com/37033081http://vimeo.com/37033081 
&amp;lt;http://vimeo.com/37033081&amp;gt;
_______________________________________________
rules-dev mailing list
rules-dev&amp;lt; at &amp;gt;lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
&lt;/pre&gt;</description>
    <dc:creator>Mark Proctor</dc:creator>
    <dc:date>2012-05-14T19:28:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5700">
    <title>[rules-dev] Build Pong in 13 minutes using JBoss Drools</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5700</link>
    <description>&lt;pre&gt;Just finished "Build Pong in 13 minutes with JBoss Drools" enjoy :) and 
please vote up on dzone
http://www.dzone.com/links/build_pong_in_13_minutes_using_jboss_drools.html

For those with more time, here is a longer and more complex video that I 
made before Pong.
"Build a Graphical Adventure Game in 20 minutes using JBoss Drools : All 
Hail the Wumpus "
http://www.dzone.com/links/build_a_graphical_adventure_game_in_20_minutes_us.html

Mark
_______________________________________________
rules-dev mailing list
rules-dev&amp;lt; at &amp;gt;lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev

&lt;/pre&gt;</description>
    <dc:creator>Mark Proctor</dc:creator>
    <dc:date>2012-05-11T15:10:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5699">
    <title>Re: [rules-dev] Help</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5699</link>
    <description>&lt;pre&gt;http://www.integratingstuff.com/2011/01/28/setting-up-drools-guvnor/

On Sat, Feb 4, 2012 at 2:58 PM, Olfa h &amp;lt;h.olfa.h&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:



&lt;/pre&gt;</description>
    <dc:creator>Shubhranshu Swain</dc:creator>
    <dc:date>2012-05-09T15:51:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5698">
    <title>[rules-dev] Drools 5.4: Artificial Intelligence, A Little History</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5698</link>
    <description>&lt;pre&gt;please vote up:
http://www.dzone.com/links/drools_54_artificial_intelligence_a_little_history.html
-----copied from website link-----
As part of the 5.4 release, going out the door as we speak, I updated 
the intro docs. I have tried to give a wider understanding of the field 
and scope of work. Here is a copy. I'll try and improve the sections 
over future releases, I ran out of time and the later sections are 
little rushed and thin. I'm not the best of writers, so please have 
patience, all contributions welcome :)


      *A Little History*

Over the last few decades artificial intelligence (AI) became an 
unpopular term, with the well know "AI Winter" 
&amp;lt;http://en.wikipedia.org/wiki/AI_winter&amp;gt;. There were large boasts from 
scientists and engineers looking for funding, that never lived up to 
expectations along with many failed projects. Thinking Machines 
Corporation &amp;lt;http://en.wikipedia.org/wiki/Thinking_Machines_Corporation&amp;gt; 
and the 5th Generation Computer 
&amp;lt;http://en.wikipedia.org/wiki/Fifth-generation_computer&amp;gt; (5GP) project 
probably exemplify best the problems at the time.

Thinking Machines Corporation was one of the leading AI firms in 1990, 
it had sales of nearly $65 million. Here is quote from it's brochure:
"Some day we will build a thinking machine. It will be a truly 
intelligent machine. One that can see and hear and speak. A machine that 
will be proud of us."

Yet 5 years later it filed for Chapter 11. inc.com has a fascinating 
article titled "The Rise and Fall of Thinking Machines" 
&amp;lt;http://www.inc.com/magazine/19950915/2622.html&amp;gt;. The article covers the 
growth of the industry and how a cosy relationship with Thinking 
Machines and DARPA &amp;lt;http://en.wikipedia.org/wiki/DARPA&amp;gt; over heated the 
market, to the point of collapse. It explains how and why commerce moved 
away from AI and towards more practical number crunching super computers.

The 5th Generation Computer project was a 400mill USD project in Japan 
to build a next generation computer. Valves was first, transistors was 
second, integrated circuits was third and finally microprocessors was 
fourth. This project spurred an "arms" race with the UK and USA, that 
caused much of the AI bubble. The 5GP would provide massive multi-cpu 
parallel processing hardware along with powerful knowledge 
representation and reasoning software via Prolog; a type of expert 
system. By 1992 the project was considered a failure and cancelled. It 
was the largest and most visible commercial venture for Prolog, and many 
of the failures are pinned on the problems trying to run a logic based 
programming language concurrently on multi cpu hardware with effective 
results. Some believe that the failure of the 5GP project tainted Prolog 
and resigned it academia, see "Whatever Happened to Prolog" 
&amp;lt;http://www.dvorak.org/blog/whatever-happened-to-prolog/&amp;gt; by John C. Dvorak.

However while research funding dried up and the term AI became less 
used, many green shoots where planted and continued more quietly under 
discipline specific names: cognitive systems, machine learning, 
intelligent systems, knowledge representation and reasoning. Offshoots 
of these then made their way into commercial systems, such as expert 
systems in the Business Rules Management System (BRMS) market.

Imperative, system based languages, languages such as C, C++, Java and 
.Net have dominated the last 20 years. Enabled by the practicality of 
the languages and ability to run with good performance on commodity 
hardware. However many believe there is renaissance undergoing in the 
field of AI, spurred by advances in hardware capabilities and AI 
research. In 2005 Heather Havenstein authored "Spring comes to AI 
winter" 
&amp;lt;http://www.computerworld.com/s/article/99691/Spring_comes_to_AI_winter&amp;gt; 
which outlines a case for this resurgence, which she refers to as a 
spring. Norvig and Russel dedicate several pages to what factors allowed 
the industry to over come it's problems and the research that came about 
as a result:

"Recent years have seen a revolution in both the content and the 
methodology of work in artificial intelligence. It is now more common to 
build on existing theories than to propose brand-new ones, to base 
claims on rigorous theorems or hard experimental evidence rather than on 
intuition, and to show relevance to real-world applications rather than 
toy examples." (Artificial Intelligence : A Modern Approach.)

Computer vision, neural networks, machine learning and knowledge 
representation and reasoning (KRR) have made great strides in become 
practical in commercial environments. For example vision based systems 
can now fully map out and navigate their environments with strong 
recognition skills, as a result we now have self driving cars about to 
enter the commercial market. Ontological research, based around 
description logic, has provided very rich semantics to represent our 
world. Algorithms such as the tableaux algorithm have made it possible 
to effectively use those rich semantics in large complex ontologies. 
Early KRR systems, like Prolog in 5GP, were dogged by the limited 
semantic capabilities and memory restrictions on the size of those 
ontologies.


      *Knowledge Representation and Reasoning *

In A Little History talks about AI as a broader subject and touches on 
Knowledge Representation and Reasoning (KRR) and also Expert Systems, 
I'll come back to Expert Systems later.
KRR is about how we represent our knowledge in symbolic form, i.e. how 
we describe something. Reasoning is about how we go about the act of 
thinking using this knowledge. System based languages, like Java or C+, 
have classification systems, called Classes, to be able to describe 
things, in Java we calls these things beans or instances. However those 
classification systems are limited to ensure computational efficiency. 
Over the years researchers have developed increasingly sophisticated 
ways to represent our world, many of you may already have heard of OWL 
(Web Ontology Language). Although there is always a gap between what we 
can be theoretically represented and what can be used computationally in 
practically timely manner, which is why OWL has different sub languages 
from Lite to Full. It is not believed that any reasoning system can 
support OWL Full. Although Each year algorithmic advances try and narrow 
that gap and improve expressiveness available to reasoning engines.

There are also many approaches to how these systems go about thinking. 
You may have heard of discussions comparing the merits of forward 
chaining, which is reactive and data driven, or backward chaining, which 
is passive and query driven. Many other types of reasoning techniques 
exists, each of which enlarges the scope of the problems we can tackle 
declaratively. To list just a few: imperfect reasoning (fuzzy logic, 
certainty factors), defeasible logic, belief systems, temporal reasoning 
and correlation. Don't worry if some of those words look alien to you, 
they aren't needed to understand Drools and are just there to give an 
idea of the range of scope of research topics; which is actually far 
more extensive than this small list and continues to grow as researches 
push new boundaries.

KRR is often refereed as the core of Artificial Intelligence Even when 
using biological approaches like neural networks, which model the brain 
and are more about pattern recognition than thinking, they still build 
on KRR theory. My first endeavours with Drools were engineering 
oriented, as I had no formal training or understanding of KRR. Learning 
KRR has allowed me to get a much wider theoretical background. Allowing 
me to better understand both what I've done and where I'm going, as it 
underpins nearly all of the theoretical side to our Drools R&amp;amp;D. It 
really is a vast and fascinating subject that will pay dividends for 
those that take the time learn, I know it did and still does for me. 
Bracham and Levesque have written a seminal piece of work, called 
"Knowledge Representation and Reasoning" that for anyone wanting to 
build strong foundations is a must read. I would also recommend the 
Russel and Norvig book "Artificial Intelligence, a modern approach" 
which also covers KRR.


      *Rule Engines and Production Rule Systems*

We've now covered a brief history of AI and learnt that the core of AI 
is formed around KRR. We've shown than KRR is vast and fascinating 
subject which forms the bulk of the theory driving Drools R&amp;amp;D.
The rule engine is the computer program that delivers KRR functionality 
to the developer. At a high level it has three components:

  * Ontology
  * Rules
  * Data

As previous mentioned the ontology is the representation model we use 
for our "things". It could be a simple records or Java classes or full 
blown OWL based ontologies. The Rules do the reasoning and facilitate 
thinking. The distinction between rules and ontologies blurs a little 
with OWL based ontologies, who's richness is rule based.

The term rule engine is quite ambiguous in that it can be any system 
that uses rules, in any form, that can be applied to data to produce 
outcomes. This includes simple systems like form validation and dynamic 
expression engines. The book "How to Build a Business Rules Engine 
(2004)" by Malcolm Chisholm exemplifies this ambiguity. The book is 
actually about how to build and alter a database schema to hold 
validation rules. The book then shows how to generate VB code from those 
validation rules to validate data entry. Which while very valid, it is 
very different to what we talking about so far.

Drools started life as a specific type of rule engine called a 
production rule system (PRS) and was based around the Rete algorithm. 
The Rete algorithm, developed by Charles Forgey in 1979, forms the brain 
of a Production Rules System and is able to scale to a large number of 
rules and facts. A Production Rule is a two-part structure: the engine 
matches facts and data against Production Rules - also called 
Productions or just Rules - to infer conclusions which result in actions.

when
     &amp;lt;conditions&amp;gt;
then
     &amp;lt;actions&amp;gt;;

The process of matching the new or existing facts against Production 
Rules is called pattern matching, which is performed by the inference 
engine. Actions execute in response to changes in data, like a database 
trigger; we say this is a data driven approach to reasoning. The actions 
themselves can change data, which in turn could match against other 
rules causing them to fire; this is referred to asforward chaining

Drools implements and extends the Rete algorithm;. The Drools Rete 
implementation is called ReteOO, signifying that Drools has an enhanced 
and optimized implementation of the Rete algorithm for object oriented 
systems. Our more recent work goes well beyond Rete. Other Rete based 
engines also have marketing terms for their proprietary enhancements to 
Rete, like RetePlus and Rete III. Th e most common enhancements are 
covered in "Production Matching for Large Learning Systems (Rete/UL)" 
(1995) by Robert B. Doorenbos. Leaps used to be provided but was retired 
as it became unmaintained, the good news is our research is close to 
producing an algorithm that merges the benefits of Leaps with Rete.

The Rules are stored in the Production Memory and the facts that the 
Inference Engine matches against are kept in the Working Memory. Facts 
are asserted into the Working Memory where they may then be modified or 
retracted. A system with a large number of rules and facts may result in 
many rules being true for the same fact assertion; these rules are said 
to be in conflict. The Agenda manages the execution order of these 
conflicting rules using a Conflict Resolution strategy.
&amp;lt;http://3.bp.blogspot.com/-vWa8Xb6vQwM/T6nHhPwGfiI/AAAAAAAAAug/dqMpgCGhDqc/s1600/rule-engine-inkscape.png&amp;gt;


      *Hybrid Reasoning Systems*

You may have read discussions comparing the merits of forward chaining 
(reactive and data driven) or backward chaining(passive query). Here is 
a quick explanation of these two main types of reasoning.

Forward chaining is "data-driven" and thus reactionary, with facts being 
asserted into working memory, which results in one or more rules being 
concurrently true and scheduled for execution by the Agenda. In short, 
we start with a fact, it propagates and we end in a conclusion.
&amp;lt;http://2.bp.blogspot.com/-VpcT8CsFVvI/T6nHI4nXNZI/AAAAAAAAAuI/Z8ym04qHZ0c/s1600/Forward_Chaining.png&amp;gt;

Backward chaining is "goal-driven", meaning that we start with a 
conclusion which the engine tries to satisfy. If it can't it then 
searches for conclusions that it can satisfy; these are known as 
subgoals, that will help satisfy some unknown part of the current goal. 
It continues this process until either the initial conclusion is proven 
or there are no more subgoals. Prolog is an example of a Backward 
Chaining engine. Drools can also do backward chaining, which we refer to 
as derivation queries.
&amp;lt;http://1.bp.blogspot.com/-K4Cy7TxxFJQ/T6nHQh0iVSI/AAAAAAAAAuQ/jvDqKhrYIgc/s1600/Backward_Chaining.png&amp;gt;

Historically you would have to make a choice between systems like OPS5 
(forward) or Prolog (backward). Now many modern systems provide both 
types of reasoning capabilities. There are also many other types of 
reasoning techniques, each of which enlarges the scope of the problems 
we can tackle declaratively. To list just a few: imperfect reasoning 
(fuzzy logic, certainty factors), defeasible logic, belief systems, 
temporal reasoning and correlation. Modern systems are merging these 
capabilities, and others not listed, to create hybrid reasoning systems 
(HRS).

While Drools started out as a PRS, 5.x introduced Prolog style backward 
chaining reasoning as well as some functional programming styles. For 
this reason HRS is now the preferred term when referring to Drools, and 
what it is.

Drools current provides crisp reasoning, but imperfect reasoning is 
almost ready. Initially this will be imperfect reasoning with fuzzy 
logic, later we'll add support for other types of uncertainty. Work is 
also under way to bring OWL based ontological reasoning, which will 
integrate with our traits system. We also continue to improve our 
functional programming capabilities.

*Expert Systems*

You will often hear the terms expert systems used to refer to production 
rule systems or Prolog like systems. While this is normally acceptable, 
it's technically wrong as these are frameworks to build expert systems 
with, and not actually expert systems themselves. It becomes an expert 
system once there is an ontological model to represent the domain and 
there are facilities for knowledge acquisition and explanation.

Mycin is the most famous expert system, built during the 70s. It is 
still heavily covered in academic literature, such as the recommended 
book "Expert Systems" by Peter Jackson.
&amp;lt;http://1.bp.blogspot.com/-LJouA2Bc8ow/T6nG9Y18NoI/AAAAAAAAAuA/CbZIhdW-zko/s1600/expertsytem_history.png&amp;gt;


      *Recommended Reading*


        *General AI, KRR and Expert System Books*

For those wanting to get a strong theoretical background in KRR and 
expert systems, I'd strongly recommend the following books. "Artificial 
Intelligence: A Modern Approach" is must have, for anyone's bookshelf.

  * Introduction to Expert Systems
      o Peter Jackson

  * Expert Systems: Principles and Programming
      o Joseph C. Giarratano, Gary D. Riley

  * Knowledge Representation and Reasoning
      o Ronald J. Brachman, Hector J. Levesque

  * Artificial Intelligence : A Modern Approach.
      o Stuart Russell and Peter Norvig


&amp;lt;http://1.bp.blogspot.com/-MxwC6sGAonk/T6nGt3cUUmI/AAAAAAAAAtw/T2fooYHJLEM/s1600/book_recommendations.png&amp;gt;


        *Papers*

Here are some recommended papers that cover some interesting areas in 
rule engine research.

  * Production Matching for Large Learning Systems : Rete/UL (1993)
      o Robert B. Doorenbos
  * Advances In Rete Pattern Matching
      o Marshall Schor, Timothy P. Daly, Ho Soo Lee, Beth R. Tibbitts
        (AAAI 1986)
  * Collection-Oriented Match
      o Anurag Acharya and Milind Tambe (1993)
  * The Leaps Algorithm (1990)
      o Don Battery
  * Gator: An Optimized Discrimination Network for Active Database Rule
    Condition Testing (1993)
      o Eric Hanson , Mohammed S. Hasan


        *Drools Books*

There are currently three Drools books, all from Packt Publishing.

  * JBoss Drools Business Rules
      o Paul Brown
  * Drools JBoss Rules 5.0 Developers Guide
      o Michali Bali
  * Drools Developer's Cookbook
      o Lucas Amador


&amp;lt;http://2.bp.blogspot.com/-aXE48hRa38Y/T6nG0-4ASXI/AAAAAAAAAt4/qJL-BiWI6dg/s1600/drools_book_recommendations.png&amp;gt;

_______________________________________________
rules-dev mailing list
rules-dev&amp;lt; at &amp;gt;lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
&lt;/pre&gt;</description>
    <dc:creator>Mark Proctor</dc:creator>
    <dc:date>2012-05-09T01:52:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5697">
    <title>[rules-dev] api's, factories and services</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5697</link>
    <description>&lt;pre&gt;Just a reminder when doing api's

Stage interfaces in internal-api and make sure you do factories for 
them, almost never expose "new" constructors to users. We provide both 
static factories and a service registry, and we ideally should continue 
to support both. i.e. we have
KnowledgeBuilderFactory (static method factory, actually wraps below)
KnowledgeBuilderFactoryService (singleton service)

static example:
KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder()

singleton service  exmaple:
KnowledgeBuilderFactoryService kbuilderfs = 
ServiceRegistry.getInstance().get( KnowledgeBuilderFactoryService.class )
KnowledgeBuilder kbuilder = kbuilderfs .newKnowledgeBuilder()

All of our factory services should be registered in 
org.drools.util.ServiceRegistryImpl, this has delegation to say OSGi if 
it exists (via the service locator pattern). So we become much more 
friendly to OSGi or other container environments that are service 
locator oriented.

"new" should almost never be used, apart from when construcing say 
default or debug listener implementations.


Mark


_______________________________________________
rules-dev mailing list
rules-dev&amp;lt; at &amp;gt;lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev

&lt;/pre&gt;</description>
    <dc:creator>Mark Proctor</dc:creator>
    <dc:date>2012-03-01T11:22:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.java.drools.devel/5696">
    <title>[rules-dev] Help</title>
    <link>http://permalink.gmane.org/gmane.comp.java.drools.devel/5696</link>
    <description>&lt;pre&gt;good morning,


can you help me to install drools  ( for windows)

thanks
_______________________________________________
rules-dev mailing list
rules-dev&amp;lt; at &amp;gt;lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
&lt;/pre&gt;</description>
    <dc:creator>Olfa h</dc:creator>
    <dc:date>2012-02-04T09:28:17</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.java.drools.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.java.drools.devel</link>
  </textinput>
</rdf:RDF>

