Pre-Grant Publication Number: 20110022575
Please help the USPTO examine the application by evaluating the relevance of the publicly submitted prior art to the patent application.
Peer To Patent forwards the Top 10 most relevant prior art submissions and their annotations to the USPTO.
Review this prior art and click on the thumbs up (or down) to indicate whether this submission should be forwarded to the USPTO.
If you login then you can add an annotation by typing in the box at the bottom of the screen to comment on the relevance of the prior art to the claims of the patent application.
Review this prior art and click on the thumbs up (or down) to indicate whether this submission should be forwarded to the USPTO.
If you login then you can add an annotation by typing in the box at the bottom of the screen to comment on the relevance of the prior art to the claims of the patent application.
Prior Art Detail
Summary / Description
| Summary / Description | In this article main business rules system components (business rules repository and business rules engine) are discussed. The business rules repository is a database that stores all the data about the business rules and all the necessary metadata about entities, attributes and relationships. [...] Steps of gathering such data are discussed and graphical schema is presented. Events that activate business rules and steps of their managing are discussed. |
Basic Information
| Type of Prior Art | Online Publication |
| URL | http://www.iadis.net/dl/final_u... |
| Author/Creator | Rimantas Butleris & Liudas Motiejunas |
| Title | METADATA FOR BUSINESS RULES INTEGRATION |
| Publication Date | 2005 |
| Publisher | IADIS Virtual Multi Conference on Computer Science and Information Systems |
| Directions to Document Location | |
| Additional Information | |
Notes / To Do
| Notes | |
Excerpt
Excerpt The business rules engine calls business rules from business rules repository and performs actions
described by the rule. Business rules engine can be implemented in various ways (Ross, 2003; Wilson, 2003),
the same as business rules repository, because its architecture depends on business rules repository (the form that business rules are stored in it). In this paper we are talking about business rules engine that primarily
deals with databases. Business rules engine “must know” what business data it has to deal with during a
business rule execution. That is why we must keep additional data about tables, attributes and relationships
existing in the database in the business rules repository. |
Relevance
Claims
1
Relevance
The publication describes business rules and a related meta data repository conceptually similar to the first part of claim 1. It further describes a business rules engine that loads and executes/enforces the business rules during events (e.g., development steps). No reference is made in the publication to a "meta system object", which also does not appear to be defined in the current application, though it appears in claim 1; perhaps it is a subcomponent of a business rules engine, as the application attributes that kind of checking to an important class called the Meta System. The last part of claim 1 requires careful parsing. I believe that taken literally it simply says that enforcing the rules can avoid at least one run-time test combination. Surely that is not a new contribution over any existing business rule system.
The publication describes business rules and a related meta data repository conceptually similar to the first part of claim 1. It further describes a business rules engine that loads and executes/enforces the business rules during events (e.g., development steps). No reference is made in the publication to a "meta system object", which also does not appear to be defined in the current application, though it appears in claim 1; perhaps it is a subcomponent of a business rules engine, as the application attributes that kind of checking to an important class called the Meta System. The last part of claim 1 requires careful parsing. I believe that taken literally it simply says that enforcing the rules can avoid at least one run-time test combination. Surely that is not a new contribution over any existing business rule system.
Claim Chart
All
0 days left
