--- a/latest/charters/payments-wg-charter.html Fri Jul 17 00:19:50 2015 -0400
+++ b/latest/charters/payments-wg-charter.html Fri Jul 17 08:01:57 2015 -0500
@@ -269,9 +269,9 @@
<h3 id="wallets">Relation to Wallets</h3>
<p>The standards from this group may be implemented in a variety of ways, including within stand-alone Web or
- native applications, within applications in the Cloud, within user agents such as Web browsers or in the
+ native applications, within applications in the Cloud, within user agents such as Web browsers, or in the
form of user agent extensions or plug-ins. Some of the capabilities provided by the standards from this
- group can be found in various Web services today, as well as in digital wallets. Because the "digital
+ group can be found in today's digital wallets and various other Web services. Because the "digital
wallet" concept is useful as a shorthand, but means different things to different audiences, this charter
includes the following definition to clarify the intent of this group.</p>
@@ -290,27 +290,20 @@
function that is complimentary to its payment capabilities.
</li>
</ul>
- <p>The group will not attempt to standardize all functions of a wallet in this first version of standards but
- will be focused primarily on the payment flow as described in the <a href="#scope">scope</a> and the wallet
- capabilities required to execute this flow.</p>
+ <p>This group is not developing standards for all digital wallet capabilities. This charter's scope is limited to payment flow capabilities. In the future, W3C expects to expand its activities to standardize additional
+ functions of physical wallets
+ such as holding digital receipts and digital credentials.
+ The definition of wallet in this charter is not intended to constrain W3C's future activities. Furthermore, the wallet metaphor appropriate to this charter may change in future charters or may become inappropriate.</p>
- <p>This definition of wallet may expand in the future to include other items people find in physical wallets
- such as digital receipts and digital credentials. What the group defines today as a wallet service may
- in future offer new functionality that even makes the wallet metaphor entirely inappropriate. Therefor the
- label <em>"wallet"</em>, while appropriate today, should not imply any limitation on the functionality that
- this service may be expected to provide under future versions of any standards produced by the group.</p>
-
- <p>The group intends to create a standard interface from the Web to a user's wallet so that a user with any
+ <p>This Working Group intends to create a standard interface from the Web to a user's wallet so that a user with any
conforming wallet can seamlessly make payments with any conforming application running in a conforming
user agent. The group may define APIs that will also be used outside of a user agent context (such as
between
Web services, or from within a native application, where the browser is not the proxy between wallet and
payee application).</p>
- <p>The group may also consider the use case where an aggregation service stands in place of a wallet service
- and offers the user a wider choice of payment solutions by combining the functionality of multiple wallet
- services or performing a complex payment instrument discovery process to collect the set of payment
- instruments the user has available.</p>
+ <p>The group may also consider the use case where an aggregation service acts as a more sophisticated wallet service or providing a wider choice of payment solutions to the user. For example, the aggregator service might combine the functionality of multiple wallet services, or apply a more complex payment instrument discovery algorithm to collect the set of payment
+ instruments available to the user.</p>
<p>
<strong>Note:</strong> The Working Group anticipates a rich ecosystem of eCommerce and payment