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>
Subject: Re: [Bitcoin-development] Bitcoin meets the Semantic Web....
Date: Fri, 11 Oct 2013 13:27:49 +0200 [thread overview]
Message-ID: <CAKaEYhLU2JUB9P_HKpmp=CtM7ckFf+maeQwkS79c4WPFBx66Og@mail.gmail.com> (raw)
In-Reply-To: <CAKaEYh+bzUdLtt7Vg7nyY0UMd1Y3+Sdnqo_+Qjyj_pc6-ZY+6A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2594 bytes --]
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!
[-- Attachment #2: Type: text/html, Size: 3797 bytes --]
prev parent reply other threads:[~2013-10-11 11:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 7:59 Melvin Carvalho
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 [this message]
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='CAKaEYhLU2JUB9P_HKpmp=CtM7ckFf+maeQwkS79c4WPFBx66Og@mail.gmail.com' \
--to=melvincarvalho@gmail$(echo .)com \
--cc=arto@bendiken$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=msporny@digitalbazaar$(echo .)com \
--cc=nrixham@gmail$(echo .)com \
/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