From 814702c5f937ebf66f075071ae13f29b20a13535 Mon Sep 17 00:00:00 2001
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Wed, 16 Mar 2016 12:56:35 -0400
Subject: [PATCH] Add reference to issue #47.

---
 specs/paymentrequest.html | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/specs/paymentrequest.html b/specs/paymentrequest.html
index e7f1c09b..4065b4a1 100644
--- a/specs/paymentrequest.html
+++ b/specs/paymentrequest.html
@@ -348,6 +348,12 @@ <h2>PaymentRequest constructor</h2>
           currently described in the specification.
         </div>
 
+        <div class="issue" data-number="47" title="Should a payment request be just data, or a programmable object?">
+          There is an open issue about whether the payment request should
+          be a programmable object or should be just pure data that can be
+          operated on by methods.
+        </div>
+
         <div class="issue" data-number="19" title="Should the API handle pre-auth, recurring payments, and similar scenarios">
           There is an open issue about whether the API should handle occasions when a site wants to request a payment
           method but not actually make a charge immediately. These may include identification validation, pre-auth