Update Extensibility section to reflect WPWG decision.

Decision can be found here: w3c/webpayments#83

index.html

@@ -64,7 +64,7 @@
   wgURI:        "http://www.w3.org/community/webpayments/",
 
   // name (with the @w3c.org) of the public mailing to which comments are due
-  wgPublicList: "public-webpayments@w3.org",
+  wgPublicList: "public-webpayments",
 
   // URI of the patent status for this WG, for Rec-track documents
   // !!!! IMPORTANT !!!!
@@ -859,16 +859,30 @@ <h2>Extensibility</h2>
 depend on. It is expected that other properties and values will be stored in
 objects that implement the various interfaces in this specification (e.g.
 <a>PaymentApplication</a>, <a>PaymentRequest</a>,
-<a>PaymentAcknowledgement</a>, etc.). Implementations MUST
-preserve unrecognized properties and their associated values.
+<a>PaymentAcknowledgement</a>, etc.). While this specification does not
+suggest a single extension mechanism, it does assert that
+extensibility MUST be possible. To that end,
   </p>
 
-  <p>
-While this specification does not suggest a single extension mechanism, it
-does assert that extensibility MUST be possible.
+  <ul>
+    <li>
+Implementations MUST preserve unrecognized properties and their
+associated values.
+    </li>
+    <li>
+Another specification [LINK_TBD] explains how to extend the
+parameters used with this API using JSON-LD.
+    </li>
+  </ul>
+
+  <p class="issue">
+The Working Group seeks feedback from the Web community on that
+specification and how well it furthers interoperability needs in the
+payments ecosystem. To provide feedback, see the
+<a href="#h-sotd">status section</a> above.
   </p>
 
-  <section>
+  <!-- section>
     <h3>Extending Messages Using JSON-LD</h3>
 
     <p>
@@ -909,14 +923,20 @@ <h3>Extending Messages Using JSON-LD</h3>
 a required value of "https://w3id.org/payments/v1" to the appropriate
 interfaces?
   </p>
-  </section>
+  <section-->
 </section>
 
 <section>
   <h2>Security Considerations</h2>
 
   <section>
     <h3>Message Integrity</h3>
+    <p class="issue">
+This section has not been discussed by the WG and is kept here as
+a placeholder for a larger discussion around ensuring
+message integrity.
+    </p>
+
     <p>
 It is possible to sign any JSON-LD based message by using
 Linked Data Signatures, like so:
@@ -1140,9 +1160,9 @@ <h2>Acknowledgements</h2>
 
 </section>
 
-<script src='//code.jquery.com/jquery-2.1.3.min.js' class='remove'></script>
-<script src='//coffeescript.org/extras/coffee-script.js' class='remove'></script>
-<script src='//jumly.tmtk.net/public/jumly.min.js' class='remove'></script>
+<script src='jquery-2.1.3.min.js' class='remove'></script>
+<script src='coffee-script.js' class='remove'></script>
+<script src='jumly.min.js' class='remove'></script>
 
 </body>
 </html>