- From: Boley, Harold <Harold.Boley@nrc-cnrc.gc.ca>
- Date: Sun, 4 Dec 2005 20:22:36 -0500
- To: <public-rif-wg@w3.org>
- Message-ID: <E4D07AB09F5F044299333C8D0FEB45E90116DED0@nrccenexb1.nrc.ca>
** NRC-2 FOAF rules * Description Ben has created his person-centric metadata in the form of a FOAF document as has become popular, covering unconditional properties about his personal interests, friends, etc. However, he also needs to specify properties conditional on other persons, the time, the location, etc. For example, Ben prefers to specify his work time and free time s.t. his colleagues can contact him when at work, while his friends can reach him when off work. Consequently, with rules, his schedule might look as follows: Monday - Friday IF 09:00 AM - 12:00 AM, THEN call my office number IF 13:00 AM - 17:00 AM, THEN call my office number IF 18:00 AM - 21:00 AM, THEN call my home number IF 12:00 AM - 13:00 AM, THEN call my cell number IF 17:00 AM - 18:00 AM, THEN call my cell number IF 21:00 AM - 09:00 AM, THEN do not call me Saturday, Sunday, Holidays IF 09:00 AM - 21:00 AM, THEN call my cell number IF 21:00 AM - 09:00 AM, THEN do not call me A general methodology for rules added to FOAF has been elaborated in RuleML FOAF [1], extending the factual FOAF vocabulary with RuleML rules. The rule engine OO jDREW [2] has been employed to run such FOAF rules. * Implications Person-centric, local rules imply the requirement of a scoping construct also for positive queries. For more and more global rules, an increasing number of such scopes need to be merged, so there is the requirement of unlimited import of local rulebases into a new scope. Since the current FOAF is based on RDF, it is required that the FOAF subset of RDF be also expressible as facts of the rule language, that the rules are able to cope with such facts, and that the rule-derived facts can be (XSLT-)translated back to RDF. [1] http://www.ruleml.org/usecases/foaf [2] http://www.jdrew.org/oojdrew
Received on Monday, 5 December 2005 01:25:43 UTC