http://blog.gmane.org/gmane.comp.java.drools.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.java.drools.devel/2759 _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev Michal Bali 2008-12-03T21:48:35 http://comments.gmane.org/gmane.comp.java.drools.devel/2754 _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev Ashish Redkar 2008-11-28T13:29:36 http://comments.gmane.org/gmane.comp.java.drools.devel/2753 Compioitions now work and the new Resource framework is committed. You can see the api in action here: http://anonsvn.labs.jboss.com/labs/jbossrules/trunk/drools-decisiontables/src/test/java/org/drools/decisiontable/CompositionTest.java Along with the xml knowledge composition file it is loading: http://anonsvn.labs.jboss.com/labs/jbossrules/trunk/drools-decisiontables/src/test/resources/org/drools/decisiontable/composition1Test.xml The summarised version is: <composition xmlns='http://drools.org/drools-4.0/composition' xmlns:xs='http://www.w3.org/2001/XMLSchema-instance' xs:schemaLocation='http://drools.org/drools-4.0/composition drools-composition-4.0.xsd' > <resource source='classpath:org/drools/decisiontable/composition1Test.drl' type='DRL' /> <resource source='classpath:data/IntegrationExampleTest.xls' type="DTABLE"> <decisiontable-conf input-type="XLS" worksheet-name="Tables_2" /> </resource> <resource source='classpath:org/drools/decisiontable/composition2Test.drl' type='DRL' /> </composition> KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder(); kbuilder.add( ResourceFactory.newClassPathResource( "composition1Test.xml", getClass()), KnowledgeType.COMPOSITION ); assertFalse( kbuilder.hasErrors() ); KnowledgeBase kbase = KnowledgeBaseFactory.newKnowledgeBase(); XML Compisition files support all knowledge types, including other xml knowledge compositions. So one composition can reference and load other compositions. I'm not just updating the agent to take advantage of this. Mark _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev Mark Proctor 2008-11-28T07:10:12 http://comments.gmane.org/gmane.comp.java.drools.devel/2748 I'm in the process of doing the final changes to drools-api. Having done the spring work, not yet committed, I liked their resource framework, so decided to copy this for Drools. So we now have: KnowledgeBuilder.add( Resource, KnowledgeType, ResourceConfiguration ); Where we support the following Resource sources: FileSystemResource, ClassPathResource, UrlResource ByteArrayResource, ReaderResource, EncodedResource and InputStreamResource In use it'll look like: kbuilder.add( ResourceFactory.newClassPathResource( "somefile.drl", classLoader ), KnowledgeType.DRL ) I do not yet do knowledge type inference from the .ext - I think I'll leave that till after 5.0, if I do it at all. So kbuilder.addResource( URL, ...) and kbuilder.addResource( Reader, ... ) from M3 no longer exist and are as above. What I'm adding now is the ability to provide an xml file that is a configuration of resources to load. The term Configuration is overloaded, and we use this more to provide the directives for knowledgebuilder and knowledgebase. So I was thinking Composition and Part - for Knowledge Composition and Knowledge Part, from dictionary.com on "composition": "the act of combining parts or elements to form a whole." "the composition of “aircraft” from “air” and “craft.” My reasoning for this is a composition will contain rules, processes, decision tables, dsls etc. "The KnowlegeBase is a composition of Knowlege Parts". The XML would look like: <composition> <part resource="classpath://........" type="DRL"> <part resource="file://........"> <decisiontable-configuration type="XLS" worksheet-name="blah" /> </part> </composition> I have not added a resource type attribute, as we will assume it must start with protocol. classpath will use ClassPathResource, file will use FileSystemResource and anything will be a UrlResource. This would be a special KnowlegeType. I may later make the type optional, once we can infer the type from the .ext. kbuilder.addResource( ResourceFactory.newFileResource( "/data/my-knowledge.xml" ), KnowledgeType.COMPOSITION ); What do people think? Mark _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev Mark Proctor 2008-11-27T06:30:52 http://comments.gmane.org/gmane.comp.java.drools.devel/2743 Documentation and Javadocs are now published continiously (we'll about 1 hour apar) as they change, as part of the hudson build server. https://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/docs/index.html https://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/javadocs/index.html So now people should be able to review our doc changes as they happen. Mark _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev Mark Proctor 2008-11-25T04:08:30 http://comments.gmane.org/gmane.comp.java.drools.devel/2733 I've been reading about spring this weekend, in preparation of spring support for drools-api. My first attempt was using drools-api factories directly, which actually works "out of the box". Here is an example using the KnowledgeAgentFactory: --------beans.xml------- <bean id="agent1" class="org.drools.agent.KnowledgeAgentFactory" factory-method="newKnowledgeAgent"> <constructor-arg type="java.lang.String" value="agent1"/> <constructor-arg type="java.util.Properties"> <props> <prop key="file">src/main/java/org/drools/springframework/testSpring.drl</prop> </props> </constructor-arg> </bean> ---------testSpring.drl--------- package org.drools.springframework rule "rule 1" when then System.out.println( "hello world" ); end ---------test--------- Resource resource = new FileSystemResource( "src/main/java/org/drools/springframework/beans.xml" ); BeanFactory factory = new XmlBeanFactory( resource ); KnowledgeAgent agent1 = ( KnowledgeAgent ) factory.getBean( "agent1" ); agent1.getKnowledgeBase().newStatelessKnowledgeSession().executeObject( "test" ); Sow I was quite impressed how easy that was to get working, but people like the "Spring" way. So I made a custom SpringKnowledgeAgentFactory that implements FactoryBean. So now the above beans.xml can look like the following: <bean id="agent1" class="org.drools.spring.SpringKnowledgeAgentFactory"> <property name="name" value="agent1"/> <property name="file" value="src/main/java/org/drools/spring/testSpring.drl" /> </bean> Which is much less verbose. So I think I'll take some time tomorrow to do FactoryBean implementations for all main user factories from drools-api, shouldn't take long and then we have out of the box spring support. Anyone have any feedback, it seems that now that we have drools-api, which provides complete implementation/interface separation, and Spring only needs to return interfaces, this is all we need to do. If it's quick to do, I might have a go at doing one for Guice too. Mark _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev Mark Proctor 2008-11-23T05:28:01 http://comments.gmane.org/gmane.comp.java.drools.devel/2730 _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev M.DILIP KUMAR 2008-11-12T14:45:14 http://comments.gmane.org/gmane.comp.java.drools.devel/2724 _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev Waleed Zedan 2008-11-10T07:12:51 http://comments.gmane.org/gmane.comp.java.drools.devel/2721 FYI, getting this error in trunk, rev 23768: [INFO] ------------------------------------------------------------------------ [INFO] Building Drools :: Process :: Task [INFO] task-segment: [clean, install] [INFO] ------------------------------------------------------------------------ [INFO] [clean:clean] [INFO] Deleting directory /home/greg/tmp/java/drools/subversion/trunk/drools-process/drools-process-task/target [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Compiling 82 source files to /home/greg/tmp/java/drools/subversion/trunk/drools-process/drools-process-task/target/classes [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Compilation failure /home/greg/tmp/java/drools/subversion/trunk/drools-process/drools-process-task/src/main/java/org/drools/process/workitem/wsht/WSHumanTaskHandler.java:[32,7] org.drools.process.workitem.wsht.WSHumanTaskHandler is not abstract and does not override abstract method abortWorkItem(org.drools.runtime.process.WorkItem,org.drools.runtime.process.WorkItemManager) in org.drools.runtime.process.WorkItemHandler /home/greg/tmp/java/drools/subversion/trunk/drools-process/drools-process-task/src/main/java/org/drools/process/workitem/wsht/WSHumanTaskHandler.java:[32,7] org.drools.process.workitem.wsht.WSHumanTaskHandler is not abstract and does not override abstract method abortWorkItem(org.drools.runtime.process.WorkItem,org.drools.runtime.process.WorkItemManager) in org.drools.runtime.process.WorkItemHandler [INFO] ------------------------------------------------------------------------ [INFO] Trace org.apache.maven.BuildFailureException: Compilation failure /home/greg/tmp/java/drools/subversion/trunk/drools-process/drools-process-task/src/main/java/org/drools/process/workitem/wsht/WSHumanTaskHandler.java:[32,7] org.drools.process.workitem.wsht.WSHumanTaskHandler is not abstract and does not override abstract method abortWorkItem(org.drools.runtime.process.WorkItem,org.drools.runtime.process.WorkItemManager) in org.drools.runtime.process.WorkItemHandler at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure /home/greg/tmp/java/drools/subversion/trunk/drools-process/drools-process-task/src/main/java/org/drools/process/workitem/wsht/WSHumanTaskHandler.java:[32,7] org.drools.process.workitem.wsht.WSHumanTaskHandler is not abstract and does not override abstract method abortWorkItem(org.drools.runtime.process.WorkItem,org.drools.runtime.process.WorkItemManager) in org.drools.runtime.process.WorkItemHandler at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more [INFO] ------------------------------------------------------------------------ [INFO] Total time: 34 seconds [INFO] Finished at: Thu Nov 06 20:20:31 CST 2008 [INFO] Final Memory: 88M/404M [INFO] ------------------------------------------------------------------------ _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev Greg Barton 2008-11-07T02:35:21 http://comments.gmane.org/gmane.comp.java.drools.devel/2720 _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev Mark Proctor 2008-11-07T01:49:21 http://comments.gmane.org/gmane.comp.java.drools.devel/2712 _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev Siddharth Angrish 2008-10-09T02:16:42 http://comments.gmane.org/gmane.comp.java.drools.devel/2702 _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev Oleg Zenzin 2008-10-28T05:08:34 http://comments.gmane.org/gmane.comp.java.drools.devel/2701 _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev Oleg Zenzin 2008-10-26T23:53:55 http://comments.gmane.org/gmane.comp.java.drools.devel/2700 The core Drools team will not have time to update the xml xsd's and parser for the 5.0 release. The XML will continue to work, but you won't be able to use any of the new features, and thus restricted to 4.0 level features. If anyone from the community wants to take this on, then please do, otherwise it'll have to wait until a later date after 5.0 when the core devs can work on this. Mark _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev Mark Proctor 2008-10-26T04:47:40 http://comments.gmane.org/gmane.comp.java.drools.devel/2699 [ our apologies should you receive this message more than one time ] AAAI Spring Symposium on Intelligent Event Processing AAAI Spring Symposium Wednesday, March 23?25, 2009 at Stanford University http://icep-aaai09.fzi.de/ Deadline for submissions: October 31st, 2008 (12.00 AM, GMT) ===================================================================== Event-based systems are now gaining increasing momentum as witnessed by current efforts in areas including event-driven architectures, business process management and modeling, Grid computing, Web services notifications, and message-oriented middleware. They become ever important in various application domains, ranging from traditional business applications, like supply-chain management, to the entertainment industry, like on-line gaming applications. However, the current status of development is just the tip of the iceberg compared with the impact that event processing could achieve, as already reported by market research companies. Indeed, existing approaches are dealing primarily with the syntactical (but very scalable) processing of low-level signals and primitive actions, which usually goes with an inadequate treatment of the notions of time, context or concurrency (for example, synchronization). For example, some of the current event processing products are descendents of the active database research that misses efficient (formal) handling of termination, priority ordering, and confluence in rule bases. AI and especially symbolic (for example, logic-based) approaches provide native background for the (formal) representation of the above mentioned missing concepts, enabling evolution from event processing systems into intelligent reactive systems. The work done in temporal logic, spatial reasoning, knowledge representation, ontologies, and so on enables more declarative representation of events and actions and their semantic processing. Contextual reasoning can support complex event prediction. Transactional logic can be used for ensuring the consistency between highly dependent processes in a formal way. On the other side, the heterogeneous and highly distributed nature of event-processing systems, especially on the web, provides new challenges for AI and logics, like the contextualized reasoning over large stream data, scalable mapping of complex structures, or distributed approximate reasoning, to name but a few. Possible symposium topics comprise, but are not limited to: ----------------------------------------------------------- Modeling *Conceptual modeling in event-driven processing *Modeling context in event-driven processing *Event processing languages *Business rules and event-driven processing *Editors for complex events *Complex event processing in highly distributed AI applications *Modeling reactive systems using event-driven processing *Event stream processing * Event-driven architecture for Intelligent Event Processing Discovery *Complex event patterns mining *Temporal aspects in event mining *Prediction of events * Discovery of similar event *Discovery of unknown events *Dealing with missing events Reasoning/Processing *Complex event detection *The role of logic in event processing *Distributed reasoning for events *Reasoning with uncertain events *Reasoning under real-time constraints *Complexity in reasoning for Intelligent Event Processing Advanced Applications *Distributed event processing as a basis for AI applications *Financial trading *Web / Internet of Things *Entertainment *Ubiquitous Computing/ Ambient Intelligence *Business Activity Monitoring *AI in global epidemiology monitoring systems *Other domains Submissions ----------- Papers should be prepared using the two-column AAAI conference paper format. Long papers should be at most six pages; short papers at most two pages. Papers must be submitted electronically via the symposium website. Submissions must be in PDF using the workshop submission system for SSS09, at http://www.easychair.org/conferences/?conf=sss09 More Information http://icep-aaai09.fzi.de/ Important Dates --------------- Deadline for submissions: October 31st, 2008 (12.00 AM, GMT) Notification of acceptance: December 9th, 2008 Camera-ready versions: January 16th, 2009 Symposium: March 23-25, 2009 Organizing Committee --------------------- Nenad Stojanovic, (FZI - Research Center for Information Technologies at the University of Karlsruhe, Germany), Andreas Abecker (FZI, Germany), Opher Etzion (IBM Research Lab, Haifa, Israel). Adrian Paschke (Corporate Semantic Web, Free University Berlin, Germany and RuleML Inc, Canada) Program Committee ------------------ Alex Kozlenkov, Betfair Ltd. UK Brian Connell, WestGlobal, Ireland Christian Brelage, SAP, Germany Darko Anicic, FZI at the University of Karlsruhe, Germany David Luckham, Stanford University, USA Dieter Gawlick, Oracle, USA Gregoris Mentzas, ICCS, University of Athens, Greece Jean-Pierre Lorre, EBM Websourcing, France José Júlio Alferes, Faculdade de Ciências e Tecnologia/Universidade Nova de Lisboa, Portugal Jun-jang Jeng, IBM Watson Research Center, USA Ljiljana Stojanovic, FZI at the University of Karlsruhe, Germany Michal Rosen-Zvi, IBM Haifa Research Lab, Israel Pedro Bizarro, University of Coimbra, Portugal Prasad Vishnubhotla, IBM Software Group, USA Rainer von Ammon, CITT, Germany Ronen Vaisenberg UC Irvine, USA Segev Wasserkrug, IBM Haifa Research Lab, Israel ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev paschke< at >mi.fu-berlin.de 2008-10-24T17:47:08 http://comments.gmane.org/gmane.comp.java.drools.devel/2691 _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev Ravindran, Ratheesh (NSN - IN/Bangalore 2008-10-23T08:45:59 http://comments.gmane.org/gmane.comp.java.drools.devel/2689 Hi All, I am not sure whether it is the right place to put this question here. Currently I am working on rules and got confused with some concepts: What are the relationships between: resolution, backward chaining, modus ponens, foward chaining, production rule system, prolog, logic programming? Can all forward chaining systems be considered as logic programming system? Some of these concepts seems overlap with each other. Can somebody kindly give me an answer to these questions. Thanks in advance. Best Regards Wei _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev Wei Tai 2008-10-22T16:00:10 http://comments.gmane.org/gmane.comp.java.drools.devel/2688 Hi guys, I 'd like to redesign the current score subsystem in drools-solver, but I 'd like your thoughts on it. Basically I feed the subsystem a Solution instance on which the DRL rules calculate a score (currently a double). Here are my thoughts, feed-back very welcome: Score function standardization ============================== - Currently a score is a double and that just won't do - Different types of scores should be implementable: Geoffrey De Smet 2008-10-19T15:36:48 http://comments.gmane.org/gmane.comp.java.drools.devel/2682 _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev hare ram 2008-10-17T18:56:03 http://comments.gmane.org/gmane.comp.java.drools.devel/2666 _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev Ringo CS 2008-10-13T09:00:42 http://comments.gmane.org/gmane.comp.java.drools.devel/2661 [ our apologies should you receive this message more than one time ] AAAI Spring Symposium on Intelligent Event Processing AAAI Spring Symposium Wednesday, March 23-25, 2009 at Stanford University http://icep-aaai09.fzi.de/ ===================================================================== Event-based systems are now gaining increasing momentum as witnessed by current efforts in areas including event-driven architectures, business process management and modeling, Grid computing, Web services notifications, and message-oriented middleware. They become ever important in various application domains, ranging from traditional business applications, like supply-chain management, to the entertainment industry, like on-line gaming applications. However, the current status of development is just the tip of the iceberg compared with the impact that event processing could achieve, as already reported by market research companies. Indeed, existing approaches are dealing primarily with the syntactical (but very scalable) processing of low-level signals and primitive actions, which usually goes with an inadequate treatment of the notions of time, context or concurrency (for example, synchronization). For example, some of the current event processing products are descendents of the active database research that misses efficient (formal) handling of termination, priority ordering, and confluence in rule bases. AI and especially symbolic (for example, logic-based) approaches provide native background for the (formal) representation of the above mentioned missing concepts, enabling evolution from event processing systems into intelligent reactive systems. The work done in temporal logic, spatial reasoning, knowledge representation, ontologies, and so on enables more declarative representation of events and actions and their semantic processing. Contextual reasoning can support complex event prediction. Transactional logic can be used for ensuring the consistency between highly dependent processes in a formal way. On the other side, the heterogeneous and highly distributed nature of event-processing systems, especially on the web, provides new challenges for AI and logics, like the contextualized reasoning over large stream data, scalable mapping of complex structures, or distributed approximate reasoning, to name but a few. Possible symposium topics comprise, but are not limited to: ----------------------------------------------------------- Modeling * Conceptual modeling in event-driven processing * Modeling context in event-driven processing * Event processing languages * Business rules and event-driven processing * Editors for complex events * Complex event processing in highly distributed AI applications * Modeling reactive systems using event-driven processing * Event stream processing * Event-driven architecture for Intelligent Event Processing Discovery * Complex event patterns mining * Temporal aspects in event mining * Prediction of events * Discovery of similar event * Discovery of unknown events * Dealing with missing events Reasoning/Processing * Complex event detection * The role of logic in event processing * Distributed reasoning for events * Reasoning with uncertain events * Reasoning under real-time constraints * Complexity in reasoning for Intelligent Event Processing Advanced Applications * Distributed event processing as a basis for AI applications * Financial trading * Web / Internet of Things * Entertainment * Ubiquitous Computing/ Ambient Intelligence * Business Activity Monitoring * AI in global epidemiology monitoring systems * Other domains Submissions ----------- Papers should be prepared using the two-column AAAI conference paper format. Long papers should be at most six pages; short papers at most two pages. Papers must be submitted electronically via the symposium website. Submissions must be in PDF using the workshop submission system for SSS09, at http://www.easychair.org/conferences/?conf=sss09 More Information http://icep-aaai09.fzi.de/ Important Dates --------------- Deadline for submissions: October 31st, 2008 (12.00 AM, GMT) Notification of acceptance: December 9th, 2008 Camera-ready versions: January 16th, 2009 Symposium: March 23-25, 2009 Organizing Committee --------------------- Nenad Stojanovic, chair, (FZI - Research Center for Information Technologies at the University of Karlsruhe, Germany), Andreas Abecker (FZI, Germany), Opher Etzion (IBM Research Lab, Haifa, Israel). Adrian Paschke (RuleML Inc, Canada and Corporate Semantic Web, Free University Berlin, Germany) Program Committee ------------------ Alex Kozlenkov, Betfair Ltd. UK Brian Connell, WestGlobal, UK Christian Brelage, SAP, Germany Darko Anicic, FZI at the University of Karlsruhe, Germany David Luckham, Stanford University, USA Dieter Gawlick, Oracle, USA Gregoris Mentzas, ICCS, University of Athens, Greece Jean-Pierre Lorre, EBM Websourcing, France José Júlio Alferes, Faculdade de Ciências e Tecnologia/Universidade Nova de Lisboa, Portugal Jun-jang Jeng, IBM Watson Research Center, USA Ljiljana Stojanovic, FZI at the University of Karlsruhe, Germany Michal Rosen-Zvi, IBM Haifa Research Lab, Israel Pedro Bizarro, University of Coimbra, Portugal Prasad Vishnubhotla, IBM Software Group, USA Rainer von Ammon, CITT, Germany (to be completed) ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ rules-dev mailing list rules-dev< at >lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev paschke< at >mi.fu-berlin.de 2008-10-09T13:38:58 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.java.drools.devel