Attribute Vector - Revision history

Tomjones: /* Preconditions */

2019-04-27T21:49:20Z

Preconditions

← Older revision		Revision as of 21:49, 27 April 2019
Line 3:		Line 3:

	==Preconditions==		==Preconditions==
	* The primary use case for the [[Attribute Vector]] is a user navigating to the web site of a [[Relying Party]] where they need be able establish a level of trust by the [[Relying Party]] to meet ~~their~~ need for assurance about the user's ability to be trusted with their goods or services while maintaining the user's expectations of privacy. As such it is expected that user stipulations will be included as well as [[User Private Information]].		* The primary use case for the [[Attribute Vector]] is a user navigating to the web site of a [[Relying Party]] where they need be able establish a level of trust by the [[Relying Party]] to meet its need for assurance about the user's ability to be trusted with their goods or services while maintaining the user's expectations of privacy. As such it is expected that user stipulations will be included as well as [[User Private Information]].
	* Both the user and the [[Relying Party]] have the capability to create and understand the vector and its release of [[Attribute]]s to the [[Relying Party]].		* Both the user and the [[Relying Party]] have the capability to create and understand the vector and its release of [[Attribute]]s to the [[Relying Party]].

Tomjones: /* Preconditions */

2019-04-27T21:48:37Z

Preconditions

