[jboss-svn-commits] JBL Code SVN: r19794 - labs/jbossrules/branches/irooskov_docs/drools-docs/drools-docs-referenceguide/en/Chapter-JSR94.

[jboss-svn-commits at lists.jboss.org]

Author: irooskov at redhat.com
Date: 2008-05-01 00:35:19 -0400 (Thu, 01 May 2008)
New Revision: 19794

Modified:
   labs/jbossrules/branches/irooskov_docs/drools-docs/drools-docs-referenceguide/en/Chapter-JSR94/Section-Introduction.xml
Log:
updated Introduction section of Java Rule engine for reference guide


Modified: labs/jbossrules/branches/irooskov_docs/drools-docs/drools-docs-referenceguide/en/Chapter-JSR94/Section-Introduction.xml
===================================================================
--- labs/jbossrules/branches/irooskov_docs/drools-docs/drools-docs-referenceguide/en/Chapter-JSR94/Section-Introduction.xml	2008-05-01 04:30:17 UTC (rev 19793)
+++ labs/jbossrules/branches/irooskov_docs/drools-docs/drools-docs-referenceguide/en/Chapter-JSR94/Section-Introduction.xml	2008-05-01 04:35:19 UTC (rev 19794)
@@ -4,23 +4,22 @@
 
   <para>Drools provides an implementation of the Java Rule Engine API (known
   as JSR94), which allows for support of multiple rule engines from a single
-  API. JSR94 does not deal in anyway with the rule language itself. W3C (World Wide Web Consortium) is
+  API. JSR94 does not deal in any way with the rule language itself. W3C (World Wide Web Consortium) is
   working on the <ulink
   url="http://www.w3.org/TR/2006/WD-rif-ucr-20060323/">Rule Interchange Format
   (RIF)</ulink> and the OMG (Object Management Group) has started to work on a standard based on <ulink
   url="http://ruleml.org/">RuleML</ulink>, recently Haley Systems has also
   proposed a rule language standard called RML.</para>
 
-  <para>It should be remembered that the JSR94 standard represents the "least
-  common denominator" in features across rule engines - this means there is
-  less functionality in the JSR94 api than in the standard Drools api. So by
-  using JSR94 you are restricting yourself in taking advantage of using the
+  <para>It should be remembered that the JSR94 standard represents the <emphasis>least
+  common denominator</emphasis> in features across rule engines, meaning there is
+  less functionality in the JSR94 api than in the standard Drools API. So by
+  using JSR94 a user is restricting themself in taking advantage of using the
   full capabilities of the Drools Rule Engine. It is necessary to expose
   further functionality, like globals and support for drl, dsl and xml via
-  properties maps due to the very basic feature set of JSR94 - this introduces
-  non portable functionality. Further to this, as JSR94 does not provide a
-  rule language, you are only solving a small fraction of the complexity of
-  switching rule engines with very little gain. So while we support JSR94, for
-  those that insist on using it, we strongly recommend you program against the
+  properties maps due to the very basic feature set of JSR94m, introducing
+  non-portable functionality. Further to this, as JSR94 does not provide a
+  rule language, only a small fraction of the complexity of switching rule engines is being solved with very little gain. So while Drools supports JSR94, for
+  those that insist on using it, we strongly recommend programming against the
   Drools API.</para>
 </section>
\ No newline at end of file