Re: [whatwg/url] Rephrase the stated goal of obsoleting RFC 3986 and RFC 3987 (Issue #703)

I think the characterization of the root problem as one of "respect" and "giving credit" is dead wrong.
It's a disagreement about an engineering question about the applicability of the "Postel Principle" to one particular protocol element which has many roles outside of browsers and HTML. 

URLs may seem to be just another part of the browser experience and for that application, perhaps it is useful to specify additional rules and behavior. But being generous to writers who type in URLs by hand into HTML and the Address bar isn't worth the pain of making every other non-browser application suffer.

People are used to URLs breaking, not just new 404 not founds (and the occasional 418) but we've managed to move large swaths of the net from http: to https:. 

IETF is not a membership organization -- "the only ones there are the people who come". 
Why isn't there a WHATWG HTTP Living Standard? Perhaps that might give a clue.


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

Message ID: <whatwg/url/issues/703/1243046945@github.com>