public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Harald Schilly <harald@schil.ly>
To: Melvin Carvalho <melvincarvalho@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin meets the Semantic Web....
Date: Mon, 1 Apr 2013 22:13:36 +0200	[thread overview]
Message-ID: <CAGG4CB6Zctb9-cgv9aQywD7J5_Er6LTdbSjFYiY5-STwt2+-jg@mail.gmail.com> (raw)
In-Reply-To: <CAKaEYh+PPccdHjzd6re4ru2M0fwaO9Ehr7qRYjQABun0qaA3Ow@mail.gmail.com>

On Mon, Apr 1, 2013 at 9:57 PM, Melvin Carvalho
<melvincarvalho@gmail.com> wrote:
> 1. bitcoin.org -- logical, but no https and github doesnt let you set mime
> types

This one looks also logical to me. I'm not an semantic web expert, but
from what you wrote I suggest to use a subdomain. Would this be
possible for a schema? E.g. schema.bitcoin.org and it points to an
indepedently run server for the files …

H



  reply	other threads:[~2013-04-01 20:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-01  7:59 [Bitcoin-development] Bitcoin meets the Semantic Web Melvin Carvalho
2013-04-01  9:35 ` Harald Schilly
2013-04-01 19:57   ` Melvin Carvalho
2013-04-01 20:13     ` Harald Schilly [this message]
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=CAGG4CB6Zctb9-cgv9aQywD7J5_Er6LTdbSjFYiY5-STwt2+-jg@mail.gmail.com \
    --to=harald@schil.ly \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=melvincarvalho@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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