Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)

@nox: that text in the RFC is also rather useless and is mostly there for humans to understand a little what the intention is: readable characters is better than percent-encoded ones since they may be read by humans. "How to write a readable URL" sort of.

Nobody would say that a URL cannot contain such codes. They are legal entities of a URL.

I think this is an important issue. I've kept harping on this number-of-slashes issue and I've been told at least twice that the URL spec says it should be two slashes, when in fact the URL spec says a parser should handle an infinite[*] amount of them.

For me personally, this (unorthodox) split is causing some of the confusion I experience when reading this spec. Maybe just maybe I'm not alone. And I have read a spec or two before.

[*] = it actually doesn't specify an exact amount

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/118#issuecomment-276087742