[Pellet-users] Incremental Reasoning.

[Alex Pinheiro das Graças]

Yes, you're right Michael. So I will redo mu question
I'd like to know is it is usable the incremental researching
Based on what Chris said ( Thank you for explanation Chris)
I will build the application in this way
Use incremental for add individual
but for deletions I will redo the reasoning model.

Pellet incremental reasoning is stable for adding, right?


On Wed, May 28, 2008 at 12:51 PM, Michael Smith <msmith at clarkparsia.com>
wrote:

> On Wed, 2008-05-28 at 12:25 -0300, Alex Pinheiro das Graças wrote:
>
> > I am have a situation I have to work with a changing knowledge base.
> > By now it will be added/deleted individual and properties ( ABox ,
> > right?). So I'd like what is better...
> > work with incremental reasoning or Concurrency control?
>
> These things are not alternatives.  If you have a changing ABox
> incremental reasoning may reduce the time to get reasoning results.
> Concurrency means accessing the KB from multiple threads, which should
> be considered carefully, totally independently of incremental reasoning,
> since many reasoner activities change the reasoner's internal state.
>
> > I am working with Jena. Can I use the Jena API or is better to use the
> > pellet API to do concurrency control?
>
> There is an FAQ entry discussing concurrency via the Jena interface at
> [1].  We have not documented thread safety for applications using the
> Pellet API directly - I would discourage attempting this with the
> current release.
>
> --
> Mike Smith
>
> Clark & Parsia
>
> [1]
> http://pellet.owldl.com/faq/how-do-i-use-pellet-with-jena-concurrently/
>
>


-- 
Alex Pinheiro das Graças
UFES
Vitória, Brasil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.owldl.com/pipermail/pellet-users/attachments/20080528/3ff2b53a/attachment.htm