Changed TUI to UV

w3c · Apr 20, 2017 · f607343 · f607343
1 parent 9ba8f8a
commit f607343
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/images/fido-signature-formats-figure1.svg b/images/fido-signature-formats-figure1.svg
diff --git a/index.bs b/index.bs
@@ -1263,7 +1263,7 @@ The [=authenticator data=] structure is a byte array of 37 bytes or more, as fol
         <td>
             Flags (bit 0 is the least significant bit):
             - Bit 0: [=Test of User Presence=] (`TUP`) result.
-            - Bit 1: [=Test of User Identity=] (`TUI`) result. 
+            - Bit 1: [=User Verification=] (`UV`) result. 
             - Bits 1-5: Reserved for future use (`RFU`).
             - Bit 6: [=Attestation data=] included (`AT`). Indicates whether the authenticator added [=attestation data=].
             - Bit 7: Extension data included (`ED`). Indicates if the [=authenticator data=] has extensions.
@@ -1296,7 +1296,7 @@ by the authenticator during the [=authenticatorGetAssertion=] operation, by veri
 requested credential exactly matches the RP ID supplied by the client.
 
 The `TUP` flag SHALL be set if and only if the authenticator detected a user through an authenticator specific gesture. The 
-`TUI` flag SHALL be set if and only if the [=user verification=] process has been performed by the authenticator. The
+`UV` flag SHALL be set if and only if the [=user verification=] process has been performed by the authenticator. The
 `RFU` bits in the flags byte SHALL be set to zero.
 
 For attestation signatures, the authenticator MUST set the AT flag and include the [=attestation data=]. For authentication