Great thoughts. If you don't mind, head to http://jira.werken.com/
and file them there.
> 2. Abstract Interpreter
> If the scripting bit in org.drools.semantic.java was abstracted out some
> more (i.e. having a drools Interpreter interface etc.) then it should be
> straightforward to add other interpreters, e.g. Python (using Jython).
Yah, we're using bsh for the action interpreter, but for the conditions,
we have to analyze them a bit, with the custom ANTLR java language
interpreter. If we have an abstract interpreter, it must be able
to exec the actions (no problem), but also give up the analysis of
the condition expressions, whatever the language may be.
Though, that might just be cause of a Jython semantic module, since
it's using jython semantics, and not Java. Dunno.
> 3. Abstract XML
> The bits in org.drools.semantic.java.io seem to mix the Java parsing in with
> the XML parsing, again it might be an idea to abstract the dom4j bits, which
> should make extension more straightforward, and also make it easier to plug
> in Xerces or whatever instead (this might also be helpful with the RDF
> module).
Yah, the XML semantic module was a real quick hack just to prove that we
can actually handle multiple semantics. I wouldn't suggest that anyone
uses the XML module as-is. It's pretty weak.
> Let me know what you reckon, I could make a start on these (if approved), as
> soon I know I've got the latest source.
Poke'em into Jira, and then we can get a view of what needs to be done.
There's going to be a little bit of re-architecting to drools soon, so I'd
hate for you to make lots of little changes that disappear when I reorg
the semantic modules, or something.
-bob
-------------------------------------------------------
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
