blob: d554cccbb53207a17912d752a1381e65f60e7afa (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <melvincarvalho@gmail.com>) id 1UMZe3-0000fC-MW
for bitcoin-development@lists.sourceforge.net;
Mon, 01 Apr 2013 07:59:11 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.217.178 as permitted sender)
client-ip=209.85.217.178; envelope-from=melvincarvalho@gmail.com;
helo=mail-lb0-f178.google.com;
Received: from mail-lb0-f178.google.com ([209.85.217.178])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UMZe1-0004ru-Pp
for bitcoin-development@lists.sourceforge.net;
Mon, 01 Apr 2013 07:59:11 +0000
Received: by mail-lb0-f178.google.com with SMTP id q13so1726790lbi.9
for <bitcoin-development@lists.sourceforge.net>;
Mon, 01 Apr 2013 00:59:03 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.112.43.232 with SMTP id z8mr5304492lbl.135.1364803142936;
Mon, 01 Apr 2013 00:59:02 -0700 (PDT)
Received: by 10.112.143.38 with HTTP; Mon, 1 Apr 2013 00:59:02 -0700 (PDT)
Date: Mon, 1 Apr 2013 09:59:02 +0200
Message-ID: <CAKaEYh+bzUdLtt7Vg7nyY0UMd1Y3+Sdnqo_+Qjyj_pc6-ZY+6A@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=e0cb4efe340085f4ad04d947feb5
X-Spam-Score: -0.6 (/)
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
(melvincarvalho[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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: 1UMZe1-0004ru-Pp
Subject: [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 07:59:11 -0000
--e0cb4efe340085f4ad04d947feb5
Content-Type: text/plain; charset=ISO-8859-1
I'm working on porting crypto currencies to the semantic web.
The advantages of this is that pages can then become machine readable on
the web allowing new types of innovation and spreading bitcoin information
to a wider audience.
The first step that needs to be done is to create a "vocabulary" for
bitcoin.
What this means is like a dictionary of terms that can be put down in a
machine readable standard (called RDF).
I was wondering if anyone has worked on this before or if there is a human
readable "glossary" for bitcoin that I could take text from?
seeAlso: https://bitcointalk.org/index.php?topic=163705.0
--e0cb4efe340085f4ad04d947feb5
Content-Type: text/html; charset=ISO-8859-1
<div dir="ltr"><div>I'm working on porting crypto currencies to the semantic web.<br><br>The
advantages of this is that pages can then become machine readable on
the web allowing new types of innovation and spreading bitcoin
information to a wider audience.<br><br>The first step that needs to be done is to create a "vocabulary" for bitcoin.<br><br>What this means is like a dictionary of terms that can be put down in a machine readable standard (called RDF).<br>
<br>I
was wondering if anyone has worked on this before or if there is a
human readable "glossary" for bitcoin that I could take text from?<br><br></div>seeAlso: <a href="https://bitcointalk.org/index.php?topic=163705.0">https://bitcointalk.org/index.php?topic=163705.0</a><br></div>
--e0cb4efe340085f4ad04d947feb5--
|
