In this page we present a full example of using DR-DEVICE rules in a brokered trade application that takes place via an independent third party, the broker. The broker matches the buyer's requirements and the sellers' capabilities, and proposes a transaction when both parties can be satisfied by the trade. In our case, the concrete application (which has been adopted from G. Antoniou, F. van Harmelen, "A Semantic Web Primer", MIT Press, 2004) is apartment renting and the landlord takes the role of the abstract seller.
Available apartments reside in an RDF document. The requirements of a potential renter, called e.g. Carlo, are shown in the following table:
Apartment Requirements
Price Requirements
Preferences
|
These requirements are expressed in:
After the rule document is loaded into DR-DEVICE, it is transformed into the native DR-DEVICE syntax, via an XSLT transformation. DR-DEVICE rules are further translated into R-DEVICE rules, which in turn are translated into CLIPS production rules. Then the RDF document is loaded and transformed into CLIPS (COOL) objects. Finally, the reasoning can begin, which ends up with 3 acceptable apartments and one suggested apartment for renting, according to Carlo’s requirements and the available apartments. The results (i.e. objects of d-rived classes) are exported in an RDF file according to the specifications posed in the RuleML document.
For any comments regarding this page contact Nick Bassiliades.