Just forwarding this to the old list for folks who haven't migrated to
the new list.

        -bob


---------- Forwarded message ----------
To: [EMAIL PROTECTED]
From: bob mcwhirter <[EMAIL PROTECTED]>
Date: Sat, 10 Aug 2002 03:01:15 -0400 (EDT)
Subject: Update


Howdy folks--

Saw lots of traffic on the lists during this past week, whilst I was
disconnected at the seaside.

Just wanted to toss an update.

1) No, I'm not ignoring y'all.  Just wan't online.  Back now.

2) I'm working on a new drools guide.  So far, about 30 pages.  Hopefully
   it'll answer most of your questions.

3) Seems that I've got a Rete-enabled co-conspirator now, who's also 
   working on a .NET port of drools.  Hopefully the two of us can get
   the Rete-OO algorithm fairly well stablized and more formally correct.

4) Please please please, if you experience any difficulty with drools, 
   go straight to http://jira.werken.com/ and file an issue.  Or, file
   an improvement-request.  Jira runs my life.  If it's not in jira,
   then it doesn't exist.  (Though, still send mail to the lists also,
   so we can discuss.)

5) If it has 'sourceforge' in the name, it's deprecated.  Do not use it.
   This include the sourceforge CVS, maillists, bug-trackers, distributions,
   etc. 

6) The official home of drools, http://drools.org/ is the canoncial source 
   for all current drools information, such as CVS, maillists, bug-trackers,
   distributions, etc. 

7) RuleML does not (currently) aim to solve the Event-Condition-Action types
   of rule languages.  They -have- left room for it though.  RuleML 0.8
   does not suit our needs.  Anyone want to take a stab at representing
   drools in the RuleML 0.9 (or wherever they are heading) ECA types of
   rules?  

8) Anyone using drools, or wanting to use drools, for inferencing?  I
   think the RDF module, doing DAML+OIL, or wahtnot, is an inference
   use-case, instead of an ECA.   This may inspire some renaming/abstracting
   of the core Rete-OO algorithm in order to support Inference and ECA
   models.  This may also require massive renaming/re-arranging to keep
   the codebase coherent.

9) Remember, I'm hanging out on irc.werken.com #drools channel.  
   Come chat.

10) Is drools potentially important to your company?  Do you have some
    priority issues/features/changes that I haven't gotten around to
    doing?  Want help integrating drools into your environment?  Really
    wish there was more/different/better documentation?  If so, I'm 
    available for consulting, development, training, etc.  I have no
    'real' Day Job now, and I'm trying to support my family (2 other
    humans and 6 animals) through contracting, consulting, and friendly
    companies sponsoring my hopefully useful open-source projects.

    So, talk to your management if you want to see drools thrive in the
    long run.

11) Some of y'all may be interested in werkflow http://werkflow.werken.com/
    which will be a BPML-compliant workflow engine.  I'm looking for some
    good Swing hackers to help work on a workflow studio.
    So far, thanks goes to Zenplex for the initial sponsorship of the werkflow
    project, during the research and first round of design phases.

        -bob

--
Bob McWhirter        [EMAIL PROTECTED]
The Werken Company   http://werken.com/




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
drools-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/drools-interest

Reply via email to