User Stipulation

Full Title or Meme

1. A statement from a User as to the behavior that the user expects of a Web Site.
2. A condition, requirement, or item specified in a legal instrument.

Context

There are at least two sources of User Stipulation:

1. The user can create a statement to be send to the correspondent Web Site informing the site as to the expectations of the user. (aka intent casting e.g. Do Not Track)
2. The Web Site can provide the user with some sort of document (terms of use, privacy policy, etc.) that the user can accept or reject.

This page does not presently include user settings on a User Device.

Problems

Compliance by the Web Site with the agreed terms will be hard to track.

Solutions

• The page Cookies has some description of user cookies that have been proposed as a source of user stipulations.
• The Best Practice shows one way to track user expressed intent within a Relying Party database.

Intent Casting

This solution covers the projection of user terms onto a correspondent Web Site.

• An existing example is the DNT (Do Not Track) HTTP header.
• The following example assumes a richer format for intent casting that is not yet defined.
  • See the page on stalking on Kantara.

Here are the potential terms to be cast

Name	OIDC	Priv Risk	Notes
openid	yes	0	requests access to the user_id (sub) Claim which is here assumed to be pair-wise unique for the privacy score.
profile	yes	4	requests that access to the End-User’s profile Claims excluding the address and email Claims.
email	yes	4	requests that access to the email and verified Claims } References