- From: Evren Sirin <evren@cs.umd.edu>
- Date: Wed, 05 Nov 2003 11:47:21 -0500
- To: Monika Solanki <monika@dmu.ac.uk>
- Cc: www-ws <www-ws@w3c.org>, pfps@research.bell-labs.com, horrocks@cs.man.ac.uk
Monika Solanki wrote: > > This is a refinement ( I think) where I have removed the > sameIndividualAtom construct and defined classAtom for each variable > > Input Classes, > > <process:Input rdf:ID="AcctID"/> > <process:Input rdf:ID="Password"/> > <process:Input rdf:ID="CreditCardNumber"/> > <process:Input rdf:ID="ISBNNumber"/> > > In ORL, we have to define "Variable" to be used in Rules. > > <owl:Variable rdf:ID="AcctID"/> > <owl:Variable rdf:ID="Password"/> > <owl:Variable rdf:ID="CreditCardNumber"/> > <owl:Variable rdf:ID="ISBNNumber"/> > Now, we can define the rule as, > > <!-- here the namespace congoUserProfile, holds the definition of > classes and properties pertaining to a user of Congo --> > <owl:Rule> > <owl:antecedent rdf:parseType="Collection"> > <owl:classAtom> > <owk:classPredicate rdf:about="&congoProcess;AccID"> > <owl:argument1 rdf:about="#AcctID" /> > </owl:classAtom> &congoProcess;AcctID was defined as an individual of type process:Input. Using this individual in the classPredicate is not correct. I think the main problem here is how to represent the value of a parameter for the process. The rule is defined to say something about the relation between the values of parameters. If the individual given for AcctID input is related to the individual given for Password with the property accountExists and so on. I don't think you can express this rule without a reference for the value of the process parameter. If I remember correctyly at point it was discussed to have a property as parameterValue for this purpose and Bijan was suggesting to use two different properties. I believe we can use these kind of properties to define this rule but I don't see anything about this in Process.owl yet. Any thoughts? Evren > <owl:classAtom> > <owk:classPredicate rdf:about="&congoProcess;Password"> > <owl:argument1 rdf:about="#Password" /> > </owl:classAtom> > <owl:classAtom> > <owk:classPredicate > rdf:about="&congoProcess;CreditCardNumber"> > <owl:argument1 rdf:about="#CreditCardNumber" /> > </owl:classAtom> > <owl:classAtom> > <owk:classPredicate rdf:about="&congoProcess;ISBNNumber"> > <owl:argument1 rdf:about="#ISBNNumber" /> > </owl:classAtom> > <owl:individualPropertyAtom> > <owl:propertyPredicate > rdf:resource="&congoUserProfile;accountExists/> > <owl:argument1 rdf:about="#AcctID" /> > <owl:argument2 rdf:about="#Password" /> > </owl:individualPropertyAtom> > <owl:individualPropertyAtom> > <owl:propertyPredicate > rdf:resource="&congoUserProfile;creditExists/> > <owl:argument1 rdf:about="#AcctID" /> > <owl:argument2 rdf:about="#CreditCardNumber" /> > </owl:individualPropertyAtom> </owl:antecedent> > <owl:consequent rdf:parseType="Collection"> > <owl:individualPropertyAtom> > <owl:propertyPredicate > rdf:resource="&congoUserProfile;allowedToBuy/> > <owl:argument1 rdf:about="#AcctID" /> > <owl:argument2 rdf:about="#ISBNNumber" /> > </owl:individualPropertyAtom> <owl:Rule> > > Feedback Appreeciated. > > Thanks, > > Monika
Received on Wednesday, 5 November 2003 11:49:10 UTC