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
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
|
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 1VUasv-0002nh-IW
for bitcoin-development@lists.sourceforge.net;
Fri, 11 Oct 2013 11:27:57 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.41 as permitted sender)
client-ip=209.85.215.41; envelope-from=melvincarvalho@gmail.com;
helo=mail-la0-f41.google.com;
Received: from mail-la0-f41.google.com ([209.85.215.41])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VUasu-0007D3-5E
for bitcoin-development@lists.sourceforge.net;
Fri, 11 Oct 2013 11:27:57 +0000
Received: by mail-la0-f41.google.com with SMTP id ec20so3337002lab.0
for <bitcoin-development@lists.sourceforge.net>;
Fri, 11 Oct 2013 04:27:49 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.3.42 with SMTP id 10mr16167059laz.22.1381490869373; Fri,
11 Oct 2013 04:27:49 -0700 (PDT)
Received: by 10.112.159.233 with HTTP; Fri, 11 Oct 2013 04:27:49 -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>
Date: Fri, 11 Oct 2013 13:27:49 +0200
Message-ID: <CAKaEYhLU2JUB9P_HKpmp=CtM7ckFf+maeQwkS79c4WPFBx66Og@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Manu Sporny <msporny@digitalbazaar.com>,
Arto Bendiken <arto@bendiken.net>, Nathan Rixham <nrixham@gmail.com>
Content-Type: multipart/alternative; boundary=089e013d14b287914a04e8756848
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
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: w3id.org]
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: 1VUasu-0007D3-5E
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: Fri, 11 Oct 2013 11:27:58 -0000
--089e013d14b287914a04e8756848
Content-Type: text/plain; charset=ISO-8859-1
On 1 April 2013 09:59, Melvin Carvalho <melvincarvalho@gmail.com> wrote:
> 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
>
Hi All
Sorry for the delay on this. I've made a very simple start, and am hosting
the vocabulary at.
https://w3id.org/cc
Having chatted on IRC, I'm not only going to model bitcion, but all crypto
currencies in time, starting first with bitcoin. There's only one use case
currently support, which is a way to tell the semantic web that a link is a
bitcoin address (I know you can already introspect on the bitcoin: link but
introspection requires out of band knowledge). More explanation below:
*Use Case
*
As a publisher Alice would like to link her web page content (or app) to a
bitcoin address, so that donations can be received by those that have
enjoyed her work.
*Model
*
It's only a slight overhead to model all crypto currencies so perhaps the
model will be something like
URI -> crypto-currency-address -> bitcoin-address
*Implementation
*
The folks at w3id.org have kindly offered to user their permanent
identifier switchboard, then we redirect to a locked down vocabulary.
As an implementer you simply need to add a single rel= tag to your markup.
*Example Usage*
In a web page:
<*meta* rel="https://w3id.org/cc#bitcoin<https://w3id.org/cc#bitcoin-address>"
href="bitcoin:1234...." />
In an html5 app:
<a rel="https://w3id.org/cc#bitcoin <https://w3id.org/cc#bitcoin-address>"
href="bitcoin:1234...."></a>
*Note: you an provide context for an individual concept in HTML5 (as
opposed to the webpage itself), such as an app, a project, a person, but
using the @about tag.
*
For litecoins (coming soon)
<a rel="https://w3id.org/cc#litecoin <https://w3id.org/cc#litecoin-address>"
href="...."></a>
*Next Steps
*
It's just a small step to start with, can allow all sorts of entities to
start accepting bitcoin in a way that complies with the W3C best
practices. I'll be improving and extending this over time, feedback or
help is welcome!
--089e013d14b287914a04e8756848
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On 1 April 2013 09:59, Melvin Carvalho <span dir=3D"ltr"><<a hre=
f=3D"mailto:melvincarvalho@gmail.com" target=3D"_blank">melvincarvalho@gmai=
l.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>I&#=
39;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=20
the web allowing new types of innovation and spreading bitcoin=20
information to a wider audience.<br><br>The first step that needs to be don=
e 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 s=
tandard (called RDF).<br>
<br>I
was wondering if anyone has worked on this before or if there is a=20
human readable "glossary" for bitcoin that I could take text from=
?<br><br></div>seeAlso: <a href=3D"https://bitcointalk.org/index.php?topic=
=3D163705.0" target=3D"_blank">https://bitcointalk.org/index.php?topic=3D16=
3705.0</a><br>
</div></blockquote><div><br></div><div>Hi All<br><br>Sorry for the delay on=
this.=A0 I've made a very simple start, and am hosting the vocabulary =
at.<br><br><a href=3D"https://w3id.org/cc">https://w3id.org/cc</a><br><br><=
/div>
<div>Having chatted on IRC, I'm not only going to model bitcion, but al=
l crypto currencies in time, starting first with bitcoin.=A0 There's on=
ly one use case currently support, which is a way to tell the semantic web =
that a link is a bitcoin address (I know you can already introspect on the =
bitcoin: link but introspection requires out of band knowledge).=A0 More ex=
planation below:<br>
<br><b>Use Case<br></b><div><br>As a publisher <span class=3D"">Alice</span=
>
would like to link her web page content (or app) to a bitcoin address,=20
so that donations can be received by those that have enjoyed her work.<br><=
br></div><div>
<b>Model<br></b><br></div><div>It's only a slight overhead to model all=
crypto currencies so perhaps the model will be something like<br><br></div=
><div>URI -> crypto-currency-address -> bitcoin-address<br><br>
</div><div><b>Implementation<br></b><br></div><div>The folks at <a href=3D"=
http://w3id.org" target=3D"_blank">w3id.org</a> have kindly offered to user=
their permanent identifier switchboard, then we redirect to a locked down =
vocabulary.<br>
<br></div><div>As an implementer you simply need to add a single rel=3D tag=
to your markup.<br></div><div><br></div><div>
<b>Example Usage</b><br><br></div><div>In a web page:<br></div><div><br><=
;<b>meta</b> rel=3D"<a href=3D"https://w3id.org/cc#bitcoin-address" ta=
rget=3D"_blank">https://w3id.org/cc#bitcoin</a>" href=3D"bitcoin:=
1234...." /><br>
<br><div>In an html5 app:<br></div><br><a rel=3D"<a href=3D"https:/=
/w3id.org/cc#bitcoin-address" target=3D"_blank">https://w3id.org/cc#bitcoin=
</a>" href=3D"bitcoin:1234...."></a><br><br></div><=
div>
<i>Note: you an provide context for an individual concept in HTML5 (as oppo=
sed to the webpage itself), such as an app, a project, a person, but using =
the @about tag.<br></i></div><div><br></div>For litecoins (coming soon)<br>
<br><a rel=3D"<a href=3D"https://w3id.org/cc#litecoin-address" targ=
et=3D"_blank">https://w3id.org/cc#litecoin</a>" href=3D"...."=
;></a><br><br><br></div></div><b>Next Steps<br><br></b></div><div =
class=3D"gmail_extra">
It's just a small step to start with, can allow all sorts of entities t=
o start accepting bitcoin in a way that complies with the W3C best practice=
s.=A0 I'll be improving and extending this over time, feedback or help =
is welcome!<br>
</div></div>
--089e013d14b287914a04e8756848--
|