← Older revision		Revision as of 21:48, 27 April 2019
Line 3:		Line 3:

	==Preconditions==		==Preconditions==
	* The primary use case for the [[Attribute Vector]] is a user navigating to the web site of a [[Relying Party] where they need be able establish a level of trust by the [[Relying Party]] to meet their need for assurance about the user's ability to be trusted with their goods or services while maintaining the user's expectations of privacy. As such it is expected that user stipulations will be included as well as [[User Private Information]].		* The primary use case for the [[Attribute Vector]] is a user navigating to the web site of a [[Relying Party]] where they need be able establish a level of trust by the [[Relying Party]] to meet their need for assurance about the user's ability to be trusted with their goods or services while maintaining the user's expectations of privacy. As such it is expected that user stipulations will be included as well as [[User Private Information]].
	* Both the user and the [[Relying Party]] have the capability to create and understand the vector and its release of [[Attribute]]s to the [[Relying Party]].		* Both the user and the [[Relying Party]] have the capability to create and understand the vector and its release of [[Attribute]]s to the [[Relying Party]].

Tomjones: /* Preconditions */

2019-04-27T21:47:42Z

Preconditions

← Older revision		Revision as of 21:47, 27 April 2019
Line 3:		Line 3:

	==Preconditions==		==Preconditions==
	* The primary use case for the [[Attribute Vector]] is a user navigating to the web site where they need be able establish a level of trust by the [[Relying Party]] to meet their need for assurance about the user's ability to be trusted with their goods or services while maintaining the user's expectations of privacy. As such it is expected that user stipulations will be included as well as [[User Private Information]].		* The primary use case for the [[Attribute Vector]] is a user navigating to the web site of a [[Relying Party] where they need be able establish a level of trust by the [[Relying Party]] to meet their need for assurance about the user's ability to be trusted with their goods or services while maintaining the user's expectations of privacy. As such it is expected that user stipulations will be included as well as [[User Private Information]].
	* Both the user and the [[Relying Party]] have the capability to create and understand the vector and its release of [[Attribute]]s to the [[Relying Party]].		* Both the user and the [[Relying Party]] have the capability to create and understand the vector and its release of [[Attribute]]s to the [[Relying Party]].

Tomjones: /* Full Title or Meme */

2019-04-27T21:46:53Z

Full Title or Meme

← Older revision		Revision as of 21:46, 27 April 2019
Line 1:		Line 1:
	==Full Title or Meme==		==Full Title or Meme==
	A list of [[Attribute]]s about an individual that is presented to provider of goods or services (the [[Relying Party]]) to establish to ability of the user to successfully complete a transaction with the provider.		A list of [[Attribute]]s about an individual that is presented to a provider of goods or services (the [[Relying Party]]) to establish to ability of the user to successfully complete a transaction with the provider.

	==Preconditions==		==Preconditions==

Tomjones: /* Solutions */

2019-04-27T21:44:15Z

Solutions

← Older revision		Revision as of 21:44, 27 April 2019
Line 13:		Line 13:
	# To be fully compliant with the various [[Privacy]] legislation like the [[GDPR]] or the California legislation the [[Relying Party]] may first require that the user establish a channel back to the user for the performance of required [[Redress]] and [[Recovery]] operations.		# To be fully compliant with the various [[Privacy]] legislation like the [[GDPR]] or the California legislation the [[Relying Party]] may first require that the user establish a channel back to the user for the performance of required [[Redress]] and [[Recovery]] operations.
	# Only then should the [[Relying Party]] be in a position to request additional [[Attribute]]s from the [[User]].		# Only then should the [[Relying Party]] be in a position to request additional [[Attribute]]s from the [[User]].
	# Once the [[Relying Party]] has possession of the [[Attribute Vector]] it can apply its own risk profile to the vector to determine if the user meets the ~~sites~~ policy for granting trust to users on the site.		# Once the [[Relying Party]] has possession of the [[Attribute Vector]] it can apply its own risk profile to the vector to determine if the user meets the site's policy for granting trust to users on the site.

	==References==		==References==

Tomjones: /* Problems */

2019-04-27T21:43:21Z

Problems

← Older revision		Revision as of 21:43, 27 April 2019
Line 7:		Line 7:

	==Problems==		==Problems==
	* Today the user is prompted for [[User Information]] by the web site it whatever form that site wishes. There is no real understanding by the user of what all will be requested or what conditions the user may be able to place on the release of information to the site.		* Today the user is prompted for [[User Private Information]] by the web site it whatever form that site wishes. There is no real understanding by the user of what all will be requested or what conditions the user may be able to place on the release of information to the site.

	==Solutions==		==Solutions==

Tomjones at 21:42, 27 April 2019

2019-04-27T21:42:27Z

← Older revision		Revision as of 21:42, 27 April 2019
Line 1:		Line 1:
	==Full Title or Meme==		==Full Title or Meme==
	A list of [[Attribute]]s about an individual that is presented to provider of goods or services to establish to ability of the user to successfully complete a transaction with the provider.		A list of [[Attribute]]s about an individual that is presented to provider of goods or services (the [[Relying Party]]) to establish to ability of the user to successfully complete a transaction with the provider.

	==Preconditions==		==Preconditions==
	* The primary use case for the [[Attribute Vector]] is a user navigating to the web site where they need be able establish a level of trust by the [[Relying Party]] to meet their need for assurance about the user's ability to be trusted with their goods or services while maintaining the user's expectations of privacy. As such it is expected that user stipulations will be included as well as [[User Private Information]].		* The primary use case for the [[Attribute Vector]] is a user navigating to the web site where they need be able establish a level of trust by the [[Relying Party]] to meet their need for assurance about the user's ability to be trusted with their goods or services while maintaining the user's expectations of privacy. As such it is expected that user stipulations will be included as well as [[User Private Information]].
	* Both the user and the [[~~Web Site~~]] have the capability to create and understand the vector and its release of [[Attribute]]s to the [[Relying Party]].		* Both the user and the [[Relying Party]] have the capability to create and understand the vector and its release of [[Attribute]]s to the [[Relying Party]].

	==Problems==		==Problems==

Tomjones at 21:41, 27 April 2019

2019-04-27T21:41:31Z

← Older revision		Revision as of 21:41, 27 April 2019
Line 3:		Line 3:

	==Preconditions==		==Preconditions==
	* The primary use case for the [[Attribute Vector]] is a user navigating to the web site where they need be able establish a level of trust by the [[~~Web Site~~]] to meet their need for assurance about the user's ability to be trusted with their goods or services while maintaining the user's expectations of privacy. As such it is expected that user stipulations will be included as well as [[User Private Information]].		* The primary use case for the [[Attribute Vector]] is a user navigating to the web site where they need be able establish a level of trust by the [[Relying Party]] to meet their need for assurance about the user's ability to be trusted with their goods or services while maintaining the user's expectations of privacy. As such it is expected that user stipulations will be included as well as [[User Private Information]].
	* Both the user and the [[Web Site]] have the capability to create and understand the vector and its release of [[Attribute]]s to the [[~~Web Site~~]].		* Both the user and the [[Web Site]] have the capability to create and understand the vector and its release of [[Attribute]]s to the [[Relying Party]].

	==Problems==		==Problems==

Tomjones: /* Solutions */

2019-04-27T21:40:34Z

Solutions

← Older revision		Revision as of 21:40, 27 April 2019
Line 13:		Line 13:
	# To be fully compliant with the various [[Privacy]] legislation like the [[GDPR]] or the California legislation the [[Relying Party]] may first require that the user establish a channel back to the user for the performance of required [[Redress]] and [[Recovery]] operations.		# To be fully compliant with the various [[Privacy]] legislation like the [[GDPR]] or the California legislation the [[Relying Party]] may first require that the user establish a channel back to the user for the performance of required [[Redress]] and [[Recovery]] operations.
	# Only then should the [[Relying Party]] be in a position to request additional [[Attribute]]s from the [[User]].		# Only then should the [[Relying Party]] be in a position to request additional [[Attribute]]s from the [[User]].
			# Once the [[Relying Party]] has possession of the [[Attribute Vector]] it can apply its own risk profile to the vector to determine if the user meets the sites policy for granting trust to users on the site.

	==References==		==References==

Tomjones: /* Problems */

2019-04-27T21:38:30Z

Problems

← Older revision		Revision as of 21:38, 27 April 2019
Line 7:		Line 7:

	==Problems==		==Problems==
	* ~~Best method~~ for ~~establishing trust with a web site today in the~~ [[~~EV Cert~~]] ~~which~~ is ~~designed~~ to ~~bind~~ the ~~web~~ site ~~to a real world entity~~.		* Today the user is prompted for [[User Information]] by the web site it whatever form that site wishes. There is no real understanding by the user of what all will be requested or what conditions the user may be able to place on the release of information to the site.

	==Solutions==		==Solutions==