Why to use Semantics and Rules in your Services.

The question is why should I use Semantics and rules and when?
Well, using semantics or rules should be another tool in you toolset. And it's a very useful one, even though is very underrated maybe because it´s never been easy to use. Or because semantic or functional programming has never been that popular.
That is changing nowaydays because of SOA and BPM's, that rely heavily upon on Business Rules, specially sSOA.

With the jServiceRules / jSemanticService frameworks I tried to cover up some of that gaps:

# Writing semantic services or agents in a easy way, just writing some rules files (and the service).

# Adapting the BRE to Services and Java environments.

# Integration with another third party frameworks.

When to use Semantics or Rules

In a Enterprise Environment these are some of the cases in which you could use jServiceRules or jSematicService:

# If you need smart agents or services (for example a service that will recommend your tv favorites series of the day).

# If you have a complex model you could write a semantic model to process it.

# Business rules that would change over the time.

# Business rules that you'd like to isolate from the code.

# Business rules that you'd need to edit in a simple way, using a scripting language (so you don't need to compile),

# Different types of events or objects you'd want to recognize and process.