Re: [xri] ED07 Issue #1: Encoding of + in query parameters

["Tan, William" <William.Tan@neustar.biz>]

<similarly-immature>
God, Gabe! Anything constructive to say? LoLz!
</similarly-immature>

IF:
1. we want to allow ANY URI to be used in _xrd_t
2. and we don't want to require that minters of HXRI to escape 
"problematic characters" such as '%' in _xrd_t value
3. and we don't want to require '+' to be encoded as %2B

Then we can't disallow %20, because who knows that %20 meant a SPACE 
character (character semantics) or just byte value \x20 (byte 
semantics). After all, it is a URI, and if we specified that no escaping 
other than ';' and '&' is necessary, we need to be able to extract that 
URI without changing anything.

=wil

Gabe Wachob wrote:
> <immature>
> Python RULEZ!!!
> </immature>
>
> Sorry, just had to put that in there.
>
> 	-Gabe
>
>   
>> -----Original Message-----
>> From: Victor Grey [mailto:victor@idcommons.org]
>> Sent: Wednesday, October 24, 2007 10:27 AM
>> To: OASIS XRI TC
>> Subject: Re: [xri] ED07 Issue #1: Encoding of + in query parameters
>>
>> John Bradley wrote:
>>     
>>> Will specifying that a literal space must be encoded as %20 if its
>>> included solve the problem?
>>>       
>> Unfortunately no. The standard URL parsers will convert both %20 and
>> + to a space. In order to get our + back in "application/xrds+xml"
>> for instance, we convert -all- spaces back to +. We don't have any
>> way, without really getting into the guts of ruby or php, to know
>> whether that space was originally a %20 or a +.
>>
>> =vg
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS TC that
>> generates this mail.  You may a link to this group and all your TCs in
>> OASIS
>> at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>     
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
>
>