Abstract: . . .  available services (e.g. if multiple sources of location information are available). In general, we envision having a set of rules, where, should everything else fail, the e- Wallet reverts to a low salience rule that invokes one or more semantic search engines and/or one or more public matchmaking services. Clearly, as users acquire new personal resources (e.g. a new calendar), they will have to register them with their e-Wallets (e.g. using predefined service profiles . . .
. . .  points on campus: <mc: AccessPoint > <mc:MAC>00:60:1D:23:C5:AF</mc:MAC> <mc: location rdf:resource=" http://www.cmu.edu/SmithHall " /> </mc:Entity> Result of invoking the location-tracking web service:  . . .
. . .  #colleague ") (subject ?person1 ) (object ?person2 ) ) ) ) Figure 13 Rule defining colleagues as members of the same team XS LT Page 26 Semantic Web Technologies to Reconcile Privacy and Context Awareness 26 8 Service layer processing As indicated earlier, needs for service triples can be satisfied by either migrating a matching core triple . . .
. . .  (subject ?person1 ) (object ?person2 ) ) ) ) Figure 13 Rule defining colleagues as members of the same team XS LT Page 26 Semantic Web Technologies to Reconcile Privacy and Context Awareness 26 8 Service layer processing As indicated earlier, needs for service triples can be satisfied by either migrating a matching core triple or by activating . . .
. . .  ?person1 ) (object ?person2 ) ) ) ) Figure 13 Rule defining colleagues as members of the same team XS LT Page 26 Semantic Web Technologies to Reconcile Privacy and Context Awareness 26 8 Service layer processing As indicated earlier, needs for service triples can be satisfied by either migrating a matching core triple or by activating a matching . . .
. . .  resources (e.g. a new calendar), they will have to register them with their e-Wallets (e.g. using predefined service profiles that are provided with the resource itself). Page 27 Fabien L. Gandon and Norman M. Sadeh 27 Annotation of access points on campus: <mc: AccessPoint > <mc:MAC>00:60:1D:23:C5:AF</mc:MAC> <mc: location rdf:resource=" http://www.cmu.edu/SmithHall " /> </mc:Entity> . . .
--3000,6,250,3222,64466