On 04/09/14 08:07, Stefan Henke wrote:
Hi, I have a question regarding model encapsulation and consumption by clients. In all jena examples I was able to find, schema data, asserted data and inferred data is separated into different models. You can see this very easy when using the createInfModel method.
No, that's not the case.
As a client you normally don´t bother about if the knowledge was asserted or inferred. Therefore, I tried to use Model.union() method to create one common model. However, it turned out that this is time consuming and from what I understood updates to one of the original models are not visible nor propagated to the unioned model. Is there a better approach?
The InfModel already is a (dynamic union) of the asserted data and the inferred data (including schema that has been bound in). There is no need to do any further union, just query that.
The complaints are normally the other way round :) The forward deductions are also separately available (getDeductionsModel) but are included in the InfModel union. However, backward deductions are not separately available (by definition they may only be created in response to a query).
Dave
