Wallet Notices - Revision history

Tom: /* Goals */

2024-02-05T17:18:44Z

‎Goals

Tom: /* Solutions */

2024-02-05T05:26:29Z

‎Solutions

Tom: /* Goals */

2024-02-05T05:21:32Z

‎Goals

Tom: /* Problems */

2024-02-05T02:12:40Z

‎Problems

Tom: /* Problems */

2024-02-05T02:11:54Z

‎Problems

Tom: /* Problems */

2024-02-05T02:10:24Z

‎Problems

Tom: /* Context */

2024-02-05T02:06:35Z

‎Context

Tom: /* Solutions */

2024-02-05T02:05:30Z

‎Solutions

Tom: /* Solutions */

2024-02-05T02:02:05Z

‎Solutions

Tom: /* Solutions */

2024-02-05T01:59:21Z

‎Solutions

@@ Line 9: / Line 9: @@
 * Some sort of user gesture is to be required by the Wallet before any data about the user or wallet is authorized to be sent to the [[Verifier]].
 * Once user data has been release to the [[Verifier]] it is responsible for notifications of any release of user data not approved by the user.
-* When possible these breach or terms updates will be stored by the wallet along with the requests that the user has accepted.
+* When possible these breaches and any terms updates will be stored by the wallet along with [[Verifier]] requests that the user has accepted.
-* The user will be able to view these notifications for as long is the user has asked the wallet to retain them.
+* The user will be able to view these notifications for as long as the user has told the wallet to retain them.
 ==Context==

@@ Line 29: / Line 29: @@
 ==Solutions==
-* The initial message from the [[Verifier]] to the user must contain:
+* The initial message from the [[Verifier]] to the user must contain: (Note the modifier "initial" as this does not apply to later connections.)
 # An identification of the [[Verifier]] that can be presented to the user in terms that they can understand.
 # A Privacy Transparency Statement that can be presented to the user as a part of a request to which the user must positively indicate acceptance.

@@ Line 7: / Line 7: @@
 * Notices from the [[Verifier]] identify it and the verified data it needs for the purpose of providing access to some resource.
 * The display of the Verifier notification will be created by the [[Wallet]] based on user settings.
-* Some sort of user gesture is to be required by the Wallet before any data about the user or wallet is sent to the [[Verifier]].
+* Some sort of user gesture is to be required by the Wallet before any data about the user or wallet is authorized to be sent to the [[Verifier]].
 * Once user data has been release to the [[Verifier]] it is responsible for notifications of any release of user data not approved by the user.
 * When possible these breach or terms updates will be stored by the wallet along with the requests that the user has accepted.

@@ Line 21: / Line 21: @@
 ==Problems==
 * User fatigue sets in on excessive notice displays. This fatigue is different for different users and so display thresholds need to be under user control.
-* [[Smartphone]]s typically have one overall notification setting per app. The wallet notification setting should be on, but many users may not chose to enable it.
+* [[Smartphone]]s typically have one overall notification setting per app. The wallet notification setting should be on, but many users may not choose to enable it.
 ** The wallet may require notifications before they start operations, but product marketing staff are likely to object to that requirement.
 ** Smartphones provide detailed settings under notifications (Banners, Sounds, Badges, etc.), but they are very seldom part of the user's attention.

@@ Line 21: / Line 21: @@
 ==Problems==
 * User fatigue sets in on excessive notice displays. This fatigue is different for different users and so display thresholds need to be under user control.
-* [[Smartphone]]s typically have one overall notification setting per app. The wallet notification setting should be on, but many user may not chose to enable it.
+* [[Smartphone]]s typically have one overall notification setting per app. The wallet notification setting should be on, but many users may not chose to enable it.
 ** The wallet may require notifications before they start operations, but product marketing staff are likely to object to that requirement.
 ** Smartphones provide detailed settings under notifications (Banners, Sounds, Badges, etc.), but they are very seldom part of the user's attention.

@@ Line 24: / Line 24: @@
 ** The wallet may require notifications before they start operations, but product marketing staff are likely to object to that requirement.
 ** Smartphones provide detailed settings under notifications (Banners, Sounds, Badges, etc.), but they are very seldom part of the user's attention.
-* Some wallet devices can be tracked by the radio signals that are released as a part of establish a connecting to the wallet.
+* Some wallet devices can be tracked by the radio signals that are released as a part of establishing a connection to the wallet.
 * At the time that the [[Verifier]] creates the request and provides their own [[Identifier]] and privacy transparency statement, the [[Identifier]] of the Holder is not known. The [[Verifier]] probably records the endpoint network address of the [[Entity]] that contacted them, but that could just be the address of a VPN endpoint.
 * Most statements of terms and conditions are too long for display on a single wallet screen to the user, but still must be available in some form that persists in the wallet and can be examined by the user whenever they wish to view them.

@@ Line 13: / Line 13: @@
 ==Context==
-* The term user here applies to wallets holders and [[Subject]]s when they are different from the holder.
+* The term "user" here applies to wallets holders and [[Subject]]s when they are different from the holder.
 * Typically only the holder (owner) of the wallet receives and stores notices.
 * This document considers only the role of the [[Verifier]] as it is assumed that the issuer or any other party first needs to verify the wallet and holder of the wallet before exchanging any certificate data.
 * Government legislation that mandates the release of information on different terms than these is not in the scope of this page.
 * A Privacy Transparency Statement will be included in (or prior to) any request for [[Subject]] information.
 ==Problems==
 * User fatigue sets in on excessive notice displays. This fatigue is different for different users and so display thresholds need to be under user control.

@@ Line 31: / Line 31: @@
 # An identification of the [[Verifier]] that can be presented to the user in terms that they can understand.
 # A Privacy Transparency Statement that can be presented to the user as a part of a request to which the user must positively indicate acceptance.
-## The purpose(s) fro which the user credential and other data is required. This must be something the user sees and understands.
+## The purpose(s) for which the user credential and other data is required. This must be something the user sees and understands.
 ## If the purpose is not sufficient the wallet can present detailed data requests so long as they are covered by the purpose.
 ## Optionally the verifier can ask for data this is not required, but this requires opt-in by the user.

@@ Line 34: / Line 34: @@
 ## If the purpose is not sufficient the wallet can present detailed data requests so long as they are covered by the purpose.
 ## Optionally the verifier can ask for data this is not required, but this requires opt-in by the user.
-## Some indication as the to retention period for data if it is stored by the [[Verifier]] beyond the verification process itself.
+## Some indication as to the retention period for data if it is stored by the [[Verifier]] beyond the verification process itself.
 ## Whenever data is stored, some contact information must be supplied for the user to determine what data is stored or request deletion of the data.
 ## The jurisdiction under which the data retention is controlled. (Whether this is part of trust registry is tbd.)

@@ Line 36: / Line 36: @@
 ## Some indication as the to retention period for data if it is stored by the [[Verifier]] beyond the verification process itself.
 ## Whenever data is stored, some contact information must be supplied for the user to determine what data is stored or request deletion of the data.
 * On any extended relationship between the verifier and holder, changes to future transaction terms and conditions must create a new consent request.
 * Breach notifications are likely to be covered by local government regulations. Where possible these should be as notifications to the wallet.