| com.hp.hpl.jena.rdf.model.InfModel
All known Subclasses: com.hp.hpl.jena.rdf.model.impl.InfModelImpl,
| InfModel | | public interface InfModel extends Model(Code) | | An extension to the normal Model interface that supports access to any
underlying inference capability.
In Jena the primary use of inference is
to generate additional entailments from a set of RDF data. These entailments
just appear as additional RDF data in the inferred model and are accessed
through the normal API. For example, if an inference engine can determine
the class of a resource "foo" is "fooClass" then all Model API calls such
as listStatements and getProperty should act as if the triple:
foo rdf:type fooClass .
were in the data.
A few reasoner services cannot be made directly available in this way
and the InfGraph extension gives access to these - specifically access to
validation/consistency checking, derivation traces and find-with-posits.
Note that this interface, and especially the interface onto ValidityReports
and Derivations are not yet stable.
author:
Dave Reynolds
version:
$Revision: 1.13 $ on $Date: 2008/01/02 12:05:46 $ |
| getDeductionsModel | | public Model getDeductionsModel()(Code) | | Returns a derivations model. The rule reasoners typically create a
graph containing those triples added to the base graph due to rule firings.
In some applications it can useful to be able to access those deductions
directly, without seeing the raw data which triggered them. In particular,
this allows the forward rules to be used as if they were rewrite transformation
rules.
the deductions model, if relevant for this class of inferenceengine or null if not. |
| getDerivation | | public Iterator getDerivation(Statement statement)(Code) | | Return the derivation of the given statement (which should be the result of
some previous list operation).
Not all reasoneers will support derivations.
an iterator over Derivation records or null if there is no derivation informationavailable for this triple.
See Also: com.hp.hpl.jena.reasoner.Derivation
See Also: Derviation |
| getRawModel | | public Model getRawModel()(Code) | | Return the raw RDF model being processed (i.e. the argument
to the Reasonder.bind call that created this InfModel).
|
| getReasoner | | public Reasoner getReasoner()(Code) | | Return the Reasoner which is being used to answer queries to this graph.
|
| listStatements | | public StmtIterator listStatements(Resource subject, Property predicate, RDFNode object, Model posit)(Code) | | Find all the statements matching a pattern.
Return an iterator over all the statements in a model
that match a pattern. The statements selected are those
whose subject matches the subject argument,
whose predicate matches the predicate argument
and whose object matchesthe object argument.
If an argument is null it matches anything.
The s/p/o terms may refer to resources which are temporarily defined in the "posit" model.
This allows one, for example, to query what resources are of type CE where CE is a
class expression rather than a named class - put CE in the posit arg.
an iterator over the subjects
Parameters:
subject - The subject sought
Parameters:
predicate - The predicate sought
Parameters:
object - The value sought |
| prepare | | public void prepare()(Code) | | Perform any initial processing and caching. This call is optional. Most
engines either have negligable set up work or will perform an implicit
"prepare" if necessary. The call is provided for those occasions where
substantial preparation work is possible (e.g. running a forward chaining
rule system) and where an application might wish greater control over when
this prepration is done rather than just leaving to be done at first query time.
|
| rebind | | public void rebind()(Code) | | Cause the inference model to reconsult the underlying data to take
into account changes. Normally changes are made through the InfModel's add and
remove calls are will be handled appropriately. However, in some cases changes
are made "behind the InfModels's back" and this forces a full reconsult of
the changed data.
|
| reset | | public void reset()(Code) | | Reset any internal caches. Some systems, such as the tabled backchainer,
retain information after each query. A reset will wipe this information preventing
unbounded memory use at the expense of more expensive future queries. A reset
does not cause the raw data to be reconsulted and so is less expensive than a rebind.
|
| setDerivationLogging | | public void setDerivationLogging(boolean logOn)(Code) | | Switch on/off drivation logging. If this is switched on then every time an inference
is a made that fact is recorded and the resulting record can be access through a later
getDerivation call. This may consume a lot of space!
|
| validate | | public ValidityReport validate()(Code) | | Test the consistency of the underlying data. This normally tests
the validity of the bound instance data against the bound
schema data.
Logically inconsistent models will be indicated by a ValidityReport which
reports isValid() as false. Additional non-fatal problems, such as uninstantiatable classes,
may be reported as warnings.
a ValidityReport structure |
|
|