URL by invoking "load-label"
twice, once for each rating service; "load-label"
adds statements to the statement-list. We then search the returned
statements for labels using two rating services, E-Trust and w3.org's
privacy service.
Each pattern-match uses criteria specific to one rating service,
and then the results of those two pattern-matches are combined
using and. Thus, in order for the policy to be satisfied,
there must be labels in both rating services.
In the previous sample policies, the requested document was downloaded and scanned for embedded labels, which would be used to decide whether or not to display the document. In a privacy application, what is at stake is our private information that could be passed to the remote host, including the fact that we accessed the site at all. For this reason, the user here has decided not to scan the document for labels (which would involve connecting to the remote site), but only to request labels separately from the document (from the bureau "http://labels.com," which the user trusts for this purpose). Using this policy, we won't even connect to the originally-requested remote site unless we've first decided that it is safe.