- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Sat, 1 Nov 2014 13:39:40 +0100
- To: Sam Ruby <rubys@intertwingly.net>
- Cc: WHATWG <whatwg@whatwg.org>
On Sat, Nov 1, 2014 at 1:29 PM, Sam Ruby <rubys@intertwingly.net> wrote:
> https://tools.ietf.org/html/draft-ietf-appsawg-uri-scheme-reg-04
I don't know how it should change. I just said that it doesn't say
that you cannot invent new hierarchical URIs (to use IETF terms). As
long as the IETF keeps building on top of RFC 3986, the mismatch will
continue.
>> I just gave you one, "%"... E.g. "http://example.org/?%" does not have
>> an RFC 3986 representation.
>
> Here's the output of a URI parser:
>
> $ ruby -r addressable/uri -e "p
> Addressable::URI.parse('http://example.org/?%').query"
> "%"
That's a bug in that parser, then. (Assuming it meant to conform to RFC 3986.)
Not sure how that helps.
--
https://annevankesteren.nl/
Received on Saturday, 1 November 2014 12:40:04 UTC