Candide, Not to undercut JESS, but there already exists an inferencing engine for RDF that you might to want to evaluate - it's name is RDFExpert. The author is Craig Pugsley from Oxford Brookes University & Baltimore Technologies.
Rich Halsey ----- Original Message ----- From: "Candide Kemmler" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, May 23, 2002 3:13 PM Subject: JESS: facts and persistence > Hi, > > I'm considering a number of alternatives for the implementation of a > distributed query system based on rdf. > > The main difficulty I'm facing so far is to allow for the persistence of > the rules-infered facts that would arise from data coming from the > outside world (i.e. from outside peers). > > To handle the persistence of facts, I've found the following > interesting. Please, I would be very, very grateful if you'd tell me of > the respective qualities/flaws of these solutions: > > - IBM commonrules: allows persistence through the use of > sensors/effectors; seems nobody's using it though; > > - JESS/Fact Storage Provider Framework: looks very interesting indeed; > only it's not much talked about; seems nobody's ever tested it with the > DBMS's _I_ use: PostgreSQL and MySQL, if ever tested _at all_; Does it > help to reduce the memory consumption of JESS ? If it does, why isn't it > considered a VERY interesting piece of software, I mean it should be put > on the homepage of JESS. > > - Aditi: well, apart the fact that Microsoft poured millions of dollars > to port Mercury, the (logical) language it's written it, apparently > nobody cares. It's the only deductive object-oriented database > management system I know that 1) handles persistence (well, I thought > that was the least you could expect from something you call a > _database_, but it seems calling something a _database_ doesn't do the > trick, as the XSB system demonstrates: it's a _database_ only it works > only in central memory, GREAT !) and 2) seems to be support by a small > community of users/researchers with some cash. > > There's something I must be missing here: everybody talks about rules, > yet managing persistence and transactions which is of course a major > requirement for business systems seems to be completely overlooked. Very > few systems that handle the persistence of rule engines seem to exist, > and they seem to come from the initiatives of lonely researchers working > for their own in their remote laboratories. > > Thanks in advance for the enlightened help of those more experienced on > this list... > > > candide > > > > -------------------------------------------------------------------- > To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' > in the BODY of a message to [EMAIL PROTECTED], NOT to the list > (use your own address!) List problems? Notify [EMAIL PROTECTED] > -------------------------------------------------------------------- > -------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED] --------------------------------------------------------------------
