Move content from wiki over to Roadmap.
authorManu Sporny <msporny@digitalbazaar.com>
Fri, 29 May 2015 01:18:54 -0400
changeset 730 ccc3c981c119
parent 729 73d6099d06cb
child 731 45af3b771501
Move content from wiki over to Roadmap.
latest/roadmap/index.html
--- a/latest/roadmap/index.html	Sat May 23 00:06:08 2015 -0400
+++ b/latest/roadmap/index.html	Fri May 29 01:18:54 2015 -0400
@@ -1,64 +1,80 @@
-<!DOCTYPE html> 
-<html> 
-  <head> 
-    <title>Web Payments Roadmap</title> 
-    <meta http-equiv='Content-Type' content='text/html;charset=utf-8'/> 
-    <script src='../respec-w3c-common.js' class='remove'></script> 
-    <script src='../respec-webpayments.js' class='remove'></script> 
-    <script class='remove'> 
+<!DOCTYPE html>
+<html>
+  <head>
+    <title>Web Payments Roadmap 1.0</title>
+    <meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
+    <link rel="stylesheet" href="spec.css">
+    <script src='../respec-w3c-common.js' class='remove'></script>
+    <script src='../respec-webpayments.js' class='remove'></script>
+    <script class='remove'>
       var respecConfig = {
           // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
           specStatus:           "ED",
-          
+
           // the specification's short name, as in http://www.w3.org/TR/short-name/
           shortName:            "web-payments-roadmap",
- 
+
           // if you wish the publication date to be other than today, set this
-          // publishDate:  "2009-08-06",
- 
+          //publishDate:  "2015-04-16",
+
           // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
           // and its maturity status
           // previousPublishDate:  "1977-03-15",
           // previousMaturity:  "CG-DRAFT",
- 
+
           // if there a publicly available Editor's Draft, this is the link
-          //edDraftURI:           "https://web-payments.org/specs/source/use-cases",
- 
+          edDraftURI:           "https://dvcs.w3.org/hg/webpayments/raw-file/default/latest/roadmap/index.html",
+
           // if this is a LCWD, uncomment and set the end of its review period
           // lcEnd: "2009-08-05",
- 
+
           // if you want to have extra CSS, append them to this list
           // it is recommended that the respec.css stylesheet be kept
           //extraCSS:             [],
- 
+
           // editors, add as many as you like
           // only "name" is required
           editors:  [
-              { name: "Pat Doe", url: "http://patdoe.example.com/",
-                company: "ACME", companyURL: "http://acme.example.com/" },
+              { name: "Manu Sporny", url: "https://manu.sporny.org/",
+                company: "Digital Bazaar", companyURL: "http://digitalbazaar.com/" },
+              { name: "Ian Jacobs", url: "http://www.w3.org/People/Jacobs/",
+                company: "W3C", companyURL: "http://www.w3.org/" }
           ],
- 
-          // authors, add as many as you like. 
+
+          // authors, add as many as you like.
           // This is optional, uncomment if you have authors as well as editors.
           // only "name" is required. Same format as editors.
- 
-          //authors:  [
-          //    { name: "Your Name", url: "http://example.org/",
-          //      company: "Your Company", companyURL: "http://example.com/" },
-          //],
+
+          authors:  [
+              { name: "Manu Sporny", url: "https://manu.sporny.org/",
+                company: "Digital Bazaar", companyURL: "http://digitalbazaar.com/" },
+              { name: "Ian Jacobs", url: "http://www.w3.org/People/Jacobs/",
+                company: "W3C", companyURL: "http://www.w3.org/" }              
+          ],
+
+          otherLinks: [{
+            key: "Version control",
+            data: [{
+              value: "Github Repository",
+              href: "https://github.com/w3c/webpayments-ig"
+            }, {
+              value: "Issues",
+              href: "http://www.w3.org/Payments/IG/track/products/9"
+            }]
+          }],
 
           // maximum level of table of contents
-          maxTocLevel: 2,
-      
+          maxTocLevel: 3,
+
           // name of the WG
           wg:           "Web Payments Interest Group",
-          
+
           // URI of the public WG page
           wgURI:        "http://www.w3.org/blog/wpig/",
-          
-          // name (with the @w3c.org) of the public mailing to which comments are due
-          wgPublicList: "public-webpayments-comments@w3.org",
-          
+
+          // name of the public mailing to which comments are due
+          wgPublicList: "public-webpayments-comments",
+
           // URI of the patent status for this WG, for Rec-track documents
           // !!!! IMPORTANT !!!!
           // This is important for Rec-track documents, do not copy a patent URI from a random
@@ -66,45 +82,266 @@
           // Team Contact.
           wgPatentURI:  "http://www.w3.org/2004/01/pp-impl/73816/status",
 
-          preProcess: [ webpayments.preProcess ]/*,
+          //preProcess: [ webpayments.preProcess ]
+          /*,
           alternateFormats: [ {uri: "diff-20111214.html", label: "diff to previous version"} ],
           */
       };
-    </script> 
-  </head> 
-<body> 
-  <section id='abstract'> 
-    <p> 
-Abstract goes here.
-    </p> 
-  </section> 
+      //respecEvents.sub('start-all', webpayments.preProcess.apply);
+    </script>
+    <style type="text/css">
+body {
+  line-height: 1.4em;
+}
+h4 {
+  color: #005A9C;
+}
+dl {
+  margin-top: 20px;
+  margin-bottom: 20px;
+}
+dt,
+dd {
+  line-height: 1.42857143;
+}
+dl > dt:first-of-type {
+  font-weight: bold;
+}
+@media (min-width: 768px), print {
+  .dl-horizontal {
+    margin-bottom: 4em;
+  }
+  .dl-horizontal dt {
+    font-weight: normal;
+    float: left;
+    width: 160px;
+    clear: left;
+    overflow: hidden;
+    text-align: right;
+    text-overflow: ellipsis;
+    white-space: nowrap;
+  }
+  .dl-horizontal dd {
+    margin-left: 180px;
+  }
+  .dl-horizontal dd > ul {
+    padding-left: 20px;
+    margin: 0px;
+  }
+}
+    </style>
+  </head>
+<body>
 
