User Choice Pattern - Revision history

Tomjones: /* Usability Considerations */

2021-11-28T19:20:36Z

Usability Considerations

← Older revision		Revision as of 19:20, 28 November 2021
Line 91:		Line 91:
	Read the report of the IDEF experience committee on use case usability at [[UXC Use Case Mapping]]		Read the report of the IDEF experience committee on use case usability at [[UXC Use Case Mapping]]

	~~--[[User:Tomjones\|Tomjones]] ([[User talk:Tomjones\|talk]]) 19:17, 28 November 2021 (UTC)~~===The Paradox of Choice===		===The Paradox of Choice===
	* In his book ''The Paradox of Choice – Why More Is Less'' ISBN 0-06-000568-8 (2004-01-06) American psychologist Barry Schwartz makes the case that more choice may not be helpful in making a decision. The user should be given only sufficient choices that have interesting and different consequences, or he will become confused and may not be able to make any decision at all. See the [https://en.wikipedia.org/wiki/The_Paradox_of_Choice Wikipedia entry] for more discussion.		* In his book ''The Paradox of Choice – Why More Is Less'' ISBN 0-06-000568-8 (2004-01-06) American psychologist Barry Schwartz makes the case that more choice may not be helpful in making a decision. The user should be given only sufficient choices that have interesting and different consequences, or he will become confused and may not be able to make any decision at all. See the [https://en.wikipedia.org/wiki/The_Paradox_of_Choice Wikipedia entry] for more discussion.
	* In a [https://www.wired.com/story/dont-give-users-control-over-data/ Wired article] (2021-11-24) Sandra Metz points out that user control provided by megaliths like FaceBook make a mockery of choice. Until there is effective legal penalties from bad behavior the choice provided by users will be deliberately obscure and hard for the user to understand.<blockquote>Empowering consumers by giving them a say is a noble goal that certainly has a lot of appeal. Yet, in the current data ecosystem, control is far less of a right than it is a responsibility—one that most of us are not equipped to take on. Even if our brains were to magically catch up with the rapidly changing technology landscape, protecting and managing one’s personal data would still be a full-time job.</blockquote>		* In a [https://www.wired.com/story/dont-give-users-control-over-data/ Wired article] (2021-11-24) Sandra Metz points out that user control provided by megaliths like FaceBook make a mockery of choice. Until there is effective legal penalties from bad behavior the choice provided by users will be deliberately obscure and hard for the user to understand.<blockquote>Empowering consumers by giving them a say is a noble goal that certainly has a lot of appeal. Yet, in the current data ecosystem, control is far less of a right than it is a responsibility—one that most of us are not equipped to take on. Even if our brains were to magically catch up with the rapidly changing technology landscape, protecting and managing one’s personal data would still be a full-time job.</blockquote>

Tomjones: /* The Paradox of Choice */

2021-11-28T19:17:30Z

The Paradox of Choice

← Older revision		Revision as of 19:17, 28 November 2021
Line 91:		Line 91:
	Read the report of the IDEF experience committee on use case usability at [[UXC Use Case Mapping]]		Read the report of the IDEF experience committee on use case usability at [[UXC Use Case Mapping]]

	===The Paradox of Choice===		--[[User:Tomjones\|Tomjones]] ([[User talk:Tomjones\|talk]]) 19:17, 28 November 2021 (UTC)===The Paradox of Choice===
	* In his book ''The Paradox of Choice – Why More Is Less'' ISBN 0-06-000568-8 (2004-01-06) American psychologist Barry Schwartz makes the case that more choice may not be helpful in making a decision. The user should be given only sufficient choices that have interesting and different consequences, or he will become confused and may not be able to make any decision at all. See the [https://en.wikipedia.org/wiki/The_Paradox_of_Choice Wikipedia entry] for more discussion.		* In his book ''The Paradox of Choice – Why More Is Less'' ISBN 0-06-000568-8 (2004-01-06) American psychologist Barry Schwartz makes the case that more choice may not be helpful in making a decision. The user should be given only sufficient choices that have interesting and different consequences, or he will become confused and may not be able to make any decision at all. See the [https://en.wikipedia.org/wiki/The_Paradox_of_Choice Wikipedia entry] for more discussion.
	* In a [https://www.wired.com/story/dont-give-users-control-over-data/ Wired article] (2021-11-24) Sandra Metz points out that user control provided by megaliths like FaceBook make a mockery of choice. Until there is effective legal penalties from bad behavior the choice provided by users will be deliberately obscure and hard for the user to understand.		* In a [https://www.wired.com/story/dont-give-users-control-over-data/ Wired article] (2021-11-24) Sandra Metz points out that user control provided by megaliths like FaceBook make a mockery of choice. Until there is effective legal penalties from bad behavior the choice provided by users will be deliberately obscure and hard for the user to understand.<blockquote>Empowering consumers by giving them a say is a noble goal that certainly has a lot of appeal. Yet, in the current data ecosystem, control is far less of a right than it is a responsibility—one that most of us are not equipped to take on. Even if our brains were to magically catch up with the rapidly changing technology landscape, protecting and managing one’s personal data would still be a full-time job.</blockquote>

	===Value Proposition===		===Value Proposition===

Tomjones: /* The Paradox of Choice */

2021-11-28T19:06:40Z

The Paradox of Choice

← Older revision		Revision as of 19:06, 28 November 2021
Line 93:		Line 93:
	===The Paradox of Choice===		===The Paradox of Choice===
	* In his book ''The Paradox of Choice – Why More Is Less'' ISBN 0-06-000568-8 (2004-01-06) American psychologist Barry Schwartz makes the case that more choice may not be helpful in making a decision. The user should be given only sufficient choices that have interesting and different consequences, or he will become confused and may not be able to make any decision at all. See the [https://en.wikipedia.org/wiki/The_Paradox_of_Choice Wikipedia entry] for more discussion.		* In his book ''The Paradox of Choice – Why More Is Less'' ISBN 0-06-000568-8 (2004-01-06) American psychologist Barry Schwartz makes the case that more choice may not be helpful in making a decision. The user should be given only sufficient choices that have interesting and different consequences, or he will become confused and may not be able to make any decision at all. See the [https://en.wikipedia.org/wiki/The_Paradox_of_Choice Wikipedia entry] for more discussion.
	* In a [https://www.wired.com/story/dont-give-users-control-over-data/ Wired article] (2-~~21=~~11=24) ~~Santra~~ Metz points out that user control provided by megaliths like FaceBook make a mockery of choice. Until there is effective legal penalties from bad behavior the choice provided by users will be deliberately obscure and hard for the user to understand.		* In a [https://www.wired.com/story/dont-give-users-control-over-data/ Wired article] (2021-11-24) Sandra Metz points out that user control provided by megaliths like FaceBook make a mockery of choice. Until there is effective legal penalties from bad behavior the choice provided by users will be deliberately obscure and hard for the user to understand.

	===Value Proposition===		===Value Proposition===

Tomjones: /* The Paradox of Choice */

2021-11-28T19:05:24Z

The Paradox of Choice

← Older revision		Revision as of 19:05, 28 November 2021
Line 93:		Line 93:
	===The Paradox of Choice===		===The Paradox of Choice===
	* In his book ''The Paradox of Choice – Why More Is Less'' ISBN 0-06-000568-8 (2004-01-06) American psychologist Barry Schwartz makes the case that more choice may not be helpful in making a decision. The user should be given only sufficient choices that have interesting and different consequences, or he will become confused and may not be able to make any decision at all. See the [https://en.wikipedia.org/wiki/The_Paradox_of_Choice Wikipedia entry] for more discussion.		* In his book ''The Paradox of Choice – Why More Is Less'' ISBN 0-06-000568-8 (2004-01-06) American psychologist Barry Schwartz makes the case that more choice may not be helpful in making a decision. The user should be given only sufficient choices that have interesting and different consequences, or he will become confused and may not be able to make any decision at all. See the [https://en.wikipedia.org/wiki/The_Paradox_of_Choice Wikipedia entry] for more discussion.
	* In a ~~Wired article<ref>~~https://www.wired.com/story/dont-give-users-control-over-data/~~</ref>~~		* In a [https://www.wired.com/story/dont-give-users-control-over-data/ Wired article] (2-21=11=24) Santra Metz points out that user control provided by megaliths like FaceBook make a mockery of choice. Until there is effective legal penalties from bad behavior the choice provided by users will be deliberately obscure and hard for the user to understand.

	===Value Proposition===		===Value Proposition===

Tomjones: /* The Paradox of Choice */

2021-11-28T18:47:59Z

The Paradox of Choice

← Older revision		Revision as of 18:47, 28 November 2021
Line 92:		Line 92:

	===The Paradox of Choice===		===The Paradox of Choice===
	In his book ''The Paradox of Choice – Why More Is Less'' ISBN 0-06-000568-8 (2004-01-06) American psychologist Barry Schwartz makes the case that more choice may not be helpful in making a decision. The user should be given only sufficient choices that have interesting and different consequences, or he will become confused and may not be able to make any decision at all. See the [https://en.wikipedia.org/wiki/The_Paradox_of_Choice Wikipedia entry] for more discussion.		* In his book ''The Paradox of Choice – Why More Is Less'' ISBN 0-06-000568-8 (2004-01-06) American psychologist Barry Schwartz makes the case that more choice may not be helpful in making a decision. The user should be given only sufficient choices that have interesting and different consequences, or he will become confused and may not be able to make any decision at all. See the [https://en.wikipedia.org/wiki/The_Paradox_of_Choice Wikipedia entry] for more discussion.
			* In a Wired article<ref>https://www.wired.com/story/dont-give-users-control-over-data/</ref>

	===Value Proposition===		===Value Proposition===

Tomjones: /* Status */

2021-11-28T18:40:33Z

Status

← Older revision		Revision as of 18:40, 28 November 2021
Line 3:		Line 3:
	In some ways this is similar to the existing use case that discusses privacy enhancing technology, but the purpose of the pattern is limited to the attributes requested by the RP and the corresponding user experience. Note that a PET provider can be inserted between the RP and the user agent that renders the user experience.		In some ways this is similar to the existing use case that discusses privacy enhancing technology, but the purpose of the pattern is limited to the attributes requested by the RP and the corresponding user experience. Note that a PET provider can be inserted between the RP and the user agent that renders the user experience.

	~~==Status==~~
	===Design Pattern Lifecycle Status===		===Design Pattern Lifecycle Status===
	{\| border="1" padding="2" width="600px"		{\| border="1" padding="2" width="600px"

Tomjones at 18:39, 28 November 2021

2021-11-28T18:39:45Z

← Older revision		Revision as of 18:39, 28 November 2021
Line 10:		Line 10:
	\|colspan=6\|This Design Pattern is available for review by the User Experice Committee (UXC) with the goal of refining and completing the Design Pattern, , see [[Identity Design Patterns]] for the current list of design patterns and their status.		\|colspan=6\|This Design Pattern is available for review by the User Experice Committee (UXC) with the goal of refining and completing the Design Pattern, , see [[Identity Design Patterns]] for the current list of design patterns and their status.
	\|}		\|}

	~~===Design Pattern Review Status===~~
	~~Initial posting.~~

	===Design Pattern Category===		===Design Pattern Category===
Line 20:		Line 17:
	Tom Jones		Tom Jones

	= Design Pattern Content =		== Design Pattern Content ==
	The User Choice Design Pattern is meant as a composable object that can be included in any IDESG conformant entity.		The User Choice Design Pattern is meant as a composable object that can be included in any IDESG conformant entity.
	==Problem Description (meme)==		==Problem Description (meme)==
	User releases only that information to Relying Parties that they wish for purposes that they understand at the time of release. This choice is conveyed in an interchange with an IDESG compliant entity via an object with entries chosen from a '''Taxonomy of Requested Attributes'''. User choices can be cached to avoid cognitive overload.		User releases only that information to Relying Parties that they wish for purposes that they understand at the time of release. This choice is conveyed in an interchange with an IDESG compliant entity via an object with entries chosen from a '''Taxonomy of Requested Attributes'''. User choices can be cached to avoid cognitive overload.

	==When to use this Pattern (Context)==		===When to use this Pattern (Context)===
	* Any time a user is asked to provide any personal information. Personal information includes patterns of behavior that could be used narrow the population that contains the user, such as search terms.		* Any time a user is asked to provide any personal information. Personal information includes patterns of behavior that could be used narrow the population that contains the user, such as search terms.
	* The user device consideration is that the device has a display at least 400 x 800 pixels with a live connection to the internet.		* The user device consideration is that the device has a display at least 400 x 800 pixels with a live connection to the internet.

Tomjones: /* Taxonomy of an Attribute Request */

2020-01-09T16:50:31Z

Taxonomy of an Attribute Request

← Older revision		Revision as of 16:50, 9 January 2020
Line 64:		Line 64:

	===Taxonomy of an Attribute Request===		===Taxonomy of an Attribute Request===
	It is important that the RP have a taxonomy of requested fields that can be presented to the user within the scope of a single device page. That implies that the taxonomy of requested fields needs to be limited to those items that the user can sensibly be expected to comprehend. It is expected that the language used will support name/value pairs with other attributes such as whether the attribute is mandatory. It is not likely that any list will be complete, the RP can always ask for other information, but this list is intended to be what is released by the user agent in claims. Permissions for release of this information to one RP is likely to be sticky; that is to be released on demand to the same RP, typically for a limited period.		It is important that the RP have a taxonomy of requested fields that can be presented to the user within the scope of a single device page. That implies that the taxonomy of requested fields needs to be limited to those items that the user can sensibly be expected to comprehend. It is expected that the language used will support name/value pairs with other attributes such as whether the attribute is mandatory. It is not likely that any list will be complete, the RP can always ask for other information, but this list is intended to be what is released by the user agent in claims. Permissions for release of this information to one RP is likely to be sticky; that is to be released on demand to the same RP, typically for a limited period. (See wiki page on [[Information Sharing Agreement]].)
	# Identifier of the RP must be supplied to the user agent in a secure message, such as an EV certificate. This is needed, not only to be sure that the user is sure who is getting the information, but also to allows the future release of the same information to the same RP.		# Identifier of the RP must be supplied to the user agent in a secure message, such as an EV certificate. This is needed, not only to be sure that the user is sure who is getting the information, but also to allows the future release of the same information to the same RP.
	# There is always a tendency for each relying party to determine that their requirement for information is unique and therefore they cannot use a predetermined set of user attributes. This tendency is destructive of user comprehension. The only way to assure that users will understand the options display is to make the basic set of options common for all users. Then a few extension on a web site will at least be in the context of the choice already known and understood by the user.		# There is always a tendency for each relying party to determine that their requirement for information is unique and therefore they cannot use a predetermined set of user attributes. This tendency is destructive of user comprehension. The only way to assure that users will understand the options display is to make the basic set of options common for all users. Then a few extension on a web site will at least be in the context of the choice already known and understood by the user.

Tomjones: /* Health Care */

2019-10-22T00:20:07Z

Health Care

← Older revision		Revision as of 00:20, 22 October 2019
Line 124:		Line 124:
	*[[Patient Registration with Distributed Attributes]] discusses the initial establishment of a medical relationship between a patient an a health care provider.		*[[Patient Registration with Distributed Attributes]] discusses the initial establishment of a medical relationship between a patient an a health care provider.
	*[[Patient with Lab and Referral Use Case]] discusses subsequent visits with referral to outside providers.		*[[Patient with Lab and Referral Use Case]] discusses subsequent visits with referral to outside providers.
			*[[Patient Choice]] wiki page deals with other issues of choice, such as selecting identifiers and access methods or applications.

	[[Category:User Experience]]		[[Category:User Experience]]
	[[Category:Design Pattern]]		[[Category:Design Pattern]]
	[[Category:Profile]]		[[Category:Profile]]
	[[Category:Authentication Design Pattern]]		[[Category:Authentication Design Pattern]]

Tomjones: /* When to use this Pattern (Context) */

2019-05-25T17:50:28Z

When to use this Pattern (Context)

← Older revision		Revision as of 17:50, 25 May 2019
Line 29:		Line 29:
	* The user device consideration is that the device has a display at least 400 x 800 pixels with a live connection to the internet.		* The user device consideration is that the device has a display at least 400 x 800 pixels with a live connection to the internet.
	* The IDESG will create an identity ecosystem consisting of multiple trust frameworks that satisfy the needs of specific affinity groups. Since users need to communicate with different affinity groups from time to time, they will typically need to accommodate different trust frameworks during the normal course of daily computer use. Each framework can optionally specify a '''Taxonomy of Requested Attributes''' and a default policy when they differ from the IDEF base policy.		* The IDESG will create an identity ecosystem consisting of multiple trust frameworks that satisfy the needs of specific affinity groups. Since users need to communicate with different affinity groups from time to time, they will typically need to accommodate different trust frameworks during the normal course of daily computer use. Each framework can optionally specify a '''Taxonomy of Requested Attributes''' and a default policy when they differ from the IDEF base policy.
	* The RP has a relatively clear set of privacy compliance regulations to follow that can be satisfied by one or more ~~IDF~~ trust frameworks.		* The RP has a relatively clear set of privacy compliance regulations to follow that can be satisfied by one or more IDEF trust frameworks.
	* The RP will support one or more IDEF trust frameworks or providers known to follow IDEF principles for the user to chose from.		* The RP will support one or more IDEF trust frameworks or providers known to follow IDEF principles for the user to chose from.
	* It is expected that each trust framework will come with a set of rules and approved independent labs that can attest to the web site based on the trust frameworks that are supported by the site.		* It is expected that each trust framework will come with a set of rules and approved independent labs that can attest to the web site based on the trust frameworks that are supported by the site.