Editorial
authorIan Jacobs <ij@w3.org>
Tue, 31 Mar 2015 14:29:46 -0500
changeset 675 74d731e2c58c
parent 674 44ae6e19e237
child 676 c7b3770cadea
Editorial

Through 6.2
latest/use-cases/index.html
--- a/latest/use-cases/index.html	Tue Mar 31 14:20:51 2015 -0500
+++ b/latest/use-cases/index.html	Tue Mar 31 14:29:46 2015 -0500
@@ -1448,7 +1448,7 @@
 
         <dl class="dl-horizontal">
           <dt>Payer Privacy</dt>
-          <dd>
+          <dd>We anticipate a range of privacy scenarios:
             <ul>
               <li>
 Lucio sends information about instruments he is willing to use to
@@ -1493,7 +1493,7 @@
 
         <dl class="dl-horizontal">
           <dt>Multi-Factor</dt>
-          <dd>
+          <dd>We anticipate a range of authentication scenarios, leveraging a wide variety of approaches and device capabilities:
             <ul>
               <li>
 When Ian selects his debit card, he is prompted for a PIN.
@@ -1526,17 +1526,14 @@
 and rapid, widespread adoption.
           </dd>
           <dt>Motivation</dt>
-          <dd>
-Different authentication scenarios will require different authentication
-devices. It is important that the array of authentication devices used for
-multi-factor authentication supports what exists today, but is not
-limited to only what exists today.
+          <dd>The payments architecture should support 
+	    the authentication devices available today for
+multi-factor authentication, as well as those of the future.
           </dd>
           <dt>Accessibility</dt>
-          <dd>
-When requiring biometric verification, it is important to provide
-at least two (if not more) alternative mechanisms. Not everyone can provide
-fingerprints or detailed iris scans.
+          <dd>Not everyone can provide fingerprints or detailed iris scans.
+	    Therefore, it is important to offer multiple forms
+	    biometric verification to improev accessibility.
           </dd>
         </dl>
 
@@ -1552,13 +1549,13 @@
           </dd>
           <dt>Motivation</dt>
           <dd>
-Easing regulatory compliance with respect to Know Your Customer (KYC) and
-Anti-Money Laundering (AML) when accessing a payment instrument will ensure
-a safer and faster <a title="payment scheme">payment schemes</a>.
+Easing compliance with Know Your Customer (KYC) and
+Anti-Money Laundering (AML) regulations 
+will ensure safer and faster <a title="payment scheme">payment schemes</a>.
           </dd>
           <dt>Exceptions</dt>
           <dd>
-If a company detects that a customer is on an applicable blacklist, the
+If a <a>payee</a> detects that a <a>payer</a> is on an applicable blacklist, the
 transaction must not proceed.
           </dd>
         </dl>
@@ -1625,12 +1622,10 @@
               </ul>
             </dd>
             <dt>Accessibility</dt>
-            <dd>
-Any sort of biometric identification should ensure that people with
-accessibility concerns are able to use alternate means to achieve the
-authentication requirement. For example, allowing multiple forms of
-biometric authentication is better than providing just one form.
-            </dd>
+          <dd>Not everyone can provide fingerprints or detailed iris scans.
+	    Therefore, it is important to offer multiple forms
+	    biometric verification to improev accessibility.
+          </dd>
           </dl>
         </section>