Re: making the webcredits.org spec more strict about 'source' and 'destination' fields.

On 05/02/2012 02:56 AM, Michiel de Jong wrote:
> oops! there we go already... i just looked up
> http://purl.org/commerce#Transfer and it's actually the other way
> around. The statement represents a transfer, so presumably Melvin
> gave Nathan money, and it's now actually Nathan who owes Melvin
> money.

We could add a vocabulary term for IOU or Credit or Debit to the
PaySwarm vocabulary if that would help matters - Melvin, thoughts?

> or maybe it's unspecified who owes who the 5 euros? maybe we need to
> leave it open. ;)

No, a Transfer in PaySwarm is directional - source -> destination.

> i'm also a bit confused btw by the relationship between the
> 'webpayments' community group and the 'webcredits' spec

The Web Payments Community Group is a loosely knit group that is
actively working on standards related to payments and finance on the
Web. PaySwarm is one of those specs. So is WebCredits, so is
OpenTransact (although, there is another mailing list for the
nitty-gritty on that). I'd like to think that this group is welcoming of
all open financial standards that would like a clear pathway to
standardization at W3C.

That said, we should list the work that this group is interested in and
actively developing.

> and the fact that the type of a webcredit can apparently be
> 'transfer' (which to me means more transaction or payment than
> credit), doesn't help with that.

This may be a bug in the WebCredits spec - Melvin?

> maybe the webpayments CG wiki should list the specs that are relevant
> for it, so webcredits and payswarm iiuc, and maybe also mention
> opentransact and ripple as related work?

http://www.w3.org/community/webpayments/wiki/Main_Page#Projects

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny)
President/CEO - Digital Bazaar, Inc.
blog: PaySwarm Website for Developers Launched
http://digitalbazaar.com/2012/02/22/new-payswarm-alpha/

Received on Wednesday, 2 May 2012 14:33:23 UTC