- From: Joseph Potvin <jpotvin@opman.ca>
- Date: Thu, 14 May 2015 10:08:44 -0400
- To: Web Payments CG <public-webpayments@w3.org>
- Message-ID: <CAKcXiSoUb8RJ4rZhG_DRsmtz1sbQDRdzUyed09-Pi_H+E4st0A@mail.gmail.com>
I would like to raise a general consideration to the CG list: What aspects of a "Web Payments: Technical Architecture" are unique to "Web" mediated payment, what what aspects are generic to payment via any medium? It seems to me that a generic payments technical architecture provides the functional system environment within and upon which a Web payments technical architecture occurs. Therefore it seems to me critical to clearly separate these two in the document. The thought I'm attempting to underline is that a Web Payments Technical Architecture must point to an explicit external source that provides a generic Payments Achitecture, preferably one provided and maintained by a genuine global standards body, or something that in effect serves that function. The generic Payment Architecture ought to be sufficiently refined as to be consistent across all media A Web Payments Technical Architecture must (I would have thought) restrict its additive scope to that which is within the domain of the W3C, while explicitly referencing (in its text and diagrams) the generic Payments Achitecture that it is engaging. -- Joseph Potvin Operations Manager | Gestionnaire des opérations The Opman Company | La compagnie Opman jpotvin@opman.ca Mobile: 819-593-5983
Received on Thursday, 14 May 2015 14:09:34 UTC