public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gary Rowe <g.rowe@froot.co.uk>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP 20 Rejected, process for BIP 21N
Date: Tue, 31 Jan 2012 22:37:50 +0000	[thread overview]
Message-ID: <CAKm8k+0o0fBcBgRMOEc3nycGaLN7EEvfQ5wrZN4XwO5Gk2Pk5w@mail.gmail.com> (raw)
In-Reply-To: <jg9p4a$c90$1@dough.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]

Andreas has a good point. See RFC 3986 on URI schemes:
http://tools.ietf.org/html/rfc3986#page-12

The colon is a reserved general delimiter (similar in use to the / in a
typical URL, but applies to URNs etc). As suggested, we get req:something
being changed to one of the unreserved characters that do not have to be
URL encoded. Again, from the RFC these are

* Option A: req_something (underscore)
* Option B: req-something (hyphen)
* Option C: req~something (tilde)
* Option D: req.something (period)

Personally, my eye likes Option B, the hyphen.

On 31 January 2012 22:14, Andreas Schildbach <andreas@schildbach.de> wrote:

> On 01/31/2012 07:22 PM, Matt Corallo wrote:
>
> > that "It is recommended that additional variables prefixed with
> > mustimplement: not be used in a mission-critical way until a grace
>
> Is the ':' sign actually allowed in URL parameter names
> (unescaped/unencoded)? If not, I'd propose an unrestricted char instead,
> maybe '_'.
>
>
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

[-- Attachment #2: Type: text/html, Size: 2384 bytes --]

  reply	other threads:[~2012-01-31 22:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31 14:27 [Bitcoin-development] BIP 20 Rejected, process for BIP 21N Amir Taaki
2012-01-31 14:33 ` slush
2012-01-31 14:52   ` Amir Taaki
     [not found]   ` <CAKm8k+1cHagzj3T27S=h0PueH8EgcCkEajZGgAw7HcQ=N-46ow@mail.gmail.com>
2012-01-31 14:53     ` Gary Rowe
2012-01-31 15:02       ` Gregory Maxwell
2012-01-31 15:04         ` Gary Rowe
2012-01-31 14:59   ` Gregory Maxwell
2012-01-31 16:04 ` Matt Corallo
2012-01-31 18:22   ` Matt Corallo
2012-01-31 19:02     ` Wladimir
2012-01-31 21:42       ` Matt Corallo
2012-01-31 22:14     ` Andreas Schildbach
2012-01-31 22:37       ` Gary Rowe [this message]
2012-01-31 22:47         ` Matt Corallo
2012-02-04 14:03     ` thomasV1
2012-02-04 16:03       ` Gary Rowe
2012-02-04 17:15         ` Matt Corallo
2012-01-31 16:07 ` Luke-Jr
2012-02-02 17:07 Gary Rowe
2012-02-02 17:39 ` Matt Corallo
2012-02-02 17:46   ` Gary Rowe

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=CAKm8k+0o0fBcBgRMOEc3nycGaLN7EEvfQ5wrZN4XwO5Gk2Pk5w@mail.gmail.com \
    --to=g.rowe@froot.co.uk \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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