From: Melvin Carvalho <melvincarvalho@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Bitcoin meets the Semantic Web....
Date: Mon, 1 Apr 2013 09:59:02 +0200 [thread overview]
Message-ID: <CAKaEYh+bzUdLtt7Vg7nyY0UMd1Y3+Sdnqo_+Qjyj_pc6-ZY+6A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 779 bytes --]
next reply other threads:[~2013-04-01 7:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 7:59 Melvin Carvalho [this message]
2013-04-01 9:35 ` Harald Schilly
2013-04-01 19:57 ` Melvin Carvalho
2013-04-01 20:13 ` Harald Schilly
2013-10-11 11:27 ` Melvin Carvalho
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKaEYh+bzUdLtt7Vg7nyY0UMd1Y3+Sdnqo_+Qjyj_pc6-ZY+6A@mail.gmail.com \
--to=melvincarvalho@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox