Ripple Transaction

[bshambaugh]

Original: Google Groups - Ripple Transaction
seeAlso : Wireframes
seeAlso: YouTube Wireframe Animation

ch_1_2_Ripple (Ripple Transaction)

{transaction}

s1) list_ripplee

When I select REA and Ripple in the Value Network /* panel I get the offer that http://example.org/outsiders/foaf.rdf#me made for :wheel_of_car by making an offer for :Car.

The triples for this offer are inspired by Example #4 of the W3C WebPayments Community Group Web Commerce 1.0 Specification.
It may be interesting to show details about the result of the transaction instead, which would be the receipt, but this seems to be too many triples to show. In addition, perhaps these different aspects of the transaction, such as a the offer and receipt would be able to be selected in some way after clicking on the REA button. For reference, in the receipt, the offer, asset, and license are included.

I only put WebIDs here, i.e. http://example.org/outsiders/foaf.rdf#me and http://bshambaugh.org/foaf.rdf#me, but I need
some way to correlate WebIDs with Ripple URIs or something for Cryptocoin such as Bitmark URIs. I am assuming that everything else, including digital signatures, etcetera, will all be the same. However, there is one exception that I know of.
The licence:TAPR_OHL may need to be expressed with the Open Digital Rights Language. This was inspired by a conversation on the
[email protected] mailing list.

As an additional note, the actual path that the payment transaction takes with the Ripple protocol will be different than shown in the diagram with value flowing directly from the sender to the recipient. This is because Ripple uses a trust network, where people have debits and credits with only agents they trust, so that the net result is value flowing from the sender to receipient. That is debits and credits may extend from A to C to D, and then from D to B, where C and D participate but do not change their net debits and credits.

References:

1. For Ripple URIs:
   Ripple URI-Ripple Wiki, http://wiki.ripple.com/

2. For Bitmark URIs:
   Transaction Data Model*project-bitmark/marking Wiki, https://github.com/project-bitmark/marking/wiki/Transaction-Data-Model

3. For ODRL:
   Open Digital Rights Language Ontology (ODRL), Final Draft Specification, http://www.w3.org/ns/odrl/2/

4. For the license:
   URIs in Licence Template in Payswarm Vocabulary, https://lists.w3.org/Archives/Public/public-webpayments/2014Nov/0034.html

5. For trust networks:
   Ryan Fugger, Money as IOUs in Social Trust Networks & A Proposal for a Decentralized Currency Network Protocol, Version 2, April 18, 2004, http://archive.ripple-project.org/decentralizedcurrency.pdf

[bshambaugh]

**Rationale:

Further Areas to Explore:**