RE: [xri] Encoding plus (+) sign

["Drummond Reed" <drummond.reed@cordance.net>]

To close on this thread, the following was recorded in the minutes of the
2006/05/25 TC telecon:

* The decision was that:

  * Since the QXRI in an HXRI must be in URI normal form, all non-URI-safe
character must already be percent-encoded.
  * In addition we MUST require percent encoding of "#", "[", and "]" as
general delimiters per requirements of RFC 3986.
  * We currently require percent encoding of "&" because it is the query
parameter delimiter.
  * Because we already require these other percent encodings, we will
require percent encoding of "+" for compatability with widely implemented
CGI libraries that will transcode this into space or %20.

=Drummond 

-----Original Message-----
From: Victor Grey [mailto:victor@idcommons.org] 
Sent: Saturday, May 20, 2006 5:02 PM
To: Drummond Reed
Cc: 'Wachob, Gabe'; 'Tan, William'; xri@lists.oasis-open.org
Subject: Re: [xri] Encoding plus (+) sign

Drummond Reed wrote:
> We never closed this thread regarding whether or not we need to 
> specify that the + sign (or other symbols) require encoding when used 
> in HXRI query parameters during XRI proxy resolution.

FWIW, both PHP 'urlencode' and perl 'URI::Escape' do escape the '+' to 
%2B by default. (Ruby is agnostic.)
=vg