Difference between revisions of "User Stipulation"
From MgmtWiki
(→Solutions) |
(→Context) |
||
| Line 5: | Line 5: | ||
==Context== | ==Context== | ||
There are at least two sources of [[User Stipulation]]: | There are at least two sources of [[User Stipulation]]: | ||
| − | #The user can create a statement to be send to the correspondent [[Web Site]] informing the site as to the expectations of the user | + | #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. [https://wiki.idesg.org/wiki/index.php/Do_Not_Track Do Not Track]) |
#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. | #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. | ||
Revision as of 17:39, 18 October 2018
Full Title or Meme
- A statement from a User as to the behavior that the user expects of a Web Site.
- A condition, requirement, or item specified in a legal instrument. [1]
Context
There are at least two sources of User Stipulation:
- 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)
- 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.
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.
References
- ↑ Merriam Webster, 3rd International Dictionary
