W3C home > Mailing lists > Public > public-webpayments@w3.org > May 2015

Re: The Payments Architecture within which a Web Payments Architecture occurs

From: Joseph Potvin <jpotvin@opman.ca>
Date: Thu, 14 May 2015 10:59:34 -0400
Message-ID: <CAKcXiSrsR9Up7jv=mEyL9bMBwJFjTW9fqYHoR8q04mQVP=PSEA@mail.gmail.com>
To: Web Payments CG <public-webpayments@w3.org>
The issue that I'm raising is that a "Payments Architecture" in general is
orthogonal to the "Architecture of the World Wide Web". Any architecture
for "web mediated payments" needs to reference a Payments Architecture that
is abstracted from whatever media are employed. And any architecture for
"web mediated e-commerce" needs to reference an Commerce Architecture that
is abstracted from whatever media are employed.

Joseph Potvin
Operations Manager | Gestionnaire des opérations
The Opman Company | La compagnie Opman
jpotvin@opman.ca
Mobile: 819-593-5983

On Thu, May 14, 2015 at 10:38 AM, Melvin Carvalho <melvincarvalho@gmail.com>
wrote:

>
>
> On 14 May 2015 at 16:08, Joseph Potvin <jpotvin@opman.ca> wrote:
>
>> 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.
>>
>
> Web arch is about naming things using URIs as per awww [1].  The payments
> work builds on that, and leverages other web technologies such as HTTP,
> linked data, JSON LD etc.
>
> [1] http://www.w3.org/TR/webarch/
>
>
>>
>> --
>> Joseph Potvin
>> Operations Manager | Gestionnaire des opérations
>> The Opman Company | La compagnie Opman
>> jpotvin@opman.ca
>> Mobile: 819-593-5983
>>
>
>


-- 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 15:00:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:07:40 UTC