|
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
The minimal interface to which all reasoners (or reasoner adaptors) conform. This only supports attaching the reasoner to a set of RDF graphs which represent the rules or ontologies and instance data. The actual reasoner requests are made through the InfGraph which is generated once the reasoner has been bound to a set of RDF data.
Method Summary | |
InfGraph |
bind(Graph data)
Attach the reasoner to a set of RDF data to process. |
Reasoner |
bindSchema(Graph tbox)
This is most commonly used to attach an ontology (a set of tbox axioms in description logics jargon) to a reasoner. |
Reasoner |
bindSchema(Model tbox)
This is most commonly used to attach an ontology (a set of tbox axioms in description logics jargon) to a reasoner. |
Model |
getCapabilities()
Return a description of the capabilities of this reasoner encoded in RDF. |
void |
setDerivationLogging(boolean logOn)
Switch on/off drivation logging. |
void |
setParameter(java.lang.String parameterUri,
java.lang.Object value)
Set a configuration parameter for the reasoner. |
boolean |
supportsProperty(Property property)
Determine whether the given property is recognized and treated specially by this reasoner. |
Method Detail |
public Reasoner bindSchema(Graph tbox) throws ReasonerException
In fact this call may be more general than the above description suggests. Firstly, a reasoner that supports arbitrary rules rather than ontologies may use the same method to bind the reasoner to the specific rule set (encoded in RDF). Secondly, even in the ontology case a given reasoner may not require a strict separation of tbox and abox - it may allow instance data in the tbox and terminology axioms in the abox.
A reasoner is free to simply note this set of RDF and merge with any future RDF rather than do processing at this time.
tbox
- the ontology axioms or rule set encoded in RDF
ReasonerException
- if the reasoner cannot be
bound to a rule set in this way, for example if the underlying engine
can only accept a single rule set in this way and one rule set has
already been bound in of if the ruleset is illformed.public Reasoner bindSchema(Model tbox) throws ReasonerException
In fact this call may be more general than the above description suggests. Firstly, a reasoner that supports arbitrary rules rather than ontologies may use the same method to bind the reasoner to the specific rule set (encoded in RDF). Secondly, even in the ontology case a given reasoner may not require a strict separation of tbox and abox - it may allow instance data in the tbox and terminology axioms in the abox.
A reasoner is free to simply note this set of RDF and merge with any future RDF rather than do processing at this time.
tbox
- the ontology axioms or rule set encoded in RDF
ReasonerException
- if the reasoner cannot be
bound to a rule set in this way, for example if the underlying engine
can only accept a single rule set in this way and one rule set has
already been bound in of if the ruleset is illformed.public InfGraph bind(Graph data) throws ReasonerException
data
- the RDF data to be processed, some reasoners may restrict
the range of RDF which is legal here (e.g. syntactic restrictions in OWL).
ReasonerException
- if the data is ill-formed according to the
constraints imposed by this reasoner.public void setDerivationLogging(boolean logOn)
Default - false.
public void setParameter(java.lang.String parameterUri, java.lang.Object value)
parameterUri
- the uri identifying the parameter to be changedvalue
- the new value for the parameter, typically this is a wrapped
java object like Boolean or Integer.public Model getCapabilities()
public boolean supportsProperty(Property property)
property
- the property which we want to ask the reasoner about
|
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |