- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 05 Oct 2006 17:01:45 +0200
- To: Joe Gregorio <joe@bitworking.org>
- CC: uri@w3.org
Joe Gregorio schrieb:
> This has been a long running part of the discussion
> and any ideas would be greatly appreciated. Here
> is a quick synopsis of the problems:
>
> 1. What about the character encoding of non-ascii characters?
> Do we force UTF-8?
I think if you *can* enforce it, by all means do it.
> 2. What about double escaping?
> Given:
>
> a none%20of%20the%20above
>
> Should the substitution be:
>
> http://example.org/{a}
> http://example.org/none%20of%20the%20above
>
> or
>
> http://example.org/none%2520of%2520the%2520above
I think it would be the latter. Pick one, but then be consistent :-)
> 3. What about 'reserved' characters?
> Given:
>
> q hullo#world
>
> Should the substitution be:
>
> http://example.org/{q}
> http://example.org/hullo#world
>
> or
>
> http://example.org/hullo%23world
That's an interesting edge case. I think it would need to be the latter.
>> - I've never seen "individual" as an org name in an IETF document;
>> leaving it out instead seems to be the agreed-upon way to do it...
>
> Fixed. (I had previously tried to drop the organization element
> but found that that caused and error.)
That changed in a recent version (before, you would have left the
element empty...).
Best regards, Julian
Received on Thursday, 5 October 2006 15:01:58 UTC