Re: implementations of "XML Voucher: Generic Voucher Language" ?

[lynn.wheeler@firstdata.com]

as an aside, X9.59 financial standard that recently passed (electronic standard
for all retail payments) also incorporates the message digest of the purchase
order (or contract) in the body of the payment message.

as specified in the standard, the payment message encoding format is ASN.1 ...
however the appendix includes an example in FSML (financial standards markup
language ... precursor to much of the XML financial related specifications).

financial standards bodys are at

http://www.x9.org/
http://www.tc68.org/

for some fsml related information

http://www.echeck.org/

misc. x9.59 information

http://www.garlic.com/~lynn/






Ian Grigg <iang@systemics.com> on 03/05/2001 08:59:35 AM

Please respond to iang@systemics.com

To:   Ko Fujimura <fujimura@isl.ntt.co.jp>
cc:   Rachel Willmer <rachel@intertrader.com>, ietf-trade@lists.elistx.com,
      dbs@philodox.com
Subject:  Re: implementations of "XML Voucher: Generic Voucher Language" ?




That's an interesting point.  In our system, the identity of the
contract is provided by a canonical message digest (calculated
over the readable contract) which is used as the identifier in
payments.  There is nothing in the SOX protocol that limits the
usage to that digest, and nothing in the Ricardian Contract that
says which protocol to use (and indeed, it is possible to plugin
a separate payment system into WebFunds, and use Ricardian Contracts),
it's mostly an implementation issue.

However, there is ample flexibility in the contract format, and
indeed, any similar format like your XML Voucher one, to add a
limitation of protocol.  That might become interesting in the
future as we are adding different transaction types to WebFunds
as a background task, and are using Ricardian Contracts in areas
that don't involve SOX directly.

--
iang