Re: RDFSExptRuleReasoner / stopping early (JENA-1719)

On 30/06/2019 10:42, Dave Reynolds wrote: Having spent some more time on this I still can't find a safe fix to the underlying problem but have created a brute force work around. https://github.com/apache/jena/pull/580 As it says in the PR it might need some serious redesign of the backward

Re: RDFSExptRuleReasoner / stopping early (JENA-1719)

Having spent some more time on this I still can't find a safe fix to the underlying problem but have created a brute force work around. https://github.com/apache/jena/pull/580 As it says in the PR it might need some serious redesign of the backward engine to properly fix the underlying issue,

Re: RDFSExptRuleReasoner / stopping early (JENA-1719)

I've spent some time on this but with limited results. At heart this looks a long standing and deep seated bug in the backward chainer but I'm not yet sure how to safely fix it. I can reproduce the problem fine using the recipe in the ticket but haven't yet managed to create a stand alone test

Re: RDFSExptRuleReasoner / stopping early (JENA-1719)

Even just some pointers as to where in the code it should close TopLevelTripleMatchFrame would be helpful if getting it setup is a barrier. (if it should close it) I don't know the rules codes well enough. --- The example on JENA-1719 after editing the and tdb2:location runs.

Re: RDFSExptRuleReasoner / stopping early (JENA-1719)

Hi Andy, Sure, I'll try to take a look over the weekend if I can get a working dev environment set up. Dave On 07/06/2019 13:46, Andy Seaborne wrote: Dave, I am hoping you can give me a some pointers so I can solve JENA-1719. https://issues.apache.org/jira/browse/JENA-1719 Setup:   data i

RDFSExptRuleReasoner / stopping early (JENA-1719)

Dave, I am hoping you can give me a some pointers so I can solve JENA-1719. https://issues.apache.org/jira/browse/JENA-1719 Setup: data in TDB2. ontology in a memory model. RDFSExptRuleReasoner First query has a short limit: select * where {?s a } limit 1 T