Presentation from a Wallet - Revision history

Tom: /* References */

2023-10-25T19:24:21Z

‎References

Tom: /* Other Material */

2022-11-13T20:54:10Z

‎Other Material

Tom: /* References */

2022-02-09T03:19:53Z

‎References

Tom: /* Requirements */

2022-02-09T01:23:54Z

‎Requirements

Tom: /* Requirements */

2022-02-09T01:23:33Z

‎Requirements

Tom: /* Requirements */

2022-02-09T01:22:33Z

‎Requirements

Tom: /* Requirements */

2022-02-09T01:18:04Z

‎Requirements

Tom: /* Requirements */

2022-02-09T01:16:35Z

‎Requirements

Tom: /* Actors */

2022-02-09T01:11:11Z

‎Actors

Tom: /* User Journey */

2022-02-09T01:05:35Z

‎User Journey

← Older revision		Revision as of 19:24, 25 October 2023
Line 70:		Line 70:
	[[Category: User Agent]]		[[Category: User Agent]]
	[[Category: Use Case]]		[[Category: Use Case]]
		+	[[Category: Attestation]]

← Older revision		Revision as of 20:54, 13 November 2022
Line 69:		Line 69:

	[[Category: User Agent]]		[[Category: User Agent]]
		+	[[Category: Use Case]]

← Older revision		Revision as of 03:19, 9 February 2022
Line 65:		Line 65:

	==References==		==References==
		+	===Other Material===
		+	* Generic information is available on the wiki page [[Presentation]].

	[[Category: User Agent]]		[[Category: User Agent]]

@@ Line 17: / Line 17: @@
 There were subsections to PEMC with my comments
-{|border="1" padding="2" width="799px"
+{|border="1" padding="2" width="999px"
 | Original || comments
 |-

@@ Line 28: / Line 28: @@
 |3) The intent to retain variable per data element should be displayed clearly to the user for increased transparency. ||. Again we must be able to shorten the request into something the user can understand.
 |-
-|4) The intent to retain variable should be supported by an up to date identity data privacy policy.  This identity specific data use policy should be accessible from within the mDL holder's Wallet.  The data use policy should offer simple explanations outlining why the relying party plans on storing the data and for how long.||
+|4) The intent to retain variable should be supported by an up to date identity data privacy policy.  This identity specific data use policy should be accessible from within the mDL holder's Wallet.  The data use policy should offer simple explanations outlining why the relying party plans on storing the data and for how long.|| This is desirable but we need some UX to test
 |}

@@ Line 20: / Line 20: @@
 | Original || comments
 |-
-| In order to foster adoption, it is essential that we create a trusted experience for all participants.  During presentment, this consists of elevating awareness around what data is being requested, by whom, whether the relying party intends on storing this data and if so, what are they planning on doing with the stored data.  The Wallet provider should incorporate these elements into their presentment UI in order to create a transparent presentment experience.
+| In order to foster adoption, it is essential that we create a trusted experience for all participants.  During presentment, this consists of elevating awareness around what data is being requested, by whom, whether the relying party intends on storing this data and if so, what are they planning on doing with the stored data.  The Wallet provider should incorporate these elements into their presentment UI in order to create a transparent presentment experience.|| It all must fit on one screen with the OK button at the bottom - if it takes more than one screen the button would not be visible until the user scrolled to the bottom
 |-
-|1) All data elements that are being requested by the relying party should be clearly outlined and visible
+|1) All data elements that are being requested by the relying party should be clearly outlined and visible ||. This places too much detail to the user in many cases. For those cases we need some way to abstract the data requirements into purposes
 |-
-|2) The mDL holder should be clearly aware of who is requesting the mDL information.  This should be done via displaying the name and icon for the relying party in the presentment sheet in a way that is clear and legible.
+|2) The mDL holder should be clearly aware of who is requesting the mDL information.  This should be done via displaying the name and icon for the relying party in the presentment sheet in a way that is clear and legible. || The logo is required, but might be a default logo provided by the software vendor
 |-
-|3) The intent to retain variable per data element should be displayed clearly to the user for increased transparency.
+|3) The intent to retain variable per data element should be displayed clearly to the user for increased transparency. ||. Again we must be able to shorten the request into something the user can understand.
 |-
-|4) The intent to retain variable should be supported by an up to date identity data privacy policy.  This identity specific data use policy should be accessible from within the mDL holder's Wallet.  The data use policy should offer simple explanations outlining why the relying party plans on storing the data and for how long.
+|4) The intent to retain variable should be supported by an up to date identity data privacy policy.  This identity specific data use policy should be accessible from within the mDL holder's Wallet.  The data use policy should offer simple explanations outlining why the relying party plans on storing the data and for how long.||
 |}

@@ Line 13: / Line 13: @@
 # The computing device, whether mobile phone or laptop, will need to provide secure storage and collect user inputs for transmission in the bundle to the RP.
 # The [[Relying Party]] aka the [[Verifier]] of the bundle sent by the [[Wallet]].
 ==Problems==

@@ Line 44: / Line 44: @@
 # If there are optional requirements the user can disable them.
 # The user clicks OK
-# The response returns to the verifier
+# The presentation response returns to the verifier
 # If the verifier is happy the user gains access