User Preference Rules. The preference rules enable user assertions over subjective personal preferences. There is no standard of comparison for Qualifying Conditions and Business Values as they are a matter of user preference. For example, one service may be more active during the weekend in which case a provider with a condition stating that the objective may only be guaranteed if it is a weekday would not be suitable for that user. The matcher is unaware of the personal circumstances of each user until they are defined using rules. A rule may assert one of two possible assertions which will have an impact on matching: isPreferred or notSuitable. A user may write a rule to assert that “a guarantee that has a condition that the day of the week must be a weekday is not suitable” or “a guarantee with a condition involving transactionRate is preferred over a guarantee with a condition involving the day of the week”. These rules have the flexibility to be more specific or generic. The following ARL rule asserts that a weekday condition is not suitable for this user: when: Agreement (A) and hasGuarantee (A, G1) and hasQualifyingCondition(G1, QC1) which hasExpression(QC1, E1) and hasParameter(E1, “time:dayOfWeek”) and hasValue(E1, “time:weekday”) do: assert Guarantee notSuitable G1 The above rule asserts that a guarantee is notSuitable if the parameter of the Qualifying Condition is the dayOfWeek and if the value is weekday. Conflicting rules are resolved by using optional priority and condition fields.
Appears in 2 contracts
Sources: Ws Agreement, Ws Agreement