- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Tue, 16 Oct 2012 13:18:59 +0200
- To: Martin J. Dürst <duerst@it.aoyama.ac.jp>
- Cc: Larry Masinter <masinter@adobe.com>, Ted Hardie <ted.ietf@gmail.com>, Robin Berjon <robin@w3.org>, "plh@w3.org" <plh@w3.org>, "Peter Saint-Andre (stpeter@stpeter.im)" <stpeter@stpeter.im>, "Pete Resnick (presnick@qualcomm.com)" <presnick@qualcomm.com>, "www-archive@w3.org" <www-archive@w3.org>
On Tue, Oct 16, 2012 at 11:45 AM, "Martin J. Dürst" <duerst@it.aoyama.ac.jp> wrote: > The advantage of having RFC 3986 and RFC 3987(bis) is that it's clear that > one does not have to say anything like "before adding an IRI to a space > separated list of IRIs, replace all spaces with %20". So lots of specs > currently don't say this. That's not an actual advantage. In the context of the URL standard all you would have to talk about is a space-separated list of valid URLs. URLs containing spaces do not suddenly become valid and indeed cannot occur in a space-separated list because such a list is first split on spaces. (Most of this is not drafted yet. I wanted to figure out parsing first.) -- http://annevankesteren.nl/
Received on Tuesday, 16 October 2012 11:19:28 UTC