Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <harald.schilly@gmail.com>) id 1UMb9r-0003y0-8i
	for bitcoin-development@lists.sourceforge.net;
	Mon, 01 Apr 2013 09:36:07 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.210.181 as permitted sender)
	client-ip=209.85.210.181; envelope-from=harald.schilly@gmail.com;
	helo=mail-ia0-f181.google.com; 
Received: from mail-ia0-f181.google.com ([209.85.210.181])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1UMb9o-0004DW-7o
	for bitcoin-development@lists.sourceforge.net;
	Mon, 01 Apr 2013 09:36:07 +0000
Received: by mail-ia0-f181.google.com with SMTP id o25so1750288iad.12
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 01 Apr 2013 02:35:58 -0700 (PDT)
X-Received: by 10.43.65.145 with SMTP id xm17mr4822871icb.35.1364808958724;
	Mon, 01 Apr 2013 02:35:58 -0700 (PDT)
MIME-Version: 1.0
Sender: harald.schilly@gmail.com
Received: by 10.64.45.102 with HTTP; Mon, 1 Apr 2013 02:35:28 -0700 (PDT)
In-Reply-To: <CAKaEYh+bzUdLtt7Vg7nyY0UMd1Y3+Sdnqo_+Qjyj_pc6-ZY+6A@mail.gmail.com>
References: <CAKaEYh+bzUdLtt7Vg7nyY0UMd1Y3+Sdnqo_+Qjyj_pc6-ZY+6A@mail.gmail.com>
From: Harald Schilly <harald@schil.ly>
Date: Mon, 1 Apr 2013 11:35:28 +0200
X-Google-Sender-Auth: y4s6xdnTqhcVZTbBTMxYrOYKokY
Message-ID: <CAGG4CB6OJPAQwj=Fjyf5gidfj7D8_KmmX9M4Ut+saG0YQBibjA@mail.gmail.com>
To: Melvin Carvalho <melvincarvalho@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(harald.schilly[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1UMb9o-0004DW-7o
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin meets the Semantic Web....
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 01 Apr 2013 09:36:07 -0000

On Mon, Apr 1, 2013 at 9:59 AM, Melvin Carvalho
<melvincarvalho@gmail.com> wrote:
> The first step that needs to be done is to create a "vocabulary" for
> bitcoin.

Hi, have you checked out databases like OKFN and searched for existing
vocabularies for payments? I don't think it's a great idea to
re-invent it, if there is already some existing protocol.

random search gave me that:

http://schema.org/PaymentMethod

http://www.heppnetz.de/ontologies/goodrelations/v1#PayPal << adding
something right here for bitcoin!? (diners club and similar also exist
there)

payment relationships:
http://iig2.com/b2bo/ns.html#

more search results:
http://lov.okfn.org/dataset/lov/search/#s=payment

Harald