- From: Thomas Hardjono <hardjono@mit.edu>
- Date: Mon, 7 Dec 2015 18:41:32 +0000
- To: Bob Way <bob@ripple.com>
- CC: Interledger Community Group <public-interledger@w3.org>
>>> From: Bob Way [mailto:bob@ripple.com] >>> Sent: Monday, December 07, 2015 11:23 AM >>> To: Ryan Fugger >>> Cc: Nitin Gaur; Interledger Community Group >>> Subject: Re: Roll call / intro - expand the scope >>> of Interledger Protocol to beyond payment >>> .... >>> …yes, we could wander lost in these weeds forever… >>> >>> What is worth realizing, is that while we often think >>> of the delivery half of a >>> business transaction as happening after the payment, >>> the delivery must always negotiated before the >>> payment can even be determined. >>> >>> As such, we can encapsulate the details of the >>> delivery half of the transaction into a single >>> contract document. Alice and Bob must agree on the >>> terms of this contract before the payment can take place. >>> But otherwise, this contract can be completely >>> opaque to the payment half of the transaction. >>> In fact, you can simply hash the contract and >>> use that as a proxy for all the delivery side details. >>> >>> This contract hash can than be signed (as the >>> ILP payment “receipt") to both trigger payment >>> execution and to signify agreement to the >>> contract’s delivery terms. Thanks Bob, Apologies -- didn't mean to come across somewhat negative. Discussions are needed for this group to move forward. Here are a bunch of questions I have with regards to interconnecting ledgers: - What does it mean to connect ledgers when it pertains to data/assets/records belonging to different verticals (e.g. health, finance, etc). - Where does the semantic information regarding a given ledger is located, and how to discover. - How to do access control on private ledgers at a global scale. /thomas/
Received on Monday, 7 December 2015 18:42:03 UTC