Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="reanjr" data-source="post: 2142088" data-attributes="member: 20740">I see it as a bit more complicated than that.  I see rules, data, engine, application, and gui.  I see data (as in character data) and rules (which you describe as data) as being two very similar, yet separate layers (both XML data, one higly mutable, one not).  Engine is a simplistic mechanism for interpreting the rules layer.  The application works with the engine layer to "apply" the rules to the data in the goal of transforming the data into a new, internal set (I guess you could call this the tranformation layer) that is then exposed to the GUI layer for final presentation and interaction.I feel that the data, engine, gui abstraction works well for transactional business software (especially for load balancing and security), but in a small application (small in the sense that is designed to run locally and it's not critical software), it simplifies things in a way that makes it difficult (though not impossible) to do certain things. Can't disagree there (at least not ideologically).  But I do think the code (in this case what I call the rules layer) should be represented and exposed as data so that it can be easily modified, tranformed, erratad, house ruled, etc.This is what I call the rules layer.  I am not familiar with SWRL, but I do think RDF-OWL and to a lesser extent, RuleML are kind of the wrong angle of approach.  I think coming up with a dedicated markup language could greatly simplify the end users' (house rulers') lives.  I would take some convincing to believe those standards would be worth implementing for this purpose.  Seems like overkill in development that would only slow things down later.The only thing I would like to add is that I think the .NET framework is worth looking at as it has the best balance of cross-platform and language-independence. (snipped image, see above)Don't take this the wrong way (it's mostly a joke), but it is my humble opinion that flow charts and data models are for presenting to the executives so that they can have input and thus slow down the progress of developers.</blockquote>

Verification