You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/en/functionalities.rst
+43-7Lines changed: 43 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,28 @@ Below are the functional and the User Experience requirements that the Wallet Pr
44
44
45
45
The Wallet Provider MUST allow the User to remove the PID issued during the activation phase. In addition, the PID Provider SHOULD allow the User to revoke the issued PID through a specific Touchpoint. The Wallet Provider MUST allow the User to always have the option to request the deactivation of their Wallet Instance, even in the absence of the device on which it was installed. For further details, please refer to the `Deactivation of the Wallet Instance`_ and `Management of Electronic Attestations`_ sections.
46
46
47
-
In case of errors using the Wallet Instance, the Wallet Provider MUST guarantee that the User receives consistent messages that inform them and guide them toward resolving the issue. For further details, please refer to the `Error Management`_ section.
47
+
In case of errors using the Wallet Instance, the Wallet Provider MUST guarantee that the User receives consistent messages that inform them and guide them toward resolving the issue. For further details, please refer to the :ref:`functionalities:Error Management` section.
48
+
49
+
Focus on PID – Person Identification Data
50
+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
51
+
52
+
The PID (Person Identification Data) refers to verified minimum set of informations about the User identity (see :ref:`credential-data-model:Digital Credential Data Model`) issued as a result of the activation process and made available in the Wallet Instance.
53
+
Below are the requirements for displaying and using the PID that each Wallet Provider MUST adhere to, in order to provide a consistent and accessible consultation and usage experience:
54
+
55
+
- The PID MUST be displayed correctly across all devices, ensuring a consistent experience on screens of varying sizes;
56
+
- The PID MUST be named as defined by the PID Provider;
57
+
- The PID MUST display its status if different from valid to provide transparency on its lifecycle and MAY display it if valid. Specific details about the PID status, if invalid, MAY be provided (e.g., the reason why the PID is revoked);
58
+
- The PID MUST include Action Buttons to enable lifecycle management and allow the User to revoke the PID, thus the entire Wallet Instance with all EAAs issued, or to update the PID at any time (see :ref:`functionalities:Management of Electronic Attestations`);
59
+
- The PID MUST be an interactive element, for the User to be authenticated by a Relying Party in a digital context (see :ref:`functionalities:Authentication`), to access services in proximity contexts, and to request the issuance of additional EAAs (see :ref:`functionalities:Issuance of Electronic Attestation of Attributes`);
60
+
- The PID MUST display a method of assistance by the PID Provider (see :ref:`functionalities:User Assistance`);
61
+
- The PID representation MUST adhere to a defined set of specifications provided by the PID Provider to ensure recognizability, consistency and homogeneity among different Wallet Solutions.
62
+
63
+
64
+
The PID Provider MUST:
65
+
66
+
- Implement a name/naming convention to refer to the PID, to guarantee consistency across all Wallet Solutions;
67
+
- Define a clear set of specifications for the PID to ensure consistent identification and representation of the PID across different Wallet Solutions, in terms of format, structure and appearance standards (e.g. name, color, background image, etc.).
68
+
48
69
49
70
Issuance of Electronic Attestations of Attributes
50
71
-------------------------------------------------
@@ -81,10 +102,25 @@ In case of errors using the Wallet Instance, the Wallet Provider MUST guarantee
81
102
82
103
If an Authentic Source (or an Electronic Attestation of Attributes Provider, should it coincide with the Authentic Source) intends to implement an Engagement Button to initiate the request process from their Touchpoint, they MUST ensure compliance with the graphical appearance and implementation requirements for the Engagement Button, as outlined in the :ref:`brand-identity:IT-Wallet System Brand Identity` section.
83
104
84
-
Layout of Electronic Attestations
85
-
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
86
105
87
-
The Electronic Attestations obtained within the Wallet Instance SHOULD be displayed in a list within a Preview View. In this case, the Electronic Attestations MUST ensure a high level of recognizability and accessibility [REF_ACCESSIBILITY] of the information contained. Below are the requirements for displaying the Electronic Attestation that each Wallet Provider MUST adhere to in order to provide a consistent and accessible consultation and usage experience:
106
+
Focus on Electronic Attestations of Attributes
107
+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
108
+
109
+
The EAAs obtained within the Wallet Instance SHOULD be displayed in a list within a Preview View. In this case, each EAA MUST ensure a high level of recognizability and accessibility [REF_ACCESSIBILITY] of the information contained. Below are the requirements for displaying the EAA that each Wallet Provider MUST adhere to in order to provide a consistent and accessible consultation and usage experience:
110
+
111
+
- The EAA MUST be displayed correctly across all devices, ensuring a consistent experience on screens of varying sizes;
112
+
- The name of the EAA MUST be clearly visible and always displayed in both the Detail View and the Preview View;
113
+
- The EAA, both in the Preview View and the Detailed View, MUST display its status if different from valid to provide transparency on its lifecycle and MAY display it if valid. The Preview View MAY also include additional Attributes to enhance the User Experience and management; for example, it MAY display the name or logo of the Electronic Attestation of Attributes Provider or the PID Provider. The Detailed View MAY provide specific details about the state if invalid (e.g., the reason why the EAA is revoked);
114
+
- The EAA MUST include Action Buttons in the Detail View to enable lifecycle management and allow the User to revoke or to update a EAA at any time (see :ref:`functionalities:Management of Electronic Attestations`);
115
+
- The EAA MUST be an interactive element, for the User to access services provided by Relying Parties in digital and proximity contexts (see :ref:`functionalities:Presentation of Electronic Attestation`);
116
+
- The EAA MAY be displayed in a card format in their Preview View, in line with approaches already used by other digital wallets in the market, to mirror the appearance of a corresponding physical document. When applicable, the digital nature of the document MAY be indicated, such as by labeling it as a "digital version" in the layout;
117
+
- The EAA MUST display the same information in the Detail View as shown in the Preview View and MAY include additional details;
118
+
- The EAA MUST display a method of assistance (see :ref:`functionalities:User Assistance`);
119
+
- The EAA layout in the Preview View MUST be optimized for scalability and usability, especially when multiple EAAs are displayed on the same screen;
120
+
- The EAA representation MUST adhere to a defined set of specifications provided by the Electronic Attestation of Attributes Provider to ensure recognizability, consistency and homogeneity among different Wallet Solutions.
121
+
122
+
123
+
The Electronic Attestation of Attributes Provider:
88
124
89
125
- The Electronic Attestation MUST be displayed correctly across all devices, ensuring a consistent experience on screens of varying sizes;
90
126
- The name of the Electronic Attestation MUST be clearly visible and always displayed in both the Detail View and the Preview View;
@@ -105,7 +141,7 @@ The presentation process allows the User to access a service or demonstrate owne
105
141
- **Remote Presentation**: the User presents the PID and/or EAA data through the Wallet Instance, to a Relying Party configured for online verification, for instance, to Authenticate and access the services offered.
106
142
107
143
Proximity Presentation
108
-
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
144
+
^^^^^^^^^^^^^^^^^^^^^^
109
145
110
146
Proximity presentation allows the User to present the PID and/or EAA data via their Wallet Instance, using one of two methods:
111
147
@@ -135,10 +171,10 @@ In case of errors using the Wallet Instance, the Wallet Provider MUST guarantee
135
171
- The User authorizes the operation using the unlock method previously set;
136
172
- The User receives confirmation of the successful presentation.
137
173
138
-
In case of errors using the Wallet Instance, the Wallet Provider MUST guarantee that the User receives consistent messages that inform them and guide them toward resolving the issue. For further details, please refer to the `Error Management`_ section.
174
+
In case of errors using the Wallet Instance, the Wallet Provider MUST guarantee that the User receives consistent messages that inform them and guide them toward resolving the issue. For further details, please refer to the :ref:`functionalities:Error Management` section.
139
175
140
176
Remote Presentation
141
-
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
177
+
^^^^^^^^^^^^^^^^^^^
142
178
143
179
Remote presentation allows the User to present the PID and/or EAA data by interacting with a Relying Party's Touchpoint through a designated Engagement Button.
0 commit comments