Add assumptions section from Ian's use cases document.
authorManu Sporny <>
Thu, 12 Mar 2015 00:49:31 -0400
changeset 612 dd7c345ba58a
parent 611 b4398c55975f
child 613 cf0f522da82a
Add assumptions section from Ian's use cases document.
--- a/latest/use-cases/index.html	Wed Mar 11 01:41:34 2015 -0400
+++ b/latest/use-cases/index.html	Thu Mar 12 00:49:31 2015 -0400
@@ -495,6 +495,44 @@
+      <h3>Assumptions</h3>
+      <p>
+The use cases below rely on a number of assumptions that are not
+detailed in the use cases but that will be explored in more detail in
+the architecture and requirements documents.
+      </p>
+      <ul>
+        <li>
+<strong>Connectivity</strong>. Connectivity requirements vary according to
+use case. The types of connections a device may utilize include Internet
+connectivity, proxied connections through short-range radio transmissions,
+and proximity connections over a technology such as Near-Field Communication
+(NFC) or Bluetooth Low Energy (BTLE). Some use cases assume no
+connectivity (e.g., user is temporarily unable to connect to a mobile phone
+network or a WiFi hotspot).
+        </li>
+        <li>
+<strong>Registered Payment Instruments</strong>. In order for the
+<tref>payer</tref> to select and utilize payment instruments, they must be
+registered in some way and discoverable by a browser, native application,
+or other software.
+        </li>
+        <li>
+<strong>Security</strong>. Keys, encryption, and other security technology
+must be used to secure sensitive information. It is important that sensitive
+information is not transmitted to parties that do not absolutely need to
+know the information in order to complete the transaction.</li>
+        <li>
+<strong>Identity</strong>. There will be a consistent, interoperable
+identifier used to identify the participants and accounts in a Web Payments
+        </li>
+      </ul>
+    </section>
+    <section>
       <h3>Negotiation of Payment Terms</h3>