All Classes and Interfaces
Class
Description
The DiffModule computes differences and similarities between concepts.
This class allows the registration of event by external client through
the
#registerEvent(String, String, Set, IEventConsumer)
RPC method.This class holds unit tests that cover the events feature in
oro-server
.This class provides various static helper methods for some common parsing and formatting tasks.
This interface is intended to be implemented by classes that are expected to
be notified when some event occurs, thus consuming the event.
This exception is thrown when a literal statement is malformed (eg, 2 tokens instead of three).
Modules must implement this interface to be loaded at runtime.
This exception is thrown when a event is registered with invalid parameters.
This exception is thrown when a SWRL rule is malformed.
This interface describes the abstract behaviour of an ontology backend.
This interface sole purpose is to signal that a class implement services for the oro-server (ie, methods annotated with a
RPCMethod
annotation).Interface to patterns that may trigger events.
Constants that defines the type of event the event module can handle.
Constants that defines the way an event is triggered.
A class loader for loading jar files, both local and remote.
A JSONArray is an ordered sequence of values.
The JSONException is thrown by the JSON.org classes when things are amiss.
A JSONObject is an unordered collection of name/value pairs.
The
JSONString
interface allows a toJSONString()
method so that a class can change the behavior of
JSONObject.toString()
, JSONArray.toString()
,
and JSONWriter.value(
Object)
.A JSONTokener takes a source string and extracts characters and tokens from
it.
This class provides several static method for namespace manipulation (expansion, contraction, SPARQL prefixes header...).
This class specializes
GenericWatcher
to easily create event watchers
that monitor new instances of a given class.This exception is thrown when a two concepts are compared but are not of the same nature (for instance, a comparison between a class and an instance would throw a NotComparableException).
The OpenRobotsOntology class is the main storage backend for oro-server.
It maps useful methods for knowledge access in a robotic context to a Jena-baked
Amongst other feature, it offers an easy way to query the ontology with standard SPARQL requests, it can try to find resources matching a set of statements or check the consistency of the knowledge storage.
Examples covering the various aspects of the API can be found in the Unit Tests.
It maps useful methods for knowledge access in a robotic context to a Jena-baked
ontology
.Amongst other feature, it offers an easy way to query the ontology with standard SPARQL requests, it can try to find resources matching a set of statements or check the consistency of the knowledge storage.
Examples covering the various aspects of the API can be found in the Unit Tests.
This class holds unit tests that cover most of the
For the tests to be executed, the
oro-server
features.For the tests to be executed, the
oro_test.owl
ontology is required, and must be referenced by the oro_test.conf
configuration file.OroServer
is the application entry point.A partial statement is a statement whose at least one element (subject, predicate or object) is unknown.
To be valid, a partial statement must have at least one variable, prepended with a "?".
This class holds more advanced unit tests that tests load scalability and some more advanced reasonning feature.
This annotation marks all the available methods exposed to remote clients.
To actually register your services by the server, you just need to annotate the relevant method with a @RPCMethod annotation and to call the
To actually register your services by the server, you just need to annotate the relevant method with a @RPCMethod annotation and to call the
OroServer.addNewServiceProviders(IServiceProvider)
method.Implements a socket interface to
The protocol is ASCII-based (ie, you can connect to the server with telnet to test everything).
oro-server
RPC methods.The protocol is ASCII-based (ie, you can connect to the server with telnet to test everything).
This enum defines the various possible verbosity levels for server messages.