=What it is?
ActiveRDF Rules is a rule base and forward chaining production system for
ActiveRDF. It can be used to process rules programatically at will, or using a
mix-in class you can have it process rules every time a triple is added to the
data store. The rules are stored in memory, and can be defined using a DSL. It comes
with a couple of prebuilt rule bases for RDF Schema and OWL reasoning.
=What it is not?
* It is not high performance.
* The rules are stored in memory, so don't add a lot of them.
* It supports RDF Schema and *some* basic OWL reasoning through the built-in
rule bases, but they are *basic*. Feel free to not use them and just define
your own.
* It does not support restrictions. I'm probably going to add restriction
rules at some point, but I haven't thought through it all just yet.
* It is not stable. I mean it's stable; I have tested it pretty thoroghly as
far as its current features go, but I reserve the right to change the
implementation, interface, and anything else. I might even change the name of
the project. If you're that concerned, then fork the code, and keep a copy for
yourself. However, I will do my best to make sure that the implementation and
interface evolve in a way that it breaks as little existing code as possible.
=What next?
Take a look at the documentation. Especially look at the person_example.rb
file. It contains a pretty heavily annotated example. If you have (or will)
install this as a gem, then look for that in the gem directory
(/usr/lib/ruby/gems/1.8/gems/activerdf-rules-X.X/examples) or some such
nonsense.
ActiveRDF Rules is a rule base and forward chaining production system for
ActiveRDF. It can be used to process rules programatically at will, or using a
mix-in class you can have it process rules every time a triple is added to the
data store. The rules are stored in memory, and can be defined using a DSL. It comes
with a couple of prebuilt rule bases for RDF Schema and OWL reasoning.
=What it is not?
* It is not high performance.
* The rules are stored in memory, so don't add a lot of them.
* It supports RDF Schema and *some* basic OWL reasoning through the built-in
rule bases, but they are *basic*. Feel free to not use them and just define
your own.
* It does not support restrictions. I'm probably going to add restriction
rules at some point, but I haven't thought through it all just yet.
* It is not stable. I mean it's stable; I have tested it pretty thoroghly as
far as its current features go, but I reserve the right to change the
implementation, interface, and anything else. I might even change the name of
the project. If you're that concerned, then fork the code, and keep a copy for
yourself. However, I will do my best to make sure that the implementation and
interface evolve in a way that it breaks as little existing code as possible.
=What next?
Take a look at the documentation. Especially look at the person_example.rb
file. It contains a pretty heavily annotated example. If you have (or will)
install this as a gem, then look for that in the gem directory
(/usr/lib/ruby/gems/1.8/gems/activerdf-rules-X.X/examples) or some such
nonsense.