-  <section id='sotd'> 
-    <p> 
-Custom Status of the Document language goes here.
-    </p> 
-  </section> 
-
-  <section> 
-    <h2>Introduction</h2> 
+  <section id='abstract'>
     <p>
-Introduction goes here.
+The purpose of this document is to outline a coherent implementation and 
+deployment strategy for the Web Payments standardization work at W3C.
     </p>
   </section>
 
-  <section> 
-    <h2>Acknowledgements</h2>
- 
+  <section id='sotd'>
     <p>
-The editors are thankful to the following contributions from ...
-(in alphabetical order): 
+This document is a work in progress and is being released early and often
+using an agile process; it is incomplete.
     </p>
-    <p>
-List of contributors/reviewers.
-    </p>
-
   </section>
 
-  </body> 
+  <section>
+    <h2>Introduction</h2>
+
+    <p>
+The purpose of this document is to outline a coherent implementation and 
+deployment strategy for the Web Payments standardization work at W3C.
+This document is separated into sections that describe "versions" that 
+consist of the following:
+    </p>
+    
+    <ul>
+      <li>
+Strategic goals for the version.
+      </li>
+      <li>
+Basic capabilities that are targeted and which groups are responsible for 
+delivering the capabilities.
+      </li>
+      <li>
+Organization of standardization of those capabilities.
+      </li>
+      <li>
+Deployment goals and strategies
+      </li>
+    </ul>
+    
+  </section>
+
+  <section>
+    <h2>Version 1</h2>
+
+    <p>
+The initial implementation of the Web Payments work will focus on delivering 
+standards for a Minimum Viable Platform (MVP) by December 2017.
+    </p>
+    
+    <section>
+      <h3>Goals</h3>
+      <ul>
+        <li>
+Lower cost of integration of payment services via standard wallet 
+(payment agent) APIs.
+        </li>
+        <li>
+Lower cost of satisfying Know Your Customer (KYC) requirements when 
+performing payments.
+        </li>
+        <li>
+Increased usability, privacy, and security for users.        
+        </li>
+      </ul>
+    </section>
+    <section>
+      <h3>Implementation Plan</h3>
+      <p>
+The following table shows the capabilities for this version, with annotations 
+about where those capabilities arise in the payment flow and which groups will 
+work on them. As we progress, we will include links to definitions of these 
+capabilities, descriptions of phases in the use cases document, and 
+draft charters.
+      </p>
+      <table>
+        <thead>
+          <tr>
+            <th style="white-space: nowrap;">Capability</th>
+            <th style="white-space: nowrap;">Supports</th>
+            <th style="white-space: nowrap;">Responsible Group</th>
+          </tr>
+        </thead>
+        <tbody>
+          <tr>
+            <td>
+Initiation of payment with invoice and payment instrument
+            </td>
+            <td>
+Phase 1: <a href="http://www.w3.org/TR/2015/WD-web-payments-use-cases-20150416/#negotiation-of-payment-terms-1">Negotiation of Payment Terms</a>
+            </td>
+            <td>
+Payment Architecture WG
+            </td>
+          </tr>
+          <tr>
+            <td>
+Discovery of payment instruments
+            </td>
+            <td>
+Phase 2: <a href="http://www.w3.org/TR/2015/WD-web-payments-use-cases-20150416/#application-of-marketing-elements">Negotiation of Payment Instruments</a>            
+            </td>
+            <td>
+Credentials WG
+            </td>
+          </tr>
+          <tr>
+            <td>
+            
+            </td>
+            <td>
+<a href=""></a>            
+            </td>
+            <td>
+            
+            </td>
+          </tr>
+          <tr>
+            <td>
+            
+            </td>
+            <td>
+<a href=""></a>            
+            </td>
+            <td>
+            
+            </td>
+          </tr>
+          <tr>
+            <td>
+            
+            </td>
+            <td>
+<a href=""></a>            
+            </td>
+            <td>
+            
+            </td>
+          </tr>
+          <tr>
+            <td>
+            
+            </td>
+            <td>
+<a href=""></a>            
+            </td>
+            <td>
+            
+            </td>
+          </tr>
+          <tr>
+            <td>
+            
+            </td>
+            <td>
+<a href=""></a>            
+            </td>
+            <td>
+            
+            </td>
+          </tr>
+          <tr>
+            <td>
+            
+            </td>
+            <td>
+<a href=""></a>            
+            </td>
+            <td>
+            
+            </td>
+          </tr>
+          <tr>
+            <td>
+            
+            </td>
+            <td>
+<a href=""></a>            
+            </td>
+            <td>
+            
+            </td>
+          </tr>
+          <tr>
+            <td>
+            
+            </td>
+            <td>
+<a href=""></a>            
+            </td>
+            <td>
+            
+            </td>
+          </tr>
+        </tbody>
+      </table>
+    </section>
+  </section>
+
+  <section class="appendix">
+    <h2>Acknowledgements</h2>
+    <p>
+The editors wish to thank the participants of the
+<a href="http://www.w3.org/Payments/IG/">Web Payments Interest Group</a>
+for discussions about and contributions to this document, as well as the
+<a href="https://www.w3.org/community/webpayments/">Web Payments Community
+Group</a> for earlier work that informed this document.
+    </p>
+  </section>
+
+  </body>
 </html>
